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

# List signature requests

> Returns all signature requests for the authenticated client's organization, newest first. Optionally pass updatedSince to return only requests updated strictly after that instant (ISO-8601).



## OpenAPI

````yaml GET /v0/signature-requests
openapi: 3.0.0
info:
  title: Formable API
  version: 1.0.0
  description: >-
    The Formable API lets you embed e-signature and document redlining workflows
    directly into your product. Create templates, send documents for signature,
    run collaborative redline negotiations, and retrieve completed documents.
servers:
  - url: https://formable-production.up.railway.app/api
    description: Production
  - url: http://localhost:4000/api
    description: Local
security:
  - bearerAuth: []
tags:
  - name: Templates
    description: Upload documents and generate editor URLs.
  - name: Signature Requests
    description: Send documents for e-signature and retrieve signed results.
  - name: Redlining
    description: Create and manage collaborative redline negotiations.
  - name: Billing
    description: Retrieve usage information.
  - name: Health
    description: Service health checks.
paths:
  /v0/signature-requests:
    get:
      tags:
        - Signature Requests
      summary: List signature requests
      description: >-
        Returns all signature requests for the authenticated client's
        organization, newest first. Optionally pass updatedSince to return only
        requests updated strictly after that instant (ISO-8601).
      operationId: listSignatureRequests
      parameters:
        - in: query
          name: updatedSince
          required: false
          schema:
            type: string
            format: date-time
          description: >-
            ISO-8601 timestamp; only signature requests updated strictly after
            this time are returned.
          example: '2024-01-15T10:30:00.000Z'
      responses:
        '200':
          description: >-
            Signature requests retrieved successfully (empty array if none
            match).
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/SignatureRequest'
        '400':
          $ref: '#/components/responses/BadRequestError'
        '401':
          $ref: '#/components/responses/UnauthorizedError'
        '403':
          $ref: '#/components/responses/ForbiddenError'
        '500':
          $ref: '#/components/responses/InternalServerError'
      security:
        - bearerAuth: []
components:
  schemas:
    SignatureRequest:
      type: object
      required:
        - templateId
        - signer
        - sender
        - status
        - testMode
      properties:
        templateId:
          type: string
          description: The template ID associated with the signature request.
          example: tmpl_abc123
        signer:
          $ref: '#/components/schemas/Party'
        sender:
          $ref: '#/components/schemas/Party'
        status:
          type: string
          enum:
            - Created
            - Completed
          description: Current status of the signature request.
          example: Created
        testMode:
          type: boolean
          description: Whether the signature request is in test mode.
          example: false
    Party:
      type: object
      required:
        - email
        - name
      properties:
        email:
          type: string
          format: email
          description: Email address.
        name:
          type: string
          description: Full name.
    Error:
      type: object
      properties:
        error:
          type: string
          description: A human-readable error message.
  responses:
    BadRequestError:
      description: Bad request - missing or invalid parameters.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error: templateId is required
    UnauthorizedError:
      description: Unauthorized - missing or invalid bearer token.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error: Auth token not valid
    ForbiddenError:
      description: Forbidden - the client is not authorized to perform this action.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error: Client not authorized to perform this action
    InternalServerError:
      description: Internal server error.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error: Internal server error
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >-
        OAuth 2.0 client credentials access token, passed as a Bearer token in
        the Authorization header.

````