Naar inhoud springen
Tibata
Docs
Integrations

Update Mappings

PUT
/v1/integrations/connections/{connection_id}/mappings

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.

Autorisatie

bearerAuth
headerAutorisatieBearer <token>

Padparameters

connection_id*string

ID of the integration connection

Request-body

Integration mappings to set

application/json
  1. body
[index: integer]?

Responsbody

The mappings sent, as the request listed them

application/json
  1. response
data*array<>
curl -X PUT 'https://api.tibata.ai/v1/integrations/connections/string/mappings' \  -H 'Content-Type: application/json' \  -d '[  {    "internalId": "tB6gszM_JPk7vKaHfz1H4",    "internalType": "space",    "externalId": "100",    "externalType": "exact_division"  }]'
Voorbeeldrespons
{  "data": [    {      "internalId": "tB6gszM_JPk7vKaHfz1H4",      "internalType": "space",      "externalId": "100",      "externalType": "exact_division"    }  ]}