Build 2026-10-07 13:08:32
The Order Management API is used to create and handle orders
https://{slug}.api-se.playground.norce.tech/checkout/order/
https://{slug}.api-se.stage.norce.tech/checkout/order/
https://{slug}.api-se.norce.tech/checkout/order/
Hook
Reference for the hook. Should be the same across orders. Used to track hooks in event logs.
The path to the property in the order that the hooks might respond with patches to. Used to correctly determine the order to call each hook in.
Url to invoke on hook trigger. Can include references to adapter configuration and order inside curly braces.
https://customer-slug.api-se.playground.norce.tech/checkout/order/api/v1/checkout/orders/{orderId}/hooks
https://customer-slug.api-se.stage.norce.tech/checkout/order/api/v1/checkout/orders/{orderId}/hooks
https://customer-slug.api-se.norce.tech/checkout/order/api/v1/checkout/orders/{orderId}/hooks
curl -i -X POST \
'https://customer-slug.api-se.playground.norce.tech/checkout/order/api/v1/checkout/orders/{orderId}/hooks' \
-H 'Authorization: YOUR_API_KEY_HERE' \
-H 'Content-Type: application/json' \
-H 'x-channel: 1' \
-H 'x-merchant: norce' \
-d '{
"adapterId": "jetshop_adapter",
"reference": "string",
"description": "string",
"scope": "string",
"target": "string",
"invoke": "{config.adapter.publicUrl}/api/v1/orders/{order.id}/some-hook",
"version": "v0"
}'https://customer-slug.api-se.playground.norce.tech/checkout/order/api/v1/checkout/orders/{orderId}/hooks/{hookId}
https://customer-slug.api-se.stage.norce.tech/checkout/order/api/v1/checkout/orders/{orderId}/hooks/{hookId}
https://customer-slug.api-se.norce.tech/checkout/order/api/v1/checkout/orders/{orderId}/hooks/{hookId}
curl -i -X DELETE \
'https://customer-slug.api-se.playground.norce.tech/checkout/order/api/v1/checkout/orders/{orderId}/hooks/{hookId}' \
-H 'Authorization: YOUR_API_KEY_HERE' \
-H 'x-channel: 1' \
-H 'x-merchant: norce'Notification
Identifier for the system responsible for this notification. If any reference to configuration is made inside curly braces in Invoke the configuration is found using this identifier.
Reference for the Notification. Should be the same across orders. Used to track notifications in event logs.
Purpose or effect of the notification.
Valid json path inside the order. Does not support scope inside arrays.
Json schema (https://json-schema.org/draft/2020-12/schema) on the scope. Notification triggers when a change occurs on the scope and the schema is valid for the scope.
Url to invoke on notification trigger. Can include references to adapter configuration and order inside curly braces.
https://customer-slug.api-se.playground.norce.tech/checkout/order/api/v1/checkout/orders/{orderId}/notifications
https://customer-slug.api-se.stage.norce.tech/checkout/order/api/v1/checkout/orders/{orderId}/notifications
https://customer-slug.api-se.norce.tech/checkout/order/api/v1/checkout/orders/{orderId}/notifications
curl -i -X POST \
'https://customer-slug.api-se.playground.norce.tech/checkout/order/api/v1/checkout/orders/{orderId}/notifications' \
-H 'Authorization: YOUR_API_KEY_HERE' \
-H 'Content-Type: application/json' \
-H 'x-channel: 1' \
-H 'x-merchant: norce' \
-d '{
"adapterId": "jetshop_adapter",
"reference": "PuXCudQEiWTOHvquGGolFUVOuy",
"description": "Export payment information to Jetshop when order has been completed.",
"scope": "/state/currentStatus",
"schema": {
"const": "completed"
},
"invoke": "{config.adapter.publicUrl}/api/v1/callbacks/orders/{order.id}/specific-callback",
"version": "v0",
"delay": 0
}'