Accept a trade offer

Upon presentation of a trade offer, this endpoint facilitates the user's acceptance of the offer, effectively signalling their agreement to proceed with the trade under the specified conditions. A user can only accept the newest offer created and it can be done within its validity (as defined in offer_validity & expires_at response parameters).

When a user submits a request to accept a trade offer, the platform immediately begins to process this request to finalise the trade. However, there are instances when the processing cannot be completed within a short, predefined time frame (e.g. 10 seconds). In such cases, rather than leaving the user uncertain of the request's status, the API responds with a 202 Accepted status code. This response serves as an acknowledgment that the user's request has been successfully received and is in the queue for processing (in progress status), but it has not yet been finalised.

After receiving 202 Accepted, there are two strategic options to proceed:

  • Retry sending the same request until you receive a 200 Offer has been accepted status response
  • Check the offer status using the Offer Status endpoint
SecuritybearerAuth
Request
path Parameters
Offer-ID
required
string <uuid>

Offer ID

query Parameters
external_transaction_id
required
string

External transaction ID

header Parameters
bp-user-id
required
string <uuid>

User ID

Responses
200

Offer has been accepted

202

Accepted

401

Unauthorized

406

The external transaction already exists. / This offer exists and it has another external transaction id associated.

409

Offer already accepted / A newer offer was created / Offer previously failed

410

Offer expired / invalid offer id

422

Error

429

Too Many Requests

500

Error

503

Maintenance or Service unavailable

patch/v2/offers/{Offer-ID}/accept
Request samples 
Response samples 
application/json
{
  • "data": {
    }
}