Skip to main content

Endpoints

  • Get Deposit Authorization: Resolve the points holder account, build the typed data to sign, and return the nonce and expiry for a deposit authorization
  • Get Deposit Claim: Verify the signed deposit authorization and return the oracle signature for Deposit.deposit(...)
  • Get Settlement Claim: Verify that an offer was properly settled onchain and return the oracle signature for settlement
  • GET /deposits?account=...: Read first-deposit status without authorization or writes
  • GET /signatures?account=...: Read paginated points-change reviews; no signatures are exposed
  • GET /markets: Check market availability
  • GET /ratelimits: Read first-deposit caps and available capacity
  • GET /config: Read adapter mappings and contract addresses

Deposit Flow

1

Request authorization payload

Call POST /claim/deposit/authorization with pointsId, account, and operator.
2

Sign as the account owner

Use the returned authorization fields to build the EIP-712 payload your client expects, then sign it with the signer that controls the underlying points account.
3

Request the oracle claim

Call POST /claim/deposit with the signed authorization. The response contains the claim and oracle signature when the deposit is ready. Submit when status is ready. The claim may cover only part of the observed balance; delayedAmount reports the remainder.
account is the hex-encoded ERC-7930 account for the underlying points holder. operator is the EVM wallet that will submit the onchain deposit transaction.

Following a Review

Poll GET /deposits?account=... while the deposit panel is open, and refresh on mount or focus. Do not poll POST /claim/deposit: it can reserve capacity or change review state. Waiting does not require repeated wallet signatures. Authorization and claims are short-lived. Use the returned expiry timestamps, request fresh authorization when needed, and submit signed claims promptly. Use the returned status to determine whether a deposit is ready. Timestamps such as maturesAt and nextCheckAt help show progress but do not guarantee completion. requiresAuthorization indicates when a new signature is needed, and resetReason explains why a review restarted. Once the onchain deposit is confirmed, use /signatures to follow any remaining points reviews. /signatures accepts optional account, limit, and offset query parameters. Follow pagination.nextOffset while hasMore is true. Maturity is not a promise of immediate release; use the reported status to follow progress.

Capacity and Market Health

GET /ratelimits reports whole-point decimal strings in fields ending in Pts. Claim and deposit status amounts use 18-decimal onchain units. All timestamps use Unix seconds. Use accountCapPts, globalCapPts, and immediateCapacityPts for current deposit limits and availability. Capacity can change before a claim is requested. These limits apply to deposits, not HTTP requests. Use GET /markets to check whether a market is active or paused. If it is paused, deposits and oracle updates may be unavailable until service resumes. See Oracle System for the review process and market availability.