Connect to an organisation
After a member is logged in they can connect to an organisation by accepting the invitation.
As long as a member is not connected to a single organisation, they are not able to perform any of the API calls, except the acceptConnectionForOrganisation and rejectConnectionForOrganisation. The other API calls will return a permission error 403.
Accept or reject a connection via the service portal
For the time being, we would suggest that members accept the invitation via the Linckr Service Portal. However, let's explore in the next section the not-so-convenient way to accept a connection via the API.
Accept or reject a connection via the API
By performing the mutation acceptConnectionForOrganisation a connection can be accepted. Checkout, the Postman documentation via the following link.
The hard part is to obtain the values for the properties connectionId and organisationId. They must be parsed from the link in the invitation email. This link is a universal link that redirects to the service portal:
http://url4826.linckr.com/ls/click?upn=B4dAiQfWOkxfXkh5n9byecdbwLPsOV8J6O34CWIvL4hMBNdfbEO6qw76dyPlPfT6-2FWgGXCD9-2B8zyuxbFwYQW51UKh-2BTQM4V29toQPtN-2B2z3ifkMMcXe-2FS4GxiXVGgVSDR44vHT9B6EKPQu0lua8YrVATfNP8gt1VToFMXd93T07DNbkyyp-2Bue2cF-2BLw-2F4yunyEUZ1Hd4ooRyFGCGYoWz4dVI8N1BWPT-2FmbTkhGPIt40-3DxOw8_vDhyrByJyj9jzFVVCWkYCzhiZ88-2FybnFRFkwfovsmUkSo9m0fS1d7rZvsZFS-2BQno38mt3qrpQjGddFPQIklNMXhPj-2BJGoR0FkTENW7bZbmibIac1faMiiQcHC9y2IUcdcsR2B31rQhbEg0903e9SSTeuRujazEalLpZgz-2BwMVPH-2FyMIUxXy9GM-2FOoRn-2FIp0-2FKsnhcuDUiuoAi0yzApuRdyTjx4hNqnms-2BYoa7AJGlYuzif9W9I4XSGwPiWhnZUAMGXm41h-2BwT2HhWx0fZfEDmFw2GQYOQgCsqacvCE64M3N0JzQwzOqyM-2F35zxtFBmK1wDbOca9gsad0c-2B4BeJN7Ltgi6VswDhD2slzDhiutjEs-3D
When you open this link, it redirects to another link:
https://serviceportal.staging.linckr.com/invitations?org=ede5d174-6376-4923-a7a7-404ac0b6b221&invite=43f0fd40-5f1d-4c9d-8d67-86438671eaf3&org_name=Blinqwise+Immo
From the latter URL you can parse the connectionId from the invite query param, and the organisationId from the org query param. We are aware that this approach is not ideal for integration purposes. In the future, a GraphQL query will be available to fetch the open connections linked to a certain member.