API Reference
Endpoint-by-endpoint reference for the Nora /v2 API.
The Nora /v2 API is a JSON-over-HTTPS REST API. The public surface includes
intents (onramp, offramp, approve-burn) and wallets (registration and
on-chain whitelist activation).
Base URLs
| Environment | Base URL |
|---|---|
| Sandbox | https://sandbox.api.nora.finance |
| Production | https://api.nora.finance |
Authentication
Every request sends a single header:
X-API-Key: sk_test_...Keys bind to (organization, instance) — no other auth header is needed.
See Authentication.
Response envelope
Success: the resource shape directly (no data wrapper).
{ "id": "…", "status": "active" }Failure: /v2 endpoints return JSON errors. The exact shape varies
by endpoint family:
/v2/intents/*returns{ code: string, message: string, validationErrors?: [...], details?: object }— a richer envelope with structured validation info./v2/wallets/*returns{ code: string, message: string, validationErrors?: [...], details?: object }. Wallet-specific machine codes appear indetails.code, for exampleTRANSACTION_EXPIREDandSYNC_PROOF_REQUIRED.
See Error handling for the full taxonomy.
Idempotency
POST /v2/intents/onramp and POST /v2/intents/offramp accept an
idempotency-key header (UUID). POST /v2/wallets and
POST /v2/wallets/:id/submit require the header. The same key and body
within the deduplication window return the same response. A different body
with the same key returns 409. See
Idempotency.
POST /v2/intents/:id/approve-burn is the exception — the on-chain
txSignature is the dedup key, and no separate header is sent.
Versioning
/v2 is the current stable surface. Breaking changes ship under a new
version prefix; no silent changes to existing endpoints.
Resources
Burn signing
Ask Nora to stage an unsigned user_burn transaction, have the user's wallet sign it, broadcast it on Solana, and submit the signature back via /v2/intents/:id/approve-burn.
Intents
Create onramp / offramp intents, fetch and list them, submit the user_burn transaction signature for offramps.