Operator entities
An organisation can store several EUDR operator entities, for example one
for each legal entity in a group. A due diligence statement (DDS) names one
operator, so you choose the entity when you create, update or submit a
statement by sending operator_entity_id.
These endpoints work on the acting organisation, so they also work while
acting as a child with x-acting-as.
▶The default entity
One entity is the default. A statement that names no operator files under
it. The default is the same data as the operator_* fields on
Get Me and Update Me: changing either one
changes the other.
An organisation that set operator_* fields before this endpoint existed
already has that block as its default entity. That entity can be
incomplete; missing_fields lists what it lacks.
▶Endpoints
| Method | Path | Description |
|---|---|---|
| GET | /organizations/me/operator-entities | List the entities, default first |
| POST | /organizations/me/operator-entities | Add an entity |
| PATCH | /organizations/me/operator-entities/:entityId | Edit an entity or make it the default |
| DELETE | /organizations/me/operator-entities/:entityId | Delete an entity |
▶Choosing an entity for a statement
Send operator_entity_id on
Create Audit Trail,
Update DDS Record
or Submit DDS. The entity must
belong to the statement's organisation, and it must be complete.
The entity's details are copied onto the statement, and the statement's
operator.entity_id records which entity they came from. Later edits to the
entity do not change the statement. To pick up an edit, send the same
operator_entity_id again. Submitting with operator_entity_id does this
for you.
Required scope:
organizations:readto list,organizations:writeto create, edit or delete