BuckBus
API
API
  1. API Introduction
  • API Introduction
    • Introduction
    • References
    • Test store
    • Authorization
    • Processing of requests
    • Webhooks
  • APIs
    • Assets
      • List assets
    • Accounts
      • List accounts
    • Payments
      • Create payment
      • Create fiat payment
      • List payments
      • Payment details
      • List payment transactions
    • Dedicated addresses
      • Create dedicated address
      • Release dedicated address
    • Transfers
      • Create transfer
    • Withdrawals
      • Create withdrawal
      • Withdrawal details
    • Convert
      • Convert amount
  • Schemas
    • Payment
    • PaymentTransaction
    • Lang
    • Withdrawal
    • DedicatedAddress
    • Providers
    • Asset
    • Account
    • Accounts
API
API
  1. API Introduction

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. If no accurate response can be given within 30 seconds, for instance because of problems on the side of the blockchain provider, 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 than make any decisions on the transaction.
Previous
Authorization
Next
Webhooks
Built with