Configure the webhook
Last updated
Was this helpful?
Last updated
Was this helpful?
A company admin can configure one or more webhooks in your company settings on the Tradecloud One platform:
Select My company in the menu below your avatar.
The Settings tab in the Company menu should be selected.
Configure one or more Webhook Integrations below.
Enable the Order Webhook Integration if you want to receive a webhook trigger when an order has been issued or changed:
A default set of order events will be enabled. The actual set you want to select wil be dependent on the capabilities of your integration and ERP system and your order process requirements. You can find a list of events here:
You can configure the way the delivery schedule is included in the body of a webhook POST request. You can choose between:
Multiple delivery lines per order line. This will result in an orderEvent in the POST request body.
Only one delivery line per order line. This will result in a singleDeliveryOrderEvent in the POST request body.
See the API manual to read about the delivery schedule versus the single delivery per order line.
Enable the Order Documents Webhook Integration if you want to receive a webhook trigger when an order document has been attached:
You may choose whether you want to receive events for documents added by the buyer of an order, the suppplier, or both. You can find a list of events here:
Enable the Shipment Webhook Integration if you want to receive a webhook trigger when a shipment has been issued or changed:
A default set of shipments events will be enabled. The actual set you want to select wil be dependent on the capabilities of your integration and ERP system and your shipment process requirements. You can find a list of events here:
Configure the webhook method and endpoint URL:
Select POST as HTTP method.
Enter your webhook endpoint URL:
The URL must start with https://
Only POST is supported as HTTP method.
Finally, configure the credentials. Choose either Basic authentication, Bearer token or OAuth.
Tradecloud supports Basic authentication, where the client sends a HTTPS request with the Authorization header that contains the word Basic followed by a space and a base64-encoded string username:password.
Published as RFC 7617 "The 'Basic' HTTP Authentication Scheme"
Fill in username and password, as provided by your webhook configuration, and save the settings.
Tradecloud supports Bearer authentication, where the client sends a HTTPS request with the Authorization header that contains word Bearer followed by a space and the static token.
Published as RFC 6750 "The OAuth 2.0 Authorization Framework: Bearer Token Usage"
Fill in the token, as provided by your webhook configuration, and save the settings.
Tradecloud supports the Oauth 2.0 Client Credentials Grant, where the client sends a HTTPS form request with:
grant_type with value client_credentials
client_id, client_secret and scope
Published as the RFC 6749 "Oauth 2.0 Client Credentials Grant"
Fill in the fields:
authentication URL: the OAuth 2.0 token endpoint including your Directory (tenant) ID, for example https://login.microsoftonline.com/<Tenant ID>/oauth2/v2.0/token
client ID: the Application (client) ID of your webhook client app as configured in Ms Azure AD
client Secret: the Client Secret Value of your webhook client app as configured in Ms Azure AD
scope: the scope granted to the webhook client app, for example containing the webhook endpoint https://<webhook endpoint>/.default.
You can test webhook triggers using webhook.site
Use a bogus username and password when testing against webhook site.
