Intents
Ask Swivy to sign or execute, then read the result.
Preview: not generally available
Swivy runs in staging only. Paths and fields can change before general availability. There is no public base URL yet; preview partners get theirs with their credentials.
Every signature and transaction is an intent. Create it, then poll GET /v1/runtime/intents/{intentId} or wait for the swivy.intent.completed webhook.
3 endpoints, generated from Swivy's OpenAPI document (apps/api/src/openapi.ts).
Create a signing intent
Auth: x-swivy-app-id + x-swivy-publishable-key + Authorization: Bearer <sessionToken> or x-swivy-app-id + x-swivy-secret-key (server only) + Authorization: Bearer <sessionToken>
Request body: Signing intent payload
Responses: 200 Queued or completed signing intent · 400 Unsupported signing payload · 401 MFA required or invalid runtime session · 403 Signing not allowed · 404 Managed account not found · 409 Client reconstruction required
Create a transaction intent
Auth: x-swivy-app-id + x-swivy-publishable-key + Authorization: Bearer <sessionToken> or x-swivy-app-id + x-swivy-secret-key (server only) + Authorization: Bearer <sessionToken>
Request body: Transaction intent payload
Responses: 200 Queued or completed transaction intent · 400 Unsupported transaction payload · 401 MFA required or invalid runtime session · 403 Execution not allowed · 404 Managed account not found · 409 Client reconstruction required
Fetch an intent by id
Auth: x-swivy-app-id + x-swivy-publishable-key + Authorization: Bearer <sessionToken> or x-swivy-app-id + x-swivy-secret-key (server only) + Authorization: Bearer <sessionToken>
Parameters
Responses: 200 Intent payload · 401 Invalid runtime session or environment credentials · 404 Intent not found