GET /v2/inscribe/order/summary remains supported. All other /v2/inscribe/* endpoints are deprecated. New integrations must use /v5/inscribe/*; deprecated V2 endpoints are retained only for existing clients while they migrate.
V5 uses the same bearer API key. When OpenAPI mode is enabled, every V5 order is scoped to the calling API application, so an order ID cannot be queried or operated on by another application.
| Deprecated V2 endpoint | V5 replacement | Migration note |
|---|---|---|
GET /v2/inscribe/order/summary |
GET /v5/inscribe/fees-config and GET /v5/inscribe/order/list |
V5 has no status-count summary. Use the order list for order state and fees-config for fee and eligibility data. |
GET /v2/inscribe/order/list |
GET /v5/inscribe/order/list |
Send cursor, size, and a JSON-encoded filter query parameter. |
GET /v2/inscribe/order/{orderId} |
GET /v5/inscribe/order/{orderId} |
V5 adds availableActions, availablePaymentMethods, outputValueFee, and optional compactFiles. |
POST /v2/inscribe/order/create |
POST /v5/inscribe/order/create |
Replace receiveAddress with receiver; supply clientId, refundAddress, userAddress, and userPubkey. |
POST /v2/inscribe/order/request-commit |
POST /v5/inscribe/order/request-commit |
V5 requires payerAddress and payerPubkey. |
POST /v2/inscribe/order/sign-commit |
POST /v5/inscribe/order/sign-commit |
The signed PSBT remains in psbt. |
POST /v2/inscribe/order/sign-reveal |
POST /v5/inscribe/order/sign-reveal |
The signed PSBT remains in psbt. |
POST /v2/inscribe/order/{orderId}/refund-estimate |
POST /v5/inscribe/refund/estimate |
Move orderId from the path into the JSON body. |
POST /v2/inscribe/order/{orderId}/refund |
POST /v5/inscribe/refund |
Move orderId into the JSON body and rename refundFeeRate to feeRate. |
| Deprecated V2 endpoint | V5 replacement |
|---|---|
POST /v2/inscribe/order/create/brc20-deploy |
POST /v5/inscribe/order/create |
POST /v2/inscribe/order/create/brc20-mint |
POST /v5/inscribe/order/create or POST /v5/inscribe/order/repeat for a supported prior mint order |
POST /v2/inscribe/order/create/brc20-transfer |
POST /v5/inscribe/order/create |
POST /v2/inscribe/order/create/brc20-5byte-mint |
POST /v5/inscribe/order/create/brc20-5byte-mint |
POST /v2/inscribe/order/request-commit/brc20-5byte-mint |
No V5 replacement. This signing step is not publicly available. |
POST /v2/inscribe/order/sign-commit/brc20-5byte-mint |
No V5 replacement. This signing step is not publicly available. |
POST /v2/inscribe/order/sign-reveal/brc20-5byte-mint |
No V5 replacement. This signing step is not publicly available. |
POST /v2/inscribe/order/create/runes-etch |
POST /v5/inscribe/order/create/runes-etch |
POST /v2/inscribe/order/create/runes-mint |
POST /v5/inscribe/order/create/runes-mint |
For ordinary BRC-20 deploy, mint, and transfer inscriptions in V5, use the generic create endpoint and provide the protocol JSON as a files[].dataURL inscription. Use the dedicated V5 endpoints for 5-byte minting, Runes, Alkanes, Clockin, and multi-protocol minting.
receiver instead of V2’s receiveAddress for order creation.clientId and refundAddress. Generic V5 creation also requires userAddress and userPubkey.devAddress (developer fee recipient) and devFee (developer fee in sats) on supported quote and order creation endpoints. Include both fields when charging a developer fee./v5/inscribe/order/quote/* endpoint where available. Quotes do not create order state.availablePaymentMethods and availableActions on the V5 order. They are the supported source for direct payment, Request-Commit, cancellation, and pause availability; acceleration endpoints are not publicly available.See the generated Inscribe API V5 reference for the complete request and response schemas.