Skip to main content
POST
Redeem a catalog item
Creates a redemption for a reward in the program catalog. For custom UNIT_BASED rewards, specify quantity (defaults to 1); for AMOUNT_BASED rewards, specify amount. Set capture: true to capture immediately, capture: false to authorize into PENDING, or omit it to use the program’s fulfillment_mode. Instant capture debits AVAILABLE and credits the redemption target in one REDEMPTION journal entry. Authorization moves the calculated cost to HELD in a HOLD journal entry and returns reservation_id plus the effective expires_at. Use expires_at or ttl_seconds to bound a pending redemption; they are mutually exclusive. For custom UNIT_BASED rewards, both paths commit catalog inventory immediately, so committed_units includes units still awaiting fulfillment. Pass an idempotency_key to safely retry requests. Duplicate requests return 200 with the existing redemption instead of 201. To protect a price shown before confirmation, send expected_amount as the total cost in asset units. Scrip compares it with the calculated cost before reserving or spending assets. A mismatch returns 409 reward_price_changed without creating a redemption. Refresh the catalog and confirm the new cost before submitting again. A retry of an existing redemption compares against its original amount; a different expected amount returns 409 idempotency_conflict.

Gift cards

Include fulfillment to order the selected gift card. Scrip reserves the cost, places the order, and captures the balance after the order succeeds. This applies regardless of the program’s fulfillment_mode; capture: true returns 422 fulfillment_capture_conflict. For fixed-value cards, include the reviewed fulfillment.face_value_minor and fulfillment.currency as well as expected_amount. If the configured value or currency changed, Scrip returns 422 fulfillment_face_value_mismatch before placing an order. The request waits up to about 30 seconds for the order to finish. Send Prefer: respond-async to return immediately. HTTP 201 means the redemption was created; check the response’s status for its outcome. A successful response may include fulfillment.claim_url. If the link is missing, use Create a claim link for the same redemption. Retrying the original request with its idempotency key returns the existing redemption and may wait again for the outcome.
For deadline selection and resolution endpoints, see the Redemption lifecycle guide. For committed, pending, and delivered inventory, see Rewards Catalog. For a complete gift-card example, see Gift cards.

Authorizations

X-API-Key
string
header
required

API key passed in the X-API-Key header.

Path Parameters

id
string<uuid>
required

Participant ID

Body

application/json

Catalog item redemption details

program_id
string<uuid>
required

The program this redemption belongs to

Example:

"550e8400-e29b-41d4-a716-446655440000"

reward_id
string<uuid>
required

The reward catalog item to redeem

Example:

"550e8400-e29b-41d4-a716-446655440001"

amount
string

Asset amount for custom AMOUNT_BASED rewards. For managed rewards, supply fulfillment.face_value_minor instead.

Example:

"50.00"

capture
boolean

Whether to capture immediately. True completes instantly, false authorizes, and omission uses the program fulfillment_mode.

Example:

false

description
string

Optional context for this redemption, used in journal entries (max 500 chars)

Example:

"Gift card redemption"

expected_amount
string

Expected total cost in asset units. If the current cost differs, no redemption is created (409 reward_price_changed). Retries compare against the original redemption's amount.

Example:

"50.00"

expires_at
string<date-time>

Absolute pending-redemption deadline (RFC3339); alternative to ttl_seconds and limited to one year. If no request or program deadline is set, the authorization defaults to 90 days.

Example:

"2024-01-15T11:30:00Z"

fulfillment
object

Order details for managed rewards. Required when the reward includes fulfillment; capture: true is unsupported.

idempotency_key
string

Prevents duplicate redemptions when retrying requests

Example:

"redeem-item-12345"

quantity
integer

Number of units to redeem. Defaults to 1; managed rewards require exactly 1.

Example:

2

ttl_seconds
integer

Relative pending-redemption deadline in seconds; alternative to expires_at and limited to one year. If no request or program deadline is set, the authorization defaults to 90 days.

Example:

3600

Response

Duplicate request (idempotency key matched, returns existing record)

amount
string

Total amount debited from the participant's balance (decimal string)

Example:

"1000.00"

asset_id
string<uuid>

The asset that was debited

Example:

"550e8400-e29b-41d4-a716-446655440003"

capture_journal_entry_id
string<uuid>

Ledger entry that captured a pending redemption

Example:

"550e8400-e29b-41d4-a716-446655440007"

captured_at
string<date-time>

When the pending redemption was captured

Example:

"2024-01-15T10:45:00Z"

created_at
string<date-time>

When this redemption was created

Example:

"2024-01-15T10:30:00Z"

description
string

Context for this redemption, used in journal entries

Example:

"Redeemed: Gift Card"

expires_at
string<date-time>

Effective deadline of the backing reservation. Always present for pending redemptions; defaults to 90 days and may be configured up to one year.

Example:

"2024-01-15T11:30:00Z"

failure_reason
string

Machine-readable or operator-supplied terminal failure detail

Example:

"fulfillment_failed"

fulfillment
object

Gift-card vendor order status, present only for provider-backed (fulfillment) redemptions

id
string<uuid>

Unique identifier for this redemption

Example:

"550e8400-e29b-41d4-a716-446655440000"

journal_entry_id
string<uuid>

Immutable ledger anchor: the hold entry for pending redemptions, otherwise the instant redemption entry

Example:

"550e8400-e29b-41d4-a716-446655440005"

participant_id
string<uuid>

The participant who redeemed

Example:

"550e8400-e29b-41d4-a716-446655440002"

program_id
string<uuid>

The program this redemption belongs to

Example:

"550e8400-e29b-41d4-a716-446655440001"

quantity
integer

Number of units redeemed (catalog redemptions only)

Example:

2

release_journal_entry_id
string<uuid>

Ledger entry that released a pending redemption's reserved value back to AVAILABLE. Present only on FAILED and CANCELLED redemptions whose reservation resolved RELEASED; null while PENDING, after capture (see capture_journal_entry_id), and when every reserved lot had already expired before release (the reservation resolved EXPIRED and no release entry was posted).

Example:

"550e8400-e29b-41d4-a716-446655440008"

released_amount
string

Amount the release entry returned to AVAILABLE (decimal string). Equals the authorized amount unless part of the reserved value expired before release, in which case only the live remainder is reported. Present exactly when release_journal_entry_id is present.

Example:

"1000.00"

reservation_id
string<uuid>

Reservation backing a pending redemption

Example:

"550e8400-e29b-41d4-a716-446655440006"

resolved_at
string<date-time>

When the pending redemption reached a terminal state

Example:

"2024-01-15T10:45:00Z"

reversed_amount
string

Cumulative amount reversed so far (decimal string)

Example:

"0.00"

reversed_quantity
integer

Cumulative units reversed so far (UNIT_BASED catalog redemptions only)

Example:

0

reward_id
string<uuid>

The reward catalog item that was redeemed (catalog redemptions only)

Example:

"550e8400-e29b-41d4-a716-446655440004"

status
enum<string>

Current lifecycle and reversal state

Available options:
PENDING,
COMPLETED,
FAILED,
CANCELLED,
PARTIALLY_REVERSED,
FULLY_REVERSED
Example:

"COMPLETED"

unit_cost
string

Cost per unit at the time of redemption (catalog redemptions only, decimal string)

Example:

"500.00"

updated_at
string<date-time>

When this redemption was last updated (e.g., after a reversal)

Example:

"2024-01-15T10:30:00Z"