webhook
Endpoint URL
POST https://api.tryoto.com/rest/v2/webhook
Example Request Body
Here is an example of a request body:
{
"method": "post",
"url": "https://webhook.site/3e53c98a-a089-4ca4-9bc4-df10e5a71e4b",
"orderPrefix": "fulfillment",
"timestampFormat": "2025-01-01 13:14:34",
"secretKey": "key1234",
"authorizationKey": "authorizationkey123",
"webhookType": "shipmentError"
}
Request Parameters
Name | Required | Type | Description |
---|---|---|---|
method | yes | string | `POST` or `PUT` |
url | yes | string | Your endpoint listens to get OTO webhook payload, when order status changes. exp.`https://webhook.site/3e53c98a-a089-4ca4-9bc4-df10e5a71e4b` |
secretKey | no | string | With this key message is signed and receiver validate. |
authorizationKey | no | string | Secure token used to authenticate and validate incoming webhook requests. |
timestampFormat | no | string | Exp "yyyy-MM-dd HH:mm:ss" format receiver want to get. |
orderPrefix | no | string | If orders has prefix in OTO, then put prefix string to be removed before webhook body prepared. |
webhookType | no | string | `shipmentError`, sends create shipment error messages; `orderStatus` sends order status changes. default is `orderStatus and newOrders` webhook is used to create orders in a different WMS. |
Available Packages: Starter Package, Scale Package, Enterprise Package, Marketplaces
This endpoint enables OTO to send update payloads to the specified URL using the defined method. Optional security measures, such as token authentication and payload validation, can be configured for enhanced security.
Request Parameters: |
webhook
Endpoint URL
GET https://api.tryoto.com/rest/v2/webhook
Request Parameters
Name | Required | Type | Description |
---|---|---|---|
id | no | string | id of the webhook |
Available Packages: Starter Package, Scale Package, Enterprise Package, Marketplaces
This endpoint allows you to retrieve a list of all registered webhook definitions. It provides detailed information about each webhook, including its configuration and associated event triggers, enabling you to manage and review your webhook integrations effectively.
Note: You can filter by id if you know the id of the webhook.
Request Parameters: |
webhook
Endpoint URL
PUT https://api.tryoto.com/rest/v2/webhook
Example Request Body
Here is an example of a request body:
{
"id": 59,
"method": "post",
"url": "https://webhook.site/3e53c98a-a089-4ca4-9bc4-df10e5a71e4b",
"orderPrefix": "test-2",
"timestampFormat": "2025-01-01 10:10:10",
"secretKey": "secret123",
"authorizationKey": "authorizationkey123",
"webhookType": "orderStatus"
}
Request Parameters
Name | Required | Type | Description |
---|---|---|---|
id | yes | string | Id of the webhook record. |
method | yes | string | `POST` or `PUT` |
url | yes | string | Your endpoint listens to get OTO webhook payload, when order status changes. exp.`https://webhook.site/3e53c98a-a089-4ca4-9bc4-df10e5a71e4b` |
secretKey | no | string | With this key message is signed and receiver validate. |
authorizationKey | no | string | Authorization key. |
timestampFormat | no | string | Exp "yyyy-MM-dd HH:mm:ss" format receiver want to get. |
orderPrefix | no | string | If orders has prefix in OTO, then put prefix string to be removed before webhook body prepared. |
webhookType | no | string | `shipmentError`, sends create shipment error messages; `orderStatus` sends order status changes. default is `orderStatus and newOrders` webhook is used to create orders in a different WMS. |
Available Packages: Starter Package, Scale Package, Enterprise Package, Marketplaces
This API endpoint allows updating an already registered webhook by providing its unique ID. This ensures you can modify existing webhook configurations, such as URL, secretKey, or other parameters, without needing to delete and recreate it.
Request Parameters: |
webhook
Endpoint URL
DELETE https://api.tryoto.com/rest/v2/webhook
Request Parameters
Name | Required | Type | Description |
---|---|---|---|
id | yes | string | Id of the webhook record. |
Available Packages: Starter Package, Scale Package, Enterprise Package, Marketplaces
This API endpoint enables the removal of a registered webhook from the system using its unique ID. This ensures you can effectively manage and clean up webhook configurations that are no longer needed.
Request Parameters: |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article