...
CB confirms a successful cancellation of the order after the service window ended. The shop is notified with the operation notifyOrder and status event Cancelled
The shop confirms the cancellation to the customer
Volume, limits and performance requirements
Timing
Webservice requests are processed realtime, i.e. an order is registered immediately when the webservice call is executed. Order processing at CB is based on scheduled processes and not primarily triggered by the webservice request.
Responses to the requester are send in Near-Realtime (NRT) with an average delay of 2 to 3 minutes. The regular maximum delay is 5 minutes, in exceptions running up to 10 minutes. During this timeframe the orderstatus has reached a status that is not yet reported to the requestor.
Volume
Webservice requests are limited to a maximum of 10 requests per service per second per requestor.
Performance
The media webservices comply with the generic CB webservice performance requirements:
Average response time within 2 seconds during prime-time (08:00-01:00 CET)
Response within 3 seconds for 99,95% of the requests during prime-time
Response within 6 seconds for 99% of the requests outside prime-time
Test environment
| Include Page | ||||
|---|---|---|---|---|
|