Developers · Partner Flow

Hosted Partner Flow universal handoff

Your backend creates a short-lived handoff. The holder approves a narrow result. Your backend verifies the new receipt.

What this is

A handoff is not an OAuth callback, not a receipt grant, and not a transaction, payment, or trade. The partner backend must re-fetch and verify the current public receipt.

Sequence

  • Partner backend creates a handoff for one configured sandbox or Production-reviewed app.
  • The holder opens a Hosted Partner Flow URL that contains only an opaque verify_request.
  • The holder reviews the request brief and gives fresh consent.
  • Abraxas stores a partner-bound result. The callback or deep link is a completion signal only.
  • Partner backend re-fetches and verifies the current public receipt with Partner Kit.

Canonical HTTPS

POST https://abraxasworld.xyz/api/v1/partner-handoff
Authorization: Bearer YOUR_SANDBOX_API_KEY
Content-Type: application/json
X-Abraxas-Application-Id: YOUR_APP_ID

{"runtime":"universal_https"}

# Response hosted_url contains only verify_request.
# GET /api/v1/partner-handoff/{ref} then kit.verifyReceiptId(public_receipt_id).
Continue with Partner FlowIntegration StudioStarter KitLaunchpadPartner Flow docs