(AUS Only) Make a new entity a direct associated entity of a parent organisation.
Create an entity with the provided details, then associated it with a parent organisation.
The referenced parent entity must be of type ORGANISATION and an ownership query must have been previously completed.
At least the entity name (family name for individuals, registered name for organisations) must be provided in entity.
At least one of role or percentage held must be in the request. If either is null or omitted, then any existing details will be retained. If either detail is given, the it will be replaced, not merged.
Path parameters
The entityId returned previously from an earlier call to /check or /entity
Headers
If, as a Frankie Customer, you are acting on behalf of your own customers, then you can populate this field with a Frankie-assigned ID.
Note: If using a CustomerChildID, you will also need a separate api_key for each child.
Any documents, checks, entities that are created when this field has been populated will now be tied to this CustomerID + CustomerChildID combination. Just as Customers cannot see data created by other Customers, so too a Customer’s Children will not be able to see each other’s data.
A Customer can see the documents/entities and checks of all their Children.
Open string that can be used to define the “channel” the request comes in from. It can potentially be used in routing and risk calculations upon request. Default values that can be used are:
- api
- portal
- smartui
Any alphanumeric string is supported though. Anything over 64 characters will be truncated.
Request
The roles are optional in an association request, but at least one of roles and percentage held must be included. If the roles object is omitted, then any existing roles for the entity will be retained. To delete all roles for the entity use an empty roles array ([]). When updating roles, all the current roles for the entity must be included. They can be obtained from the business ownership query results, by going through the officers array in the ownership details for the organisation and extracting records with the ID of the entity and a non-blank ‘addedBy’ field.
Response
Unique identifier for every request. Can be used for tracking down answers with technical support.
Uses the ULID format (a time-based, sortable UUID)
Note: this will be different for every request.