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

# Submit a signed permit

> Submit an EIP-712 signature to grant a gasless token allowance.

Submits the `v`/`r`/`s` signature for a [permit message](/api-reference/Finance-API/permits/get-permit-messages). It moves `PENDING → SUBMITTED → CONFIRMED` (poll `GET .../permits`); once all of a wallet's permits are `CONFIRMED` the wallet becomes `ACTIVE`. Re-submitting an already-confirmed permit returns `409`.

<Note>The signature must recover to the wallet `owner`, or the permit settles as `FAILED`. The call returns HTTP `200` with `result.status` — poll `SUBMITTED → CONFIRMED`. See [Approving transfers without gas](/guides/finance/permits-and-allowances).</Note>


## OpenAPI

````yaml api-reference/Finance-API-Specs.yaml POST /accounts/{accountId}/wallets/{walletId}/permits
openapi: 3.1.0
info:
  title: Venly Finance API
  description: >
    REST API for the Venly Finance platform:

    - Party management (Individuals & Organisations)

    - Account management with party association

    - Wallet balances & token allowances on supported chains (Base, Avalanche)

    - Virtual bank account assignment for global payments (EUR SEPA)

    - Fiat-to-crypto payment sessions (pay-in)

    - Account-to-account fiat & crypto transfers

    - EIP-2612 permits and payment requests


    ## Authentication


    All endpoints use OAuth2 client credentials. Obtain a token first, then
    include it in every request:


    **Step 1 — Get a token:**

    ```bash

    curl -X POST
    https://login.venly.io/auth/realms/VenlyFinance/protocol/openid-connect/token
    \
      -H "Content-Type: application/x-www-form-urlencoded" \
      -d "grant_type=client_credentials&client_id={CLIENT_ID}&client_secret={CLIENT_SECRET}"
    ```


    **Step 2 — Use the token:**

    ```

    Authorization: Bearer {access_token}

    ```


    Tokens expire after **5 minutes**. Implement refresh logic in your client.
  version: 1.1.0
  contact:
    name: Venly Support
    email: support@venly.io
    url: https://docs.venlyfinance.com
  license:
    name: Proprietary
  x-logo:
    url: https://venlyfinance.com/logo.png
  x-security-contact: security@venly.io
servers:
  - url: https://api.venlyfinance.com/v1
    description: Production
  - url: https://api-staging.venlyfinance.com/v1
    description: Staging
security:
  - OAuth2: []
tags:
  - name: Parties
    description: Party management (Individuals & Organisations)
  - name: Accounts
    description: Account management, party-role associations
  - name: Wallets
    description: Blockchain wallet balances
  - name: Virtual Bank Accounts
    description: Virtual bank account payment references for global payments
  - name: Fiat-to-crypto Payment Sessions
    description: Fiat-to-crypto payment session creation
  - name: Payment Requests
    description: Payment request management for card provider integrations
  - name: Transfers
    description: Fiat and crypto transfer operations between accounts
  - name: Permits
    description: EIP-712 permit signature management for token approvals
  - name: Allowances
    description: Token allowance management for wallets
paths:
  /accounts/{accountId}/wallets/{walletId}/permits:
    post:
      tags:
        - Permits
      summary: Submit signed permit
      description: >
        Submits a signed EIP-712 permit for on-chain execution by the
        orchestration wallet (which pays the gas). The signature **must recover
        to the wallet `owner`** — otherwise the permit settles as `FAILED`.


        Returns HTTP 200 with the permit `status`: `SUBMITTED` while it settles
        on-chain, then `CONFIRMED`. Poll `GET .../permits` for the transition.
        When all of a wallet's permits are `CONFIRMED`, the wallet becomes
        `ACTIVE` and can send transfers/payments. Re-submitting an
        already-confirmed permit returns `409`.
      operationId: submitPermit
      parameters:
        - $ref: '#/components/parameters/AccountId'
        - $ref: '#/components/parameters/WalletId'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/SubmitPermitRequest'
            example:
              supportedAssetId: aabbccdd-1122-4334-9556-7788990011ab
              signature:
                v: '28'
                r: >-
                  0x1111111111111111111111111111111111111111111111111111111111111111
                s: >-
                  0x2222222222222222222222222222222222222222222222222222222222222222
      responses:
        '200':
          description: Permit submitted successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SinglePermitResultResponse'
              example:
                success: true
                result:
                  id: 11aa22bb-33cc-4dd4-9ee5-66ff77aa88bb
                  supportedAssetId: aabbccdd-1122-4334-9556-7788990011ab
                  asset: USDC
                  contractAddress: '0x036CbD53842c5426634e7929541eC2318f3dCF7e'
                  status: SUBMITTED
                  permitTxId: 0a9f8e7d-6c5b-4a39-8271-6a5b4c3d2e1f
                  skipped: false
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '404':
          $ref: '#/components/responses/NotFound'
        '409':
          $ref: '#/components/responses/Conflict'
        '500':
          $ref: '#/components/responses/InternalServerError'
components:
  parameters:
    AccountId:
      name: accountId
      in: path
      required: true
      description: Unique account identifier
      schema:
        type: string
        format: uuid
      example: b2a1f0e9-8c7d-4e3a-9f21-0a1b2c3d4e5f
    WalletId:
      name: walletId
      in: path
      required: true
      description: Unique wallet identifier
      schema:
        type: string
        format: uuid
      example: 9f8e7d6c-5b4a-4938-8271-6a5b4c3d2e1f
  schemas:
    SubmitPermitRequest:
      type: object
      required:
        - supportedAssetId
        - signature
      properties:
        supportedAssetId:
          type: string
          format: uuid
          description: ID of the supported asset to grant spending permission for
        signature:
          $ref: '#/components/schemas/PermitSignature'
    SinglePermitResultResponse:
      allOf:
        - $ref: '#/components/schemas/BaseResponse'
        - type: object
          properties:
            result:
              $ref: '#/components/schemas/PermitResult'
    PermitSignature:
      type: object
      required:
        - v
        - r
        - s
      properties:
        v:
          type: string
          description: Recovery byte of the signature
        r:
          type: string
          pattern: ^0x[0-9a-fA-F]{64}$
          description: First 32 bytes of the signature
        s:
          type: string
          pattern: ^0x[0-9a-fA-F]{64}$
          description: Second 32 bytes of the signature
    BaseResponse:
      type: object
      properties:
        success:
          type: boolean
          description: Indicates whether the request was successful
    PermitResult:
      type: object
      properties:
        id:
          type: string
          format: uuid
        supportedAssetId:
          type: string
          format: uuid
        asset:
          type: string
        contractAddress:
          type: string
        status:
          $ref: '#/components/schemas/PermitStatus'
        permitTxId:
          type: string
          description: Internal permit transaction identifier (UUID, not an on-chain hash)
        skipped:
          type: boolean
          description: True if the permit was a no-op (e.g. allowance already granted)
    ErrorResponse:
      type: object
      description: Error response wrapper
      properties:
        success:
          type: boolean
          description: Always false for error responses
          example: false
        errors:
          type: array
          description: List of errors that occurred
          items:
            $ref: '#/components/schemas/ErrorBody'
        result:
          type: object
          nullable: true
          description: Null or omitted when success is false
    PermitStatus:
      type: string
      description: Status of an EIP-712 permit
      enum:
        - PENDING
        - SUBMITTED
        - CONFIRMED
        - FAILED
    ErrorBody:
      type: object
      description: Individual error details
      properties:
        code:
          type: string
          description: Machine-readable error code
          example: invalid-request
        message:
          type: string
          description: Human-readable error message
          example: The request contains invalid parameters.
  responses:
    BadRequest:
      description: Request validation failed (400)
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            success: false
            errors:
              - code: invalid-request
                message: The request contains invalid parameters.
    Unauthorized:
      description: Authentication required or failed (401)
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            success: false
            errors:
              - code: unauthenticated
                message: Please authenticate to perform this action.
    Forbidden:
      description: Caller lacks the required authority/role (403)
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            success: false
            errors:
              - code: forbidden
                message: You do not have permission to access this resource.
    NotFound:
      description: Resource not found (404)
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            success: false
            errors:
              - code: account-not-found
                message: The requested resource was not found.
    Conflict:
      description: Resource conflict / optimistic-lock failure (409)
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            success: false
            errors:
              - code: concurrent-modification
                message: >-
                  This request has been modified by another user. Please refresh
                  and try again.
    InternalServerError:
      description: Unexpected server error (500)
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            success: false
            errors:
              - code: internal-error
                message: An unexpected error occurred. Please try again later.
  securitySchemes:
    OAuth2:
      type: oauth2
      description: >
        OAuth2 client credentials flow. Token endpoints:

        - Staging:
        https://login-staging.venly.io/auth/realms/VenlyFinance/protocol/openid-connect/token

        - Production:
        https://login.venly.io/auth/realms/VenlyFinance/protocol/openid-connect/token
      flows:
        clientCredentials:
          tokenUrl: >-
            https://login-staging.venly.io/auth/realms/VenlyFinance/protocol/openid-connect/token
          scopes: {}

````