> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scrip.dev/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Before planning an integration, read https://docs.scrip.dev/which-endpoints-you-need.md. It lists the calls an app makes as users earn and redeem, such as sending and reversing events, reading balances, and redeeming rewards. Every other endpoint creates or changes the program itself, and the dashboard at https://app.scrip.dev is the usual place for that work.
> Gift cards are rewards in the program's rewards catalog, next to custom rewards. Redeem one with `POST /v1/participants/{id}/redemptions/items` and a `fulfillment` object. When the order succeeds, show the participant the claim link from `fulfillment.claim_url` in the redemption response or from `POST /v1/redemptions/{id}/claim-link`. An order can finish after the request returns, so handle the `redemption.fulfillment_succeeded` and `redemption.fulfillment_failed` webhooks. See https://docs.scrip.dev/guides/gift-cards.md.
> Give every event, redemption, and transfer an `idempotency_key` built from your own data, such as an order ID, so retries are safe. Keep API keys on your server.
> Request and response schemas are in https://docs.scrip.dev/openapi.json. Add `.md` to any docs URL to get the page as Markdown.

# List fulfillment accounts

> List the organization's fulfillment accounts.

List the fulfillment accounts connected to your organization. Use an account's `id` when creating a reward source. You can have one live account per vendor.

Only an `ACTIVE` account accepts new redemptions. This status does not indicate whether the account has enough funds for an order. Connect, fund, and manage accounts in the Scrip dashboard.

<Note>
  See [Gift-card setup](/guides/gift-cards#set-up) for how account funding and participant balances work together.
</Note>


## OpenAPI

````yaml GET /v1/fulfillment-accounts
openapi: 3.0.3
info:
  contact:
    email: support@scrip.dev
    name: Scrip Support
  description: >-
    Scrip is the operating system for rewards programs. Use this REST API to
    define earn and redemption rules, issue and redeem assets, and track every
    movement in a double-entry ledger. Full guides and reference:
    https://docs.scrip.dev


    Core concepts:

    - **Programs**: Containers for incentive logic (e.g., "Q1 Sales Bonus",
    "Customer Loyalty")

    - **Assets**: The currency or points being tracked (e.g., "Bonus Points",
    "Cash Rewards")

    - **Participants**: Users who earn and spend assets (identified by
    external_id)

    - **Groups**: Collections of participants for team-based incentives

    - **Rules**: Automated reward logic triggered by events

    - **Events**: Actions that trigger rule evaluation (e.g., "purchase",
    "referral")


    Response formats:

    - **Collection endpoints** return: {"data": [...], "pagination":
    {"has_more": true, "next_cursor": "..."}}

    - **Single-resource endpoints** return the resource directly

    - **Errors** return: {"code": "...", "message": "...", "details": {...}} —
    `details` is an optional object, present on input errors only
  license:
    name: Proprietary
  termsOfService: https://scrip.dev/terms
  title: Scrip API
  version: '1.0'
servers:
  - url: https://api.scrip.dev
security: []
tags:
  - description: >-
      Manage incentive programs. Programs are the top-level container for all
      incentive logic.
    name: Programs
  - description: >-
      Manage asset types (currencies, points). Assets define what participants
      can earn and spend.
    name: Assets
  - description: >-
      Manage participants and their balances. Participants are identified by
      external_id from your system.
    name: Participants
  - description: Manage participant groups for team-based incentives.
    name: Groups
  - description: >-
      Manage automated reward rules. Rules define conditions and actions
      triggered by events.
    name: Rules
  - description: Ingest events that trigger rule evaluation and reward distribution.
    name: Events
  - description: Transfer assets between participants.
    name: Transfers
  - description: Access ledger summaries and program activity reports.
    name: Reporting
  - description: >-
      Redeem participant balances for rewards. Supports raw amount redemptions
      and catalog item redemptions.
    name: Redemptions
  - description: >-
      Manage the reward catalog. Create and manage redeemable items with
      inventory tracking.
    name: Rewards
  - description: >-
      Schedule and manage automated event dispatching. Automations generate
      events on cron schedules, at specific times, or by evaluating participant
      state.
    name: Automations
  - description: >-
      Manage tier types and levels within programs. Tiers define status
      hierarchies that participants progress through based on qualification
      rules.
    name: Tiers
  - description: Inspect double-entry ledger records for auditing and reconciliation.
    name: Journal Entries
  - description: >-
      Manage webhook endpoints and delivery logs. Webhooks notify your
      application of real-time events via HTTP POST with HMAC-SHA256 signatures.
    name: Webhooks
paths:
  /v1/fulfillment-accounts:
    get:
      tags:
        - Fulfillment Accounts
      summary: List fulfillment accounts
      description: List the organization's fulfillment accounts.
      operationId: listFulfillmentAccounts
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/handlers.providerConnectionListResponse'
          description: OK
        '401':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/handlers.ErrUnauthorizedResponse'
          description: 'Missing or invalid credentials (code: unauthorized)'
        '403':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/handlers.ErrForbiddenResponse'
          description: 'Insufficient permissions (code: forbidden)'
        '500':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/handlers.ErrInternalResponse'
          description: 'Internal server error (code: internal_error)'
      security:
        - ApiKeyAuth: []
        - BearerAuth: []
components:
  schemas:
    handlers.providerConnectionListResponse:
      properties:
        data:
          items:
            $ref: '#/components/schemas/handlers.providerConnectionResponse'
          type: array
      type: object
    handlers.ErrUnauthorizedResponse:
      properties:
        code:
          description: Code is the machine-readable error code
          example: unauthorized
          type: string
        details:
          allOf:
            - $ref: '#/components/schemas/handlers.ErrorDetails'
          description: Details provides optional structured error context
        message:
          description: Message is the human-readable error description
          example: Missing or invalid credentials
          type: string
      type: object
    handlers.ErrForbiddenResponse:
      properties:
        code:
          description: Code is the machine-readable error code
          example: forbidden
          type: string
        details:
          allOf:
            - $ref: '#/components/schemas/handlers.ErrorDetails'
          description: Details provides optional structured error context
        message:
          description: Message is the human-readable error description
          example: Insufficient permissions for this action
          type: string
      type: object
    handlers.ErrInternalResponse:
      properties:
        code:
          description: Code is the machine-readable error code
          example: internal_error
          type: string
        message:
          description: Message is the human-readable error description
          example: An internal error occurred
          type: string
      type: object
    handlers.providerConnectionResponse:
      properties:
        config:
          allOf:
            - $ref: '#/components/schemas/handlers.providerConnectionConfigPayload'
          description: Fulfillment account settings
        created_at:
          description: When the fulfillment account was created
          example: '2026-08-31T10:30:00Z'
          format: date-time
          type: string
        credential_method:
          description: >-
            Authentication method used with the fulfillment vendor: API_KEY or
            OAUTH
          example: OAUTH
          type: string
        credential_owner:
          description: 'Scope that owns the authorization: ORG or PLATFORM'
          example: ORG
          type: string
        environment:
          description: 'Credential environment: TEST or PROD'
          example: TEST
          type: string
        id:
          description: Fulfillment account ID
          example: 550e8400-e29b-41d4-a716-446655440000
          format: uuid
          type: string
        last_validated_at:
          description: When the authorization last validated successfully with the vendor
          example: '2026-08-31T10:30:00Z'
          format: date-time
          type: string
        onboarding_expires_at:
          description: Expiry of onboarding_url (OAUTH creates only).
          example: '2026-09-02T10:30:00Z'
          format: date-time
          type: string
        onboarding_url:
          description: |-
            A freshly minted onboarding session URL (OAUTH creates only); never
            stored, and appears here and on the session endpoint only.
          type: string
        provider:
          description: Fulfillment vendor for this account
          example: TREMENDOUS
          type: string
        provider_account_id:
          description: The vendor's identifier for this fulfillment account, once known
          type: string
        status:
          description: >-
            Fulfillment account status: ACTIVE, DISABLED, PENDING_ONBOARDING,
            PENDING_REVIEW, or REJECTED
          example: ACTIVE
          type: string
        status_reason:
          description: |-
            Machine-readable reason for REJECTED, or a DISABLED connection that
            needs reconnection (reauth_required)
          example: reauth_required
          type: string
        updated_at:
          description: When the fulfillment account was last modified
          example: '2026-08-31T10:30:00Z'
          format: date-time
          type: string
        webhook_registered:
          description: >-
            Whether the account webhook is registered with the fulfillment
            vendor
          example: true
          type: boolean
      type: object
    handlers.ErrorDetails:
      description: >-
        Optional structured details about the error. Always a JSON object: a
        `fields` array for validation errors, or flat
        field/reason/expected/received properties for other input errors.
      properties:
        expected:
          description: Expected value or format (non-validation input errors)
          example: uuid
          type: string
        field:
          description: Field name that caused the error (non-validation input errors)
          example: asset_id
          type: string
        fields:
          description: >-
            Fields lists each offending input field on validation_error
            responses.
          items:
            $ref: '#/components/schemas/handlers.ErrorFieldDetail'
          type: array
        reason:
          description: Machine-readable reason code (non-validation input errors)
          example: invalid
          type: string
        received:
          description: Value that was received (non-validation input errors)
          example: not-a-uuid
          type: string
      type: object
    handlers.providerConnectionConfigPayload:
      properties:
        awaiting_funds_window_hours:
          description: |-
            How long a fulfillment may wait in AWAITING_FUNDS after the provider
            reports an empty balance before failing terminally (default 24)
          example: 24
          type: integer
      type: object
    handlers.ErrorFieldDetail:
      description: >-
        A single field-level error: which input field failed, why, and (where
        known) the expected and received values.
      properties:
        expected:
          description: >-
            Expected value or format. Usually a string; for "one of" constraints
            it

            is an array of the allowed values.
        field:
          description: Field name that caused the error
          example: amount
          type: string
        message:
          description: Human-readable explanation (validation errors only)
          example: This field is required
          type: string
        reason:
          description: Machine-readable reason code
          example: required
          type: string
        received:
          description: Value that was received
          example: '-10.00'
          type: string
      type: object
  securitySchemes:
    ApiKeyAuth:
      description: API key passed in the X-API-Key header.
      in: header
      name: X-API-Key
      type: apiKey
    BearerAuth:
      description: Bearer token passed in the Authorization header (e.g. "Bearer sk_...").
      in: header
      name: Authorization
      type: apiKey

````