Get Mappings
Retrieve all mappings for this connection. A connection the organization cannot use (a SharePoint connection while SharePoint is switched off for it) answers 404.
bearerAuthAutorisatieBearer <token>connection_id*stringID of the integration connection
Integration mappings for the connection
application/json- response
data*array<>curl -X GET 'https://api.tibata.ai/v1/integrations/connections/string/mappings'{ "data": [ { "internalId": "tB6gszM_JPk7vKaHfz1H4", "internalType": "space", "externalId": "100", "externalType": "exact_division" } ]}List Connections GET
Returns an overview of external integration connections available in the organization. Only safe, non-sensitive fields are exposed (no tokens or personal user info). Only connections the organization can use are listed. When SharePoint is switched off for the organization, its SharePoint connections are not listed, and their mappings answer 404 to a read and a write, as a connection that does not exist. Their links are kept, and return when SharePoint is switched on again. A connection belongs to a member of the organization. When that member is removed or leaves, their connection is deleted and its id answers 404 to a read and a write of its mappings. The mappings themselves are kept: list the connections again, and another member's connection to the same tenant reads and writes them under its own id. When no other member is connected, nothing is listed for that tenant until someone connects.
Update Mappings PUT
Replace all mappings for this connection. A mapping the request leaves out is removed, a new one is added, and one it repeats is kept as it is, with what was set for it in Tibata. Send an empty array to remove all mappings. The response repeats the mappings you sent. For SharePoint, a repeated link keeps whether it includes its subfolders, the files left out under it and its sync state. A link the space already holds through another connection is not written twice, though the response still lists it. While SharePoint is switched off for the organization, a SharePoint connection answers 404 and nothing is written, and a replace of another connection leaves its SharePoint links as they are. Adding or removing a link of a Space where not every member can edit (general access Can view or No access) needs the Editor or Manager role on that Space: a client-credentials token through a role given to its client, a token issued for a user through that user's role. Without it, the request answers `403` with the code `FORBIDDEN` and the reason `ROLE_REQUIRED`, and nothing is written. A link the request repeats unchanged needs no role.