You can configure and create tokens for integration of prduct.com with other systems. We recommend creating one token per integration.
Create a new bearer token
Click on the three dots in the lower-left corner.
Select “My company.”
Then go to “API Client” in the menu.
Click “Create new token.”
Grant the token all permissions.
Choose format: JSON (XML does not support all use cases).
When the token is created, you can use it to authenticate your API calls.
Configure a new bearer token
When configuring a new token you should set Response type and Token permissions:
Response type
Choose the response type. XML does not support all use cases. We recommend response type JSON, but you can choose the following:
JSON
XML.
Token permissions
You can select the following permission, we recommend selecting all:
Create
Read
Update
Delete
Furthermore can you se advanced settings, see the section below.
Validation and error handling token configurations
When setting up the bearer token you can also set multiple advanced settings. This dictate how prduct.com should behave when related data is missing or invalid.
In the advanced settings you can choose the following:
Documents bulk - Company relation
A choice of what the system should do on bulk creation of companies if a company is invalid:
Reject all document creations and updates if the linked company (via external_id) is invalid.
Reject only the documents where the linked company (via external_id) is invalid.
If the linked company (via external_id) is invalid, complete the document creation/update but set the company relation to NULL.
EUDR Purchase - Company relation
A choice of what the system should do on EUDR purchase invoice creation if a company is invalid:
Reject all document creations and updates if the linked company (via external_id) is invalid.
If the linked company (via external_id) is invalid, complete the document creation/update but set the company relation to NULL.
EUDR Purchase - Product relation
A choice of what the system should do on EUDR purchase invoice creation if a product is invalid:
Reject all document creations and updates if the linked product (via external_id) is invalid.
Reject only the documents where the linked product (via external_id) is invalid.
If the linked product (via external_id) is invalid, complete the document creation/update but set the product relation to NULL.
Legacy & compatibility options
There is an extra options for older ERPs or non-standard integrations. When this is enabled, a POST with an existing external_id will update the existing record instead of creating a new one.
This i recommended only for legacy systems that can’t send PUT requests.