Cross organisation ingest
- Alexis Rombaut
- An De Moor
This feature is part of release 25.2 and is intended for API integrators
Introduction
When an API integrator wants to upload objects for multiple organisations, a separate API user is required for each organisation. This procedure is cumbersome due to having to create and maintain multiple users. With the new cross organisation ingest feature, the API user will be able specify the target organisation when creating records.
Ingest
By using the property organisationId or organisationExternalId in the API method POST /records the user can choose a different organisation.
Linked concept | Description |
|---|---|
Zone | Because zones are not shareable, the specified zone must be from the same organisation as the record. |
Groups |
|
Parent record | The parent can be from any organisation. However, if the index is not shared, the parent should be from the same organisation. |
Restrictions
The following restrictions apply
The user must have the function
ADMIN_EDIT_ALL_ORGANISATIONSThe organisation must not be special (monitor and _default)
When using Resumable Uploads the index must be shared between all organisations