Easy Labs
APITreasuryTreasury

Confirm a send operation (with optional 2FA code)

Confirm a send operation (with optional 2FA code)

POST
/v1/api/treasury/send/confirm

Authorization

apiKey
x-easy-api-key<token>

Merchant API key. Publishable keys (pk_test_* / pk_live_) are safe for browser/frontend use and carry a limited scope set (sessions, payment_instruments, customers, orders writes; products, product_prices, payment_links reads). Secret keys (sk_test_ / sk_live_*) grant full admin access and must only be used server-side.

In: header

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

application/json

application/json

curl -X POST "https://loading/v1/api/treasury/send/confirm" \  -H "Content-Type: application/json" \  -d '{    "transaction_id": "0fec1e58-b197-4052-99cf-2218496c5482"  }'
{
  "success": true,
  "timestamp": "2019-08-24T14:15:22Z",
  "data": null,
  "message": "string",
  "pagination": {
    "total": 0,
    "limit": 1,
    "offset": 0,
    "has_more": true,
    "truncated": true,
    "cursors": {
      "first": "string",
      "last": "string"
    }
  }
}
{
  "success": false,
  "timestamp": "2019-08-24T14:15:22Z",
  "error": {
    "code": "string",
    "message": "string",
    "details": null
  }
}
{
  "success": false,
  "timestamp": "2019-08-24T14:15:22Z",
  "error": {
    "code": "string",
    "message": "string",
    "details": null
  }
}
{
  "success": false,
  "timestamp": "2019-08-24T14:15:22Z",
  "error": {
    "code": "string",
    "message": "string",
    "details": null
  }
}
{
  "success": false,
  "timestamp": "2019-08-24T14:15:22Z",
  "error": {
    "code": "string",
    "message": "string",
    "details": null
  }
}

Cancel a pending send operation

Cancel a pending send operation

Pre-fill a payment attached to a pending recipient invitation

Creates a payment that stays pending until the invited recipient submits their bank details via POST /recipients/accept-invite, at which point it executes automatically (or falls back to the normal approval flow if security rules require it at that time). Requires an existing, non-expired pending invitation for the recipient (create one first via POST /recipients/:id/invite) — a missing recipient returns 404, but a missing/expired invitation returns 400 (NO_PENDING_INVITATION), not 404, since it's a client-correctable sequencing error rather than a missing resource. A duplicate active deferred send for the same invitation returns 409.