Venue bindings

Submit a list of venue authorization signatures

Sign each returned payload exactly and map it by requestId. An incomplete subset is accepted; a venue queues only when its required signatures are complete. All signatures must recover the batch owner. They authenticate this operation without Bearer authentication or an additional wallet signature. Persist and reuse the submission body and Idempotency-Key. Keys are scoped to bindingId; replay returns current state and still verifies signatures. Unknown/duplicate request IDs and signature replacement are rejected. Worker confirms external authorization before saving credentials; uncertain outcomes remain confirming, with no signed resubmission after session expiry.

post/v1/venue-bindings/{bindingId}/submit

Request

  • Base URL: https://api.mob.exchange
  • URL: https://api.mob.exchange/v1/venue-bindings/{bindingId}/submit
  • Auth: none required

Path parameters

bindingIdstring uuid required

Headers

Idempotency-Keystring required

Persist one ID per intended mutation before sending. Reuse it with the same request for retries; different content returns 409.

Request body

Response

Signatures durably accepted; poll to observe venue execution.

bindingIdstring uuid required
ownerstring required
expiresAtstring date-time required
status'awaiting_signatures' | 'processing' | 'bound' | 'partial_success' | 'failed' required

Changes

No recorded changes to this operation across all 1 revision of this API.