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

# Approve or reject approvals (your own key)

> Approves (`approved: true`) or rejects (`false`) up to 100 approvals at once, as the app's Approvals page does for one or many, as the key's person. Only a person decides an approval, with their own key: any other key is refused (403). Approving resumes each run on its own shortly after, and a run can send email to your customers; rejecting ends it and nothing it was waiting to send goes out. Each approval must be assigned to the person, unless they build in Agent Studio. Each item answers on its own, in request order: `approved` or `rejected`, or `failed` with the error a single decision would have had (`not_found` for one the key can't see, as GET answers, `conflict` when already decided, `upstream_failed` when the run couldn't be queued to resume: retry it when it is pending again; its message says when it is stuck approved instead, for someone to put right). Each item carries the approval's `app_url`: end the answer with the links. Over MCP: first show the person what will be sent (GET the approval: recipients, subject, the email as text) with its `app_url`, where the email shows rendered, and act only on their explicit go-ahead for these approvals.



## OpenAPI

````yaml /api/statisfy-api.openapi.json post /v1/approvals/decisions
openapi: 3.1.0
info:
  description: >-
    The agent-first Statisfy API. Authenticate with an API key (`Authorization:
    Bearer stfy_live_…`), then call `GET /v1/meta/capabilities` to discover
    every operation and its schemas.
  title: Statisfy API
  version: 1.0.0
servers:
  - url: https://api.statisfy.com
    description: Production
security: []
paths:
  /v1/approvals/decisions:
    post:
      tags:
        - approvals
      summary: Approve or reject approvals (your own key)
      description: >-
        Approves (`approved: true`) or rejects (`false`) up to 100 approvals at
        once, as the app's Approvals page does for one or many, as the key's
        person. Only a person decides an approval, with their own key: any other
        key is refused (403). Approving resumes each run on its own shortly
        after, and a run can send email to your customers; rejecting ends it and
        nothing it was waiting to send goes out. Each approval must be assigned
        to the person, unless they build in Agent Studio. Each item answers on
        its own, in request order: `approved` or `rejected`, or `failed` with
        the error a single decision would have had (`not_found` for one the key
        can't see, as GET answers, `conflict` when already decided,
        `upstream_failed` when the run couldn't be queued to resume: retry it
        when it is pending again; its message says when it is stuck approved
        instead, for someone to put right). Each item carries the approval's
        `app_url`: end the answer with the links. Over MCP: first show the
        person what will be sent (GET the approval: recipients, subject, the
        email as text) with its `app_url`, where the email shows rendered, and
        act only on their explicit go-ahead for these approvals.
      operationId: approvals_decide
      requestBody:
        content:
          application/json:
            schema:
              additionalProperties: false
              properties:
                approval_ids:
                  description: >-
                    The approvals to decide, ids from GET /v1/approvals (1 to
                    100, each once)
                  items:
                    maxLength: 64
                    minLength: 1
                    type: string
                  maxItems: 100
                  minItems: 1
                  title: Approval Ids
                  type: array
                approved:
                  description: '`true` approves them all; `false` rejects them all'
                  title: Approved
                  type: boolean
              required:
                - approval_ids
                - approved
              type: object
        required: true
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DecisionResult'
          description: Successful Response
      security:
        - HTTPBearer: []
components:
  schemas:
    DecisionResult:
      properties:
        items:
          description: One per approval, in request order
          items:
            $ref: '#/components/schemas/DecisionItem'
          title: Items
          type: array
      required:
        - items
      title: DecisionResult
      type: object
    DecisionItem:
      properties:
        app_url:
          anyOf:
            - type: string
            - type: 'null'
          description: >-
            The approval's page in the app, to follow what the run does next
            (unset for one the key can't see)
          title: App Url
        error:
          anyOf:
            - $ref: '#/components/schemas/ItemError'
            - type: 'null'
          description: >-
            Set exactly when `status` is `failed`: `not_found` (no such
            approval, or one the key can't see), `conflict` (already decided;
            `details` names its status), or `upstream_failed` (the run couldn't
            be queued to resume: usually the approval is pending again, so
            retry; rarely it stays approved with no resume coming, and the
            message says so: someone has to put it right, so don't retry)
        id:
          title: Id
          type: string
        status:
          enum:
            - approved
            - rejected
            - failed
          title: Status
          type: string
      required:
        - id
        - status
      title: DecisionItem
      type: object
    ItemError:
      description: The error envelope a single request would have returned.
      properties:
        code:
          title: Code
          type: string
        details:
          items:
            additionalProperties: true
            type: object
          title: Details
          type: array
        message:
          title: Message
          type: string
      required:
        - code
        - message
      title: ItemError
      type: object
  securitySchemes:
    HTTPBearer:
      scheme: bearer
      type: http
      description: >-
        An API key, sent as `Authorization: Bearer stfy_live_…`. See
        [Authentication](/rest-api/authentication) for how to get one and which
        scopes it needs.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.