Processing of requests BucksBus will promptly process any request it receives and will return the processing result ("successful" or "failed"). The response will contain the response HTTP code, standard headers and, if desired, the response body in the JSON format.To ensure idempotency of requests to the BucksBus API, it is required to send a unique idempotency key in the x-idempotency-key header. This key must be unique for each request and must not exceed 40 characters in length. If the key exceeds 40 characters, the service will reject the request with HTTP status code 400 (Bad Request). Using x-idempotency-key allows clients to safely retry requests, for example, in case of network errors, without risking duplicate operations. Reusing the same key within 24 hours will result in the service returning the result of the original request without creating new resources.If no accurate response can be given within 30 seconds, for instance because of problems on the side of the blockchain provider, the service will return the response code HTTP 500, and for requests related to payments, it will also try to cancel the operation. HTTP 500 does not show whether your operation was successful or failed. Therefore, upon receiving a HTTP 500, you must first find the result of your request processing and only then make any decisions on the transaction.
