Benji Pays Autoprocessing API

openapi: 3.2.0
info:
  title: Benji Pays Merchant Autoprocessing API
  description: 'The Benji Pays Merchant API is a JSON over HTTPS API. All endpoints live under `/v2`. Errors follow RFC 7807 and are served as `application/problem+json`. This overview describes the cross-cutting behavior shared by every merchant endpoint. Endpoint-specific schemas live with each operation. ## Authentication


    Merchant endpoints authenticate with an organization-scoped `x-api-key` header issued from the merchant app:


    ```

    x-api-key:

    ```


    The key is scoped to one organization and inherits the permissions of the login that created it. Failures return `401 Unauthorized` (missing/expired/invalid credentials) or `403 Forbidden` (insufficient mapping permission or organization lifecycle restrictions). ## Request and Correlation IDs


    Two header pairs help with tracing:


    | Header | Direction | Purpose |

    | --- | --- | --- |

    | `X-Request-ID` | request (optional) / response (always) | Unique identifier for one request. Generated as a UUID v4 when the client omits it. |

    | `X-Correlation-ID` | request (optional) / response (always) | Identifier that flows across service boundaries for distributed tracing. Generated as a UUID v4 when omitted. |


    Both IDs are echoed on success and included as `requestId` / `correlationId` extensions on `application/problem+json` error responses. These headers are auto-injected on every operation in this spec — do not redeclare them per route. ## Idempotency


    POST, PATCH, and PUT endpoints accept an `Idempotency-Key` header to make retries safe. - Format: 1–255 characters, alphanumeric only (`[a-zA-Z0-9]+`). - Scope: keys are scoped per actor (no cross-tenant collisions). - Cache: the first response for a given key is cached for 24 hours. - Replay: a duplicate request with the same key and the same body returns the cached response with `X-Idempotency-Replayed: true` only after credentials were resolved by the global authenticate middleware (API key or Auth0 JWT signature check) before the idempotency cache lookup. - Conflict: same key with a different body returns `409 Conflict`. - In-flight: a second request with the same key while the first is still being processed returns `429 Too Many Requests` with `Retry-After` and problem `type` `https://api.benjipays.com/problems/idempotency-processing` (distinct from rate-limit `…/rate-limit-exceeded`). `Idempotency-Key` is auto-injected on every POST/PATCH/PUT operation in this spec — do not redeclare it per route. Routes that intentionally opt out set `x-bp-skip-idempotency: true`. The middleware fails open: if the cache layer is unavailable the request proceeds without idempotency protection. Most write routes treat the header as optional. Routes that require it set `x-bp-require-idempotency: true` and return `400 Bad Request` when it is missing — currently `POST /v2/transactions`, `POST /v2/transactions/prepayments`, and `POST /v2/transactions/{transactionId}/retry-accounting`. Those routes are also the exception to the fail-open rule above: when the cache layer is unavailable they return `503 Service Unavailable` with `Retry-After` and problem `type` `https://api.benjipays.com/problems/idempotency-unavailable`, and the request is not processed. Retry with the same key. The two charge routes (`POST /v2/transactions` and `POST /v2/transactions/prepayments`) also save the key on the charge. Recover a charge with `GET /v2/transactions?idempotencyKey={key}` (empty `data` when the key was never used). After the 24-hour replay window, the same key creates a new charge. ## Pagination


    List endpoints use offset-based pagination with two query parameters:


    | Parameter | Type | Default | Bounds |

    | --- | --- | --- | --- |

    | `limit` | integer | `20` | `1`–`1000` |

    | `offset` | integer | `0` | `≥ 0` |


    Some endpoints use different bounds (for example usage/billing and autoprocessing forecast). Check the per-operation schema.'
  version: 2.0.0
  contact:
    name: Benji Pays API Support
    email: benji@benjipays.com
servers:
- url: https://api.benjipays.com
  description: Development server
security:
- ApiKeyAuth: []
tags:
- name: Autoprocessing
  description: Auto-processing forecast for authenticated organizations
paths:
  /v2/autoprocessing-forecast:
    get:
      summary: List the auto-processing forecast for an Organization
      description: 'Returns a paginated auto-processing forecast: for each open invoice, whether it will be auto-charged on the supplied run date and the reasons behind that decision. Matches the merchant-app batch forecast report. Requires a connected accounting system.'
      tags:
      - Autoprocessing
      security:
      - ApiKeyAuth: []
      parameters:
      - $ref: '#/components/parameters/RequestIdHeader'
      - $ref: '#/components/parameters/CorrelationIdHeader'
      - in: query
        name: startDate
        schema:
          type: string
          pattern: ^\d{4}-\d{2}-\d{2}$
          description: Run/report date the forecast is evaluated against (YYYY-MM-DD, interpreted as UTC).
        required: true
        description: Run/report date the forecast is evaluated against (YYYY-MM-DD, interpreted as UTC).
      - in: query
        name: invoiceId
        schema:
          description: When provided, forecast only this single accounting-system invoice ID. Pagination parameters are ignored.
          type: string
          minLength: 1
          maxLength: 200
          example: '1042'
        description: When provided, forecast only this single accounting-system invoice ID. Pagination parameters are ignored.
      - in: query
        name: limit
        schema:
          default: 20
          type: integer
          minimum: 1
          maximum: 100
      - in: query
        name: offset
        schema:
          default: 0
          type: integer
          minimum: 0
          maximum: 9007199254740991
      responses:
        '200':
          description: Paginated forecast
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ListAutoprocessingForecastResponse'
        '400':
          description: Bad request — request validation failed (invalid query parameters, e.g. date; `type` `…/validation-error` with optional `errors[]`), and/or organization has no accounting integration configured.
          content:
            application/problem+json:
              schema:
                type: object
                properties:
                  type:
                    type: string
                  title:
                    type: string
                  status:
                    type: number
                  detail:
                    type: string
                  instance:
                    type: string
                required:
                - type
                - title
                - status
                - detail
                additionalProperties: false
                description: RFC 7807 Problem Details error response
        '401':
          description: Unauthorized
          content:
            application/problem+json:
              schema:
                type: object
                properties:
                  type:
                    type: string
                  title:
                    type: string
                  status:
                    type: number
                  detail:
                    type: string
                  instance:
                    type: string
                required:
                - type
                - title
                - status
                - detail
                additionalProperties: false
                description: RFC 7807 Problem Details error response
        '403':
          description: Forbidden — missing required OAuth scope (`organizations:autoprocessing:read`), insufficient live mapping permission on the API key owner (e.g. `companyAdmin`), and/or free trial ended without billing enabled. Scope, mapping, and billing state are independent gates; see response `detail`.
          content:
            application/problem+json:
              schema:
                type: object
                properties:
                  type:
                    type: string
                  title:
                    type: string
                  status:
                    type: number
                  detail:
                    type: string
                  instance:
                    type: string
                required:
                - type
                - title
                - status
                - detail
                additionalProperties: false
                description: RFC 7807 Problem Details error response
        '404':
          description: Organization not found
          content:
            application/problem+json:
              schema:
                type: object
                properties:
                  type:
                    type: string
                  title:
                    type: string
                  status:
                    type: number
                  detail:
                    type: string
                  instance:
                    type: string
                required:
                - type
                - title
                - status
                - detail
                additionalProperties: false
                description: RFC 7807 Problem Details error response
        '429':
          description: Too Many Requests
          content:
            application/problem+json:
              schema:
                type: object
                properties:
                  type:
                    type: string
                  title:
                    type: string
                  status:
                    type: number
                  detail:
                    type: string
                  instance:
                    type: string
                required:
                - type
                - title
                - status
                - detail
                additionalProperties: false
                description: RFC 7807 Problem Details error response
      operationId: getV2AutoprocessingForecast
      x-operation-id-source: derived
components:
  schemas:
    ListAutoprocessingForecastResponse:
      type: object
      properties:
        data:
          type: array
          items:
            $ref: '#/components/schemas/AutoprocessingForecastItem'
        pagination:
          type: object
          properties:
            total:
              type: number
              description: Total open invoices across all pages
            limit:
              type: number
            offset:
              type: number
            hasMore:
              type: boolean
            nextOffset:
              anyOf:
              - type: number
              - type: 'null'
            prevOffset:
              anyOf:
              - type: number
              - type: 'null'
          required:
          - total
          - limit
          - offset
          - hasMore
          - nextOffset
          - prevOffset
          additionalProperties: false
      required:
      - data
      - pagination
      additionalProperties: false
      description: Paginated auto-processing forecast response
    AutoprocessingForecastItem:
      type: object
      properties:
        id:
          anyOf:
          - type: string
          - type: 'null'
          description: Accounting system invoice ID
        invoiceNumber:
          anyOf:
          - type: string
          - type: 'null'
          description: Invoice document number
        customerId:
          anyOf:
          - type: string
          - type: 'null'
          description: Accounting customer ID
        customerName:
          anyOf:
          - type: string
          - type: 'null'
        currency:
          anyOf:
          - type: string
          - type: 'null'
        dueDate:
          anyOf:
          - type: string
          - type: 'null'
          description: Invoice due date (YYYY-MM-DD)
        amountToCharge:
          anyOf:
          - type: number
          - type: 'null'
          description: Amount that would be charged
        willBeCharged:
          type: boolean
          description: Whether the invoice will be auto-charged on the run date
        dueDateMet:
          type: boolean
        autoProcessingEnabled:
          type: boolean
          description: Whether auto-processing is enabled for the customer
        hasEnabledProfile:
          type: boolean
          description: Whether an enabled payment profile exists
        hasInstallments:
          type: boolean
        installmentDateMet:
          anyOf:
          - type: boolean
          - type: 'null'
          description: Whether an installment date is met; null when no installments
        startDateMet:
          type: boolean
        memoSkip:
          type: boolean
          description: Whether the invoice is skipped by the memo rule
        amountSkip:
          type: boolean
          description: Whether the invoice is skipped by the amount rule
        reasons:
          type: array
          items:
            type: string
          description: Human-readable reasons explaining the forecast outcome
      required:
      - id
      - invoiceNumber
      - customerId
      - customerName
      - currency
      - dueDate
      - amountToCharge
      - willBeCharged
      - dueDateMet
      - autoProcessingEnabled
      - hasEnabledProfile
      - hasInstallments
      - installmentDateMet
      - startDateMet
      - memoSkip
      - amountSkip
      - reasons
      additionalProperties: false
      description: Auto-processing forecast for a single invoice
  parameters:
    CorrelationIdHeader:
      name: X-Correlation-ID
      in: header
      required: false
      description: Optional ID that flows across service boundaries for distributed tracing. The server generates a UUID v4 if omitted and always echoes the value in the response.
      schema:
        type: string
        format: uuid
    RequestIdHeader:
      name: X-Request-ID
      in: header
      required: false
      description: Optional client-supplied unique ID for one request. The server generates a UUID v4 if omitted and always echoes the value in the response.
      schema:
        type: string
        format: uuid
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key
      description: Organization-scoped API key. Send it in the x-api-key header. Available on organization endpoints only.
x-speakeasy-retries:
  strategy: backoff
  backoff:
    initialInterval: 500
    maxInterval: 60000
    maxElapsedTime: 3600000
    exponent: 1.5
  statusCodes:
  - 5XX
  retryConnectionErrors: true
x-provenance:
  method: searched
  source: https://developer.benjipays.com/reference
  harvested: '2026-11-02'
  tool: harvest-readme-openapi.py
  note: Assembled verbatim from the OpenAPI definition ReadMe embeds in each operation page of the provider's developer portal; paths and components merged by API title, nothing authored.
  assembled_from:
  - https://developer.benjipays.com/reference/delete_v2-customers-customerid-alert.md
  - https://developer.benjipays.com/reference/delete_v2-customers-customerid-notes-noteid.md
  - https://developer.benjipays.com/reference/get_v2-accounting-accounts.md
  - https://developer.benjipays.com/reference/get_v2-autoprocessing-forecast.md
  - https://developer.benjipays.com/reference/get_v2-customers-customerid-notes-noteid.md
  - https://developer.benjipays.com/reference/get_v2-customers-customerid-notes.md
  - https://developer.benjipays.com/reference/get_v2-customers-customerid.md
  - https://developer.benjipays.com/reference/get_v2-customers.md
  - https://developer.benjipays.com/reference/get_v2-emails-emailid.md
  - https://developer.benjipays.com/reference/get_v2-emails.md
  - https://developer.benjipays.com/reference/get_v2-gateways-capabilities.md
  - https://developer.benjipays.com/reference/get_v2-gateways.md
  - https://developer.benjipays.com/reference/get_v2-invoices-invoiceid-pdf.md
  - https://developer.benjipays.com/reference/get_v2-invoices-invoiceid.md
  - https://developer.benjipays.com/reference/get_v2-invoices.md
  - https://developer.benjipays.com/reference/get_v2-notes-categories.md
  - https://developer.benjipays.com/reference/get_v2-notes-statuses.md
  - https://developer.benjipays.com/reference/get_v2-organization.md
  - https://developer.benjipays.com/reference/get_v2-payment-method-requests-paymentmethodrequestid.md
  - https://developer.benjipays.com/reference/get_v2-payment-method-requests.md
  - https://developer.benjipays.com/reference/get_v2-payment-methods-id.md
  - https://developer.benjipays.com/reference/get_v2-payment-methods.md
  - https://developer.benjipays.com/reference/get_v2-settings.md
  - https://developer.benjipays.com/reference/get_v2-transactions-transactionid-receipt.md
  - https://developer.benjipays.com/reference/get_v2-transactions.md
  - https://developer.benjipays.com/reference/get_v2-users.md
  - https://developer.benjipays.com/reference/get_v2-whoami-1.md
  - https://developer.benjipays.com/reference/patch_v2-customers-customerid-notes-noteid.md
  - https://developer.benjipays.com/reference/patch_v2-customers-customerid.md
  - https://developer.benjipays.com/reference/post_v2-customers-customerid-alert.md
  - https://developer.benjipays.com/reference/post_v2-customers-customerid-notes-noteid-replies.md
  - https://developer.benjipays.com/reference/post_v2-customers-customerid-notes-noteid-status.md
  - https://developer.benjipays.com/reference/post_v2-customers-customerid-notes.md
  - https://developer.benjipays.com/reference/post_v2-payment-links-applied-invoiceid.md
  - https://developer.benjipays.com/reference/post_v2-payment-links-unapplied.md
  - https://developer.benjipays.com/reference/post_v2-payment-method-requests.md
  - https://developer.benjipays.com/reference/post_v2-transactions-prepayments.md
  - https://developer.benjipays.com/reference/post_v2-transactions-transactionid-resend-receipt.md
  - https://developer.benjipays.com/reference/post_v2-transactions-transactionid-retry-accounting.md
  - https://developer.benjipays.com/reference/post_v2-transactions.md
  merge:
    pages: 40
    deduped: 167
    conflicts_kept_first: 0