Introduction - Scrip Docs

The Scrip API is a REST API. All requests and responses use JSON. The current version is v1. There are no client libraries yet: every example is plain HTTP, and you can generate a client from the OpenAPI spec or point AI tools at the AI resources.

https://api.scrip.dev/v1

If you’re new to Scrip, start with the Quickstart to create a program and process your first event, or read Core Concepts for an overview of the data model.

Authentication

Every request requires an API key in the Authorization header:

curl https://api.scrip.dev/v1/programs \
  -H "Authorization: Bearer sk_your_api_key" \
  -H "Content-Type: application/json"

Keys use the sk_ prefix and have full read/write access to all resources in your organization. The request examples on each endpoint page send the same key in the X-API-Key header instead. Both headers work on every endpoint and authenticate the key identically; if a request carries both, the Authorization: Bearer value is used. Create and manage keys from the Scrip dashboard. See the Authentication page for details on key management and rate limits.

Conventions

Convention	Detail
Property names	`snake_case`
IDs	UUIDs (`550e8400-e29b-41d4-a716-446655440000`)
Timestamps	RFC 3339 (`2024-01-15T10:30:00Z`)
Amounts	Strings to preserve decimal precision (`"100.00"`)
Content type	`application/json` for all request and response bodies

Idempotency

Events, balance operations (hold, release, forfeit), redemptions, reversals, and transfers accept an idempotency_key field. Use deterministic keys derived from your domain data (order-12345-completed), not random UUIDs. Balance operations (adjust, hold, release, forfeit, and void-hold, for both participants and groups) also accept the standard Idempotency-Key HTTP header as an alternative to the body field:

Header only: the header value is used as the idempotency key.
Body only: the body value is used (unchanged behavior).
Both, equal: treated as one key.
Both, different: 400 with reason header_body_mismatch. The API never silently picks one.

Header values must be 1–255 printable ASCII characters. Malformed values are rejected with a 400 whose details carry a reason: empty, too_long, invalid_characters, or multiple_values. On event ingestion endpoints, the idempotency key is carried only by the body field; a well-formed Idempotency-Key header is ignored there, though malformed values are still rejected. Events use the idempotency key as the logical event identity:

Reusing the same program_id + idempotency_key returns the same event identity without reprocessing, even if the payload differs.
To correct or replace an event, send a new event with a new idempotency key.

Other idempotent operations compare the request payload:

Same key + same payload: returns the original response without reprocessing.
Same key + different payload: returns 409 Conflict with code idempotency_conflict.

Keys are scoped to program_id. For operations that compare payloads, comparison uses a SHA-256 hash of semantic fields. Cosmetic differences (JSON key order, trailing decimal zeros, whitespace) are normalized before hashing, so they will not trigger a conflict. Automation creation does not accept an idempotency key. Automation names are unique per program, so a retried create returns a name-conflict error rather than a duplicate; the events an automation fires carry their own deterministic idempotency keys.

Pagination

List endpoints return paginated results using cursor-based pagination:

{
  "data": [
    { "id": "...", "name": "..." }
  ],
  "pagination": {
    "has_more": true,
    "next_cursor": "eyJ..."
  }
}

Pass cursor as a query parameter to fetch the next page. Use limit to control page size (default 50, max 200). Pagination is stable across concurrent modifications. Inserts and deletes between pages do not cause skipped or duplicated results.

Filtering, sorting, and search

Most list endpoints support query parameters for filtering and ordering results. Available parameters vary by endpoint and are documented in each endpoint’s parameter table.

Filtering

Filter by resource status or related IDs:

GET /v1/participants?status=ACTIVE&program_id=550e8400-...
GET /v1/events?status=COMPLETED&from=2025-01-01T00:00:00Z&to=2025-02-01T00:00:00Z

Time-range filters (from, to) accept RFC 3339 timestamps and filter on the resource’s creation time. from is required when to is provided, and from must be before to.

Sorting

Control result ordering with sort_by and sort_dir:

GET /v1/programs?sort_by=name&sort_dir=asc
GET /v1/events?sort_by=event_timestamp&sort_dir=desc

Each endpoint defines its own set of sortable fields (e.g., created_at, name, order). The default sort is typically created_at descending. Rules default to order ascending.

Search

Search uses case-insensitive partial matching. The searched field varies by resource:

Resource	Searched fields
Participants	`external_id`
Programs, Rules	`name`
Assets	`name` and `symbol`

GET /v1/participants?search=user_abc
GET /v1/rules?search=welcome

Errors

Error responses include a machine-readable code and a human-readable message:

{
  "code": "not_found",
  "message": "Program not found"
}

Some errors include a details object with field-level validation information:

{
  "code": "validation_error",
  "message": "Invalid request body",
  "details": {
    "name": "is required",
    "key": "must be lowercase alphanumeric with hyphens"
  }
}

Status codes

Code	Meaning
`200`	Success
`201`	Resource created
`202`	Accepted for async processing (events)
`204`	Success, no content
`400`	Bad request or validation error
`401`	Unauthorized
`403`	Forbidden
`404`	Resource not found
`409`	Conflict (state violation, duplicate idempotency key, reversal exceeds remaining)
`422`	Business rule violation (insufficient funds, inactive resource)
`429`	Rate limit exceeded
`500`	Internal server error
`502`	The gift-card vendor rejected or failed a request
`503`	Gift cards or an upstream fulfillment service are temporarily unavailable

Error codes

The code field in error responses is a machine-readable string you can match on programmatically. Common codes by category:

Validation (400)

Code	Description
`validation_error`	One or more fields failed validation. Check `details` for field-level errors
`invalid_request`	Request structure is invalid (e.g., mutually exclusive fields provided)
`invalid_amount`	Amount is malformed or non-positive
`invalid_scale`	A redemption amount has more decimal places than the asset’s `scale`. Balance operations report the same problem as `bad_request` with `details.reason: invalid_scale`. See Money amounts end to end
`amount_precision_exceeded`	A numeric value in `event_data` exceeds the precision-safe range (magnitude above 2^53). Send very large values as strings
`bad_request`	Malformed request, including invalid `Idempotency-Key` header values (reason: `empty`, `too_long`, `invalid_characters`, `multiple_values`) or a header that conflicts with the body `idempotency_key` (reason: `header_body_mismatch`)
`invalid_quantity`	Quantity must be a positive integer
`asset_not_linked`	Asset is not linked to the specified program
`reward_program_mismatch`	Reward does not belong to the specified program

Authentication & authorization (401 / 403)

Code	Description
`unauthorized`	Missing or invalid API key / JWT
`forbidden`	Valid credentials but insufficient permissions for this action

Not found (404)

Code	Description
`not_found`	The requested resource does not exist

Conflict (409)

Code	Description
`participant_inactive`	Participant is `SUSPENDED` or `CLOSED`. Financial operations and counter updates are blocked for inactive participants
`idempotency_conflict`	Idempotency key was already used with different parameters
`redemption_already_resolved`	A pending redemption already reached a different terminal outcome
`reservation_expired`	Capture reached or passed the reservation’s effective deadline
`redemption_not_completed`	Reversal was requested for a pending, failed, or cancelled redemption
`already_reversed`	Redemption has already been fully reversed
`quantity_exceeds_remaining`	Reversal quantity exceeds the remaining reversible units
`amount_exceeds_remaining`	Reversal amount exceeds the remaining reversible amount
`max_total_exceeded`	Reward’s global inventory limit reached
`max_per_participant_exceeded`	Reward’s per-participant inventory limit reached
`program_archived`	Program is archived and cannot be modified
`program_suspended`	Program is suspended and cannot process transactions
`key_exists`	A tier key or reward name already exists in this program
`tier_referenced_by_rules`	Tier cannot be archived while `ACTIVE` or `SUSPENDED` rules reference its key. The error details list the referencing rules
`fulfillment_managed`	A pending gift-card fulfillment redemption can’t be completed directly; it captures only when the vendor order executes
`fulfillment_in_progress`	A gift-card fulfillment can only be failed or cancelled while it is still `PENDING` or `AWAITING_FUNDS` with no vendor order
`fulfillment_delivered`	A redemption can’t be reversed once its gift card has already been delivered
`claim_link_not_ready`	The gift-card fulfillment hasn’t succeeded yet; retry shortly
`auto_managed_item`	A reward created by a reward source can’t be edited directly; update its reward source or product settings instead
`reward_source_exists`	A live reward source already exists for this program, account, and asset
`catalog_reconcile_conflict`	The reward source changed while this request was being applied; retry

Business rules (422)

Code	Description
`insufficient_funds`	Not enough balance for the requested operation
`fulfillment_window_too_short`	Effective pending-redemption deadline is less than 60 seconds away
`fulfillment_window_too_long`	Request or program deadline exceeds the 365-day system limit
`asset_not_reservable`	Asset inventory mode cannot back a pending redemption
`asset_archived`	Asset is archived and cannot be used in new operations
`program_inactive`	Program is not active; accepted events fail during async processing
`participant_not_found`	Participant does not exist and the program is configured to reject unknown participants
`participant_suspended`	Event actor or recipient is `SUSPENDED` (or otherwise not active); the event is rejected at ingestion before rules run
`participant_closed`	Event actor or recipient is `CLOSED`; the event is rejected at ingestion before rules run
`recipient_not_found`	Target participant not found or not enrolled in the program
`fulfillment_capture_conflict`	`capture: true` was combined with a `fulfillment` block
`fulfillment_required`	A gift-card reward was redeemed without a `fulfillment` block
`fulfillment_not_supported`	A `fulfillment` block was supplied for a non-gift-card reward
`provider_connection_unavailable`	The reward’s fulfillment account is not `ACTIVE`
`fulfillment_face_value_cap_exceeded`	Redemption face value exceeds the program’s `fulfillment_max_face_value_minor`
`fulfillment_participant_count_cap_exceeded`	Participant reached the program’s rolling fulfillment count cap
`fulfillment_participant_amount_cap_exceeded`	Participant reached the program’s rolling fulfillment amount cap
`claim_link_not_applicable`	The redemption has no gift-card fulfillment to claim
`claim_link_fulfillment_failed`	The gift-card order failed, so there is no card to claim
`claim_link_unsupported`	The vendor doesn’t support claim-link delivery

Gift-card vendor errors (502)

A transient claim-link failure returns 503 with code: "provider_unavailable"; retry with backoff. Other claim-link failures return 502 with code: "claim_link_provider_error" and may require investigation. 503 provider_connections_not_configured means claim-link creation is unavailable; contact support.

Rate limits

Requests are rate-limited per organization at 10 requests/second with burst to 30. All API keys in the same organization share one rate limit bucket. Every response includes X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers. When exceeded, the API returns 429 with a Retry-After header. See Authentication for the full header reference.

Resources

Your app calls a short list of these as users earn and redeem: events, balances, the rewards catalog, redemptions, transfers, and webhooks. The rest create or change the program itself, which is the dashboard’s job day to day. Which endpoints you need sorts them.

Resource	Prefix	Description
Programs	`/v1/programs`	Top-level containers for incentive logic
Assets	`/v1/assets`	Units of value (points, credits, cashback)
Participants	`/v1/participants`	Users who earn and spend
Groups	`/v1/groups`	Collections of participants
Rules	`/v1/rules`	CEL conditions and reward actions
Events	`/v1/events`	Signals that trigger rule evaluation
Tiers	`/v1/programs/{id}/tiers`	Status hierarchies for participants
Redemptions	`/v1/participants/{id}/redemptions`	Instant and asynchronous balance spend operations
Rewards	`/v1/programs/{id}/rewards`	Catalog items for redemption
Gift cards	`/v1/fulfillment-accounts`	Fulfillment accounts, reward sources, and product settings for gift-card rewards
Transfers	`/v1/transfers`	Value movement between participants and groups
Automations	`/v1/programs/{id}/automations`	Stored event submissions fired on a cron schedule, at a one-time moment, or on participant state
Reporting	`/v1/reports`	Liability reports, summaries, and the journal

For a complete map of entities and their relationships, see the Data Model.

​Authentication

​Conventions

​Idempotency

​Pagination

​Filtering, sorting, and search

​Filtering

​Sorting

​Search

​Errors

​Status codes

​Error codes

​Validation (400)

​Authentication & authorization (401 / 403)

​Not found (404)

​Conflict (409)

​Business rules (422)

​Gift-card vendor errors (502)

​Rate limits

​Resources

Authentication

Conventions

Idempotency

Pagination

Filtering, sorting, and search

Filtering

Sorting

Search

Errors

Status codes

Error codes

Validation (400)

Authentication & authorization (401 / 403)

Not found (404)

Conflict (409)

Business rules (422)

Gift-card vendor errors (502)

Rate limits

Resources