Sinbad Partner API

curl -X POST https://us-central1-sinbad-staging-env.cloudfunctions.net/b2b-v1/v1/trade-breakdowns/breakdown_demo/approval \
     -H "Idempotency-Key: request_demo_001" \
     -H "Authorization: Bearer <token>" \
     -H "Content-Type: application/json" \
     -d '{}'

{
  "approvalRequired": true,
  "approval": {
    "required": true,
    "tokenAddress": "0x4444444444444444444444444444444444444444",
    "spender": "0x3333333333333333333333333333333333333333",
    "requiredAmount": "100000000",
    "allowance": "0"
  },
  "transactions": [
    {
      "preparationId": "preparation_approval",
      "purpose": "approval",
      "chainId": 80002,
      "from": "0x19e7e376e7c213b7e7e7e46cc70a5dd086daff2a",
      "to": "0x4444444444444444444444444444444444444444",
      "data": "0x095ea7b300000000000000000000000033333333333333333333333333333333333333330000000000000000000000000000000000000000000000000000000005f5e100",
      "value": "0",
      "expiresAt": "2026-10-23T10:05:00.000Z"
    }
  ]
}

Prepare token approval.

Credential: Customer session

Before you call

A customer session for the same partner, integration, customer, wallet and chain.
Use the original preparationId and the customer’s registered wallet.
Keep the signed bytes and any known hashes if you need to recover an uncertain submission.
Set an Idempotency-Key and reuse it for an identical retry.

Prepares the token approval transactions that a SELL needs before escrow creation. Use the owning customer session. Sinbad may reuse an allowance snapshot for up to 30 seconds and invalidates it after a confirmed approval or reset. A snapshot is advisory, because Sinbad always simulates the current chain state before it broadcasts.

The response holds no transactions when the customer needs no approval: on a BUY, or when the allowance is already enough. On a SELL, it returns the exact approval, preceded by an allowance reset when a non-zero allowance is too small.

Run the transactions in order and wait for each to be CONFIRMED before the next. You can execute them with the wallet, submit the signed bytes of an ordinary wallet transaction to POST /v1/transactions, or broadcast externally and report the hash there. An approval does not create a trade and does not extend the breakdown’s deadline.

Confirm with Sinbad that this endpoint is enabled in your environment.

Errors

Status	Code	What to do
400	`VALIDATION_ERROR`	Correct the fields reported in details before retrying.
401	`UNAUTHENTICATED`	Create a new customer session or use a valid server credential.
403	`FORBIDDEN`	Check credential ownership, integration and the supplied Origin.
404	`NOT_FOUND`	Check the resource ID. A resource that belongs to someone else also returns 404.
409	`CONFLICT`	Read the current state again before you prepare or retry.
503	`UPSTREAM_ERROR`	Retry with backoff; preserve the same idempotency key for a repeated mutation.

Authentication

AuthorizationBearer

Bearer authentication of the form Bearer <token>, where token is your auth token.

Path parameters

breakdownIdstringRequired

Request

This endpoint expects an object.

Response

Separate approval calls in execution order.

approvalRequiredboolean

approvalobject

transactionslist of objects

Errors

400

Bad Request Error

401

Unauthorized Error

403

Forbidden Error

404

Not Found Error

409

Conflict Error

503

Service Unavailable Error

Authentication

Path parameters

Headers

Request

Response

Errors