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

# Submit a recurring payment signature

> Submit a signature for a recurring payment permit to activate the recurring payment schedule. This endpoint is called after creating a recurring payment and obtaining the permit data. The signature authorizes the recurring payment contract to execute payments on behalf of the payer according to the schedule. Once activated, payments will be executed automatically at the specified intervals.



## OpenAPI

````yaml /api-reference/openapi.v2.json post /v2/payouts/recurring/{id}
openapi: 3.0.0
info:
  title: Request Network API
  description: API for easily creating and paying Requests with Request Network.
  version: 0.13.0
  contact: {}
servers:
  - url: https://api.request.network
    description: Production server
  - url: https://api.stage.request.network
    description: Staging server
  - url: http://127.0.0.1:8080
    description: Local development server
security: []
tags:
  - name: V2/Request
    description: Core payment request operations (V2)
  - name: V2/Payments
    description: Payment search and management operations (V2)
  - name: V2/Payouts
    description: Pay a request without creating one first (V2)
  - name: V2/Payer
    description: Crypto-to-fiat payer management operations (V2)
  - name: V2/Currencies
    description: Currency operations (V2)
  - name: V2/Client IDs
    description: Client ID management (V2)
  - name: V2/Payee Destination
    description: Payee destination management (V2)
externalDocs:
  description: Request Network Docs
  url: https://docs.request.network/request-network-api
paths:
  /v2/payouts/recurring/{id}:
    post:
      tags:
        - Pay
        - V2/Payouts
      summary: Submit a recurring payment signature
      description: >-
        Submit a signature for a recurring payment permit to activate the
        recurring payment schedule. This endpoint is called after creating a
        recurring payment and obtaining the permit data. The signature
        authorizes the recurring payment contract to execute payments on behalf
        of the payer according to the schedule. Once activated, payments will be
        executed automatically at the specified intervals.
      operationId: PayoutV2Controller_submitRecurringPaymentSignature_v2
      parameters:
        - name: id
          required: true
          in: path
          description: The ID of the recurring payment
          schema:
            example: 01JXYJKCAHGFTDR15F2D072ESG
            type: string
        - name: x-api-key
          in: header
          description: API key for authentication (optional if using Client ID)
          required: false
          schema:
            type: string
        - name: x-client-id
          in: header
          description: Client ID for frontend authentication (optional if using API key)
          required: false
          schema:
            type: string
        - name: Origin
          in: header
          description: >-
            Origin header (required for Client ID auth, automatically set by
            browser)
          required: false
          schema:
            type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                permitSignature:
                  type: string
                  description: The signature of the recurring payment permit.
              required:
                - permitSignature
              example:
                permitSignature: >-
                  0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1b
      responses:
        '201':
          description: Recurring payment signature submitted successfully
          content:
            application/json:
              examples:
                success:
                  summary: Signature submitted successfully
                  value:
                    message: Recurring payment activated successfully
                    id: 01JXYJKCAHGFTDR15F2D072ESG
                    status: active
        '400':
          description: Bad request
          content:
            application/json:
              examples:
                invalidSignature:
                  summary: Invalid signature provided
                  value:
                    message: Invalid signature provided
                    error: Bad Request
                    statusCode: 400
                alreadyActive:
                  summary: Recurring payment is already active
                  value:
                    message: Recurring payment is already active
                    error: Bad Request
                    statusCode: 400
        '404':
          description: Recurring payment not found
        '429':
          description: Too Many Requests

````