Submit Signed Artifact

Submit the externally signed artifact for the current swap step.

Endpoint: POST /api/v1/swap/{swapId}/signing Auth: Required (Authorization: Bearer YOUR_API_KEY)

Headers

Header	Required	Description
Idempotency-Key	No	Optional opaque dedupe token. If omitted, the gateway generates one automatically. Leave it blank for one-off Swagger or curl calls. Send your own UUIDv4 or ULID only when retrying the exact same payload and you need retry-safe dedupe. Allowed characters: A-Z, a-z, 0-9, ., _, :, -. Max 200 chars.

Path parameters

Field	Type	Required	Description
swapId	string	Yes	Swap ID returned by POST /swap/build

Request body

Field	Type	Required	Description
rawTx	string	Yes	Signed transaction artifact returned by the external wallet or signer

Example

curl -X POST 'https://api.gateway.zert.com/api/v1/swap/92714c81-38ec-4782-8624-0f56f526a9fd/signing' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -d '{
    "rawTx": "0x_signed_tx_from_external_wallet"
  }'

Leave Idempotency-Key blank for one-off Swagger or curl calls. If you need retry-safe dedupe, send your own key only when retrying the exact same payload. The SDK and Postman collection can generate one automatically.

Responses

Code	Description
200	Signed artifact accepted. Poll the same signing surface for the next step
400	Invalid signed transaction
401	Unauthorized
404	Swap not found
409	Current tx request is expired, not yet valid, or does not match the payload
503	PG or Kafka unavailable

Zert APIsapi.gateway.zert.com

Zert API — Submit Signed Artifact