Authorize an exact offer

POST

/v1/offers/{id}/exact-authorizations

const url = 'https://api.digirare.com/v1/offers/example/exact-authorizations';
const options = {
  method: 'POST',
  headers: {'x-session-token': '<x-session-token>', 'Content-Type': 'application/json'},
  body: '{"utxo_txid":"example","utxo_vout":1,"fee_rate":1}'
};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request POST \
  --url https://api.digirare.com/v1/offers/example/exact-authorizations \
  --header 'Content-Type: application/json' \
  --header 'x-session-token: <x-session-token>' \
  --data '{ "utxo_txid": "example", "utxo_vout": 1, "fee_rate": 1 }'

Buyer composes an exact-target transaction over a known asset outpoint. Nothing is reserved; the returned input-0 ALL signature request becomes a unilateral seller-executable authorization only after bidder-psbt submission. expires_at is a marketplace serving deadline, not Bitcoin signature expiry; spending the shared funding outpoint is the on-chain invalidation mechanism. The seller read endpoint requotes current fees and, when necessary, supplies a seller-funded CPFP child. The seller is the taker: platform_fee_sats is the fee output platformFeeSats(price_sats), prefunded_fee_sats is the part a legacy bidder-pays slot already funded (0 for every new offer), and seller_proceeds_sats = price_sats + asset UTXO - (platform_fee_sats - prefunded_fee_sats) - network_fee_sats. platform_fee_internal_key (see the PlatformFeeInternalKey schema) is the fee output’s x-only Taproot internal key, derived server-side, on this and every exact-authorization template response (batch and seller read).

Authorizations

session

Parameters

Path Parameters

required

string

>= 1 characters

Request Body^required

application/json

object

utxo_txid

required

string

/^[0-9a-f]{64}$/

utxo_vout

required

integer

fee_rate

number

>= 0.1 <= 500

Example^generated

{
  "utxo_txid": "example",
  "utxo_vout": 1,
  "fee_rate": 1
}

Responses

201

Successful createExactOfferAuthorization response.

application/json

object

result

required

object

operation_id

required

string

protocol_version

required

string

Allowed value: exact_offer_v1

authorization_id

required

string

status

required

string

Allowed values: awaiting_bidder active

funding_slot_id

required

string

bidder

required

string

psbt_hex

required

Always the UNSIGNED settlement template, for both roles. The buyer’s input-0 signature is never served to the seller; the market merges it server-side when the seller submits input 1.

string

expected_txid

required

string

signing

required

object

psbt_hex

string

inputs_to_sign

required

Any of:

Array<number>
string

Array<number>

signer_address

string

sighash

string

Allowed values: ALL DEFAULT|ALL SINGLE|ANYONECANPAY

expected_txid

string

target

required

object

asset

required

string

quantity_raw

required

Counterparty atomic units. A string preserves integers beyond JSON’s safe numeric range; divisibility affects display, never this wire value.

string

/^[0-9]+$/

seller

required

string

outpoint

required

object

txid

required

string

vout

required

number

price_sats

required

Integer satoshis, exactly representable as a JSON number. Aggregated historical volume can exceed Bitcoin’s supply, so this is the safe JSON integer ceiling, not a single-transaction spending limit.

integer

<= 9007199254740991

seller_proceeds_sats

required

integer

<= 9007199254740991

network_fee_sats

required

integer

<= 9007199254740991

platform_fee_sats

required

integer

<= 9007199254740991

platform_fee_internal_key

Hex x-only BIP86 internal key of the marketplace fee output, derived server-side from the fee allocation’s own index. The fee output is exactly the key-path-only P2TR of this key; a wallet that reads it checks that match and shows the fee payment either way. Absent when there is no key to vouch for (a pre-fee template or an unconfigured/rotated key).

string

prefunded_fee_sats

required

integer

<= 9007199254740991

fee_rate

required

number

delivery

required

object

mode

required

string

Allowed values: detached attached

address

required

string

utxo_value_sats

integer

<= 9007199254740991

signature_validity

required

object

marketplace_expires_at

required

number

bitcoin_expires_at

required

null

bitcoin_invalidation

required

object

type

required

string

Allowed value: spend_funding_outpoint

outpoint

required

object

txid

required

string

vout

required

number

fee_adjustment

Any of:

object

state

required

string

Allowed value: ready

signed_parent_fee_rate

required

number

current_target_fee_rate

required

number

parent_fee_sats

required

integer

<= 9007199254740991

package_fee_sats

required

integer

<= 9007199254740991

package_fee_rate

required

number

final_seller_proceeds_sats

required

integer

<= 9007199254740991

cpfp

object

psbt_hex

required

string

expected_txid

required

string

signing

required

object

psbt_hex

string

inputs_to_sign

required

Any of:

Array<number>
string

Array<number>

signer_address

string

sighash

string

Allowed values: ALL DEFAULT|ALL SINGLE|ANYONECANPAY

expected_txid

string

expires_at

required

number

reserves_funding

boolean

requires_buyer_action

boolean

Example

{
  "result": {
    "protocol_version": "exact_offer_v1",
    "status": "awaiting_bidder",
    "signing": {
      "inputs_to_sign": "all",
      "sighash": "ALL"
    },
    "delivery": {
      "mode": "detached"
    },
    "signature_validity": {
      "bitcoin_invalidation": {
        "type": "spend_funding_outpoint"
      }
    },
    "fee_adjustment": {
      "state": "ready"
    },
    "cpfp": {
      "signing": {
        "inputs_to_sign": "all",
        "sighash": "ALL"
      }
    },
    "reserves_funding": false,
    "requires_buyer_action": false
  }
}

4XX

Stable machine-readable failure

application/json

object

error

required

string

code

required

string

Allowed values: invalid_request unsupported_address_type unauthenticated forbidden not_found method_not_allowed state_changed expired invalid_transaction rate_limited internal_error upstream_unavailable service_unavailable checkout_changed target_unavailable signature_invalid template_mismatch mempool_rejected broadcast_unknown conflict_spend duplicate_funding_slot offer_selection_unavailable attached_delivery_single_item_only insufficient_funds insufficient_asset_balance price_below_minimum listing_price_above_maximum counter_price_invalid self_trade offer_capacity_full open_offer_limit policy_offer_refused

retryable

boolean

mempool_policy

On 422 mempool_rejected from a broadcast: which deterministic node policy refused the bytes. Retrying the same bytes fails the same way. fee_floor: re-quote at a higher fee_rate. chain_too_long: too many unconfirmed ancestors; wait for a confirmation, then retry. truc: a version-3 (TRUC) package rule, such as spending an unconfirmed version-3 output; wait for a confirmation, then retry.

string

Allowed values: fee_floor chain_too_long truc dust nonstandard

mempool_reason

The node’s own reject reason, on mempool_rejected (422) and on state_changed (409) when a broadcast lost to a conflicting or replacing spend.

string

wait_for_confirmation

Present and true when mempool_policy is chain_too_long or truc.

boolean

claims_released

On a checkout or accept completion refused as mempool_rejected: the journaled settlement ended and every listing, bid, and asset claim it held was released (its inputs were proven unspent). The quote or accept is replaced; request a new one.

boolean

refused_listings

Batch listing routes only: every refused item. The first sets the status and code.

Array<object>

One refused item in a batch refusal’s refused_listings array. Nothing in the batch was changed.

object

index

required

integer

listing_id

required

string

status

required

integer

code

required

string

error

required

string

key

additional properties

any

retry_after_seconds

On 429 rate_limited: the exact seconds until the oldest counted request leaves the window; a retry then is admitted (also sent as Retry-After). Limited writes are bucketed per route scope in exact sliding 60-second windows: by session address when a valid x-session-token is present, otherwise by IP, with a per-IP ceiling across sessions. Expensive writes: 20, ceiling 120. Signed completions: 120, ceiling 600. Session minting (/auth/*): 60 per IP. A request refused by any bucket is counted by none.

integer

>= 1

key

additional properties

any

Example

{
  "code": "invalid_request",
  "mempool_policy": "fee_floor"
}

5XX

Stable machine-readable failure

application/json

object

error

required

string

code

required

string

retryable

boolean

mempool_policy

string

Allowed values: fee_floor chain_too_long truc dust nonstandard

mempool_reason

The node’s own reject reason, on mempool_rejected (422) and on state_changed (409) when a broadcast lost to a conflicting or replacing spend.

string

wait_for_confirmation

Present and true when mempool_policy is chain_too_long or truc.

boolean

claims_released

boolean

refused_listings

Batch listing routes only: every refused item. The first sets the status and code.

Array<object>

One refused item in a batch refusal’s refused_listings array. Nothing in the batch was changed.

object

index

required

integer

listing_id

required

string

status

required

integer

code

required

string

error

required

string

key

additional properties

any

retry_after_seconds

integer

>= 1

key

additional properties

any

Example

{
  "code": "invalid_request",
  "mempool_policy": "fee_floor"
}

Authorize an exact offer

Authorizations

Parameters

Path Parameters

Request Bodyrequired

Examplegenerated

Responses

201

Example

4XX

Example

5XX

Example

Request Body^required

Example^generated