> ## 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.

# Get permit messages

> Fetch the EIP-712 typed-data messages to sign for gasless token approvals.

Returns the EIP-2612 permit messages for a **self-custody** account wallet — one per supported asset, each with a `supportedAssetId` and the `typedData` to sign. Sign `typedData` with the wallet **owner's** key, then [submit the signature](/api-reference/Finance-API/permits/submit-signed-permit) to grant a gasless allowance. Full flow: [Approving transfers without gas](/guides/finance/permits-and-allowances).

<Note>Self-custody account wallets only — Venly-managed and escrow wallets are permitted automatically. Calling this on a Venly-managed company returns `400 invalid-request` ("Permits are only applicable for SELF\_CUSTODY companies"). See [Approving transfers without gas](/guides/finance/permits-and-allowances).</Note>


## OpenAPI

````yaml api-reference/Finance-API-Specs.yaml GET /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:
    get:
      tags:
        - Permits
      summary: Get permit messages for wallet
      description: >
        Retrieves the EIP-712 permit messages a self-custody wallet must sign to
        grant the orchestration wallet an allowance. Returns one entry per
        supported asset, each with a `supportedAssetId` and the `typedData` to
        sign.


        Sign `typedData` with the wallet **owner's** key (the signature must
        recover to `owner`), then submit it via POST.


        **Note:** Applies to SELF_CUSTODY companies only — VENLY_MANAGED wallets
        (and all escrow wallets) are permitted automatically by Venly.
      operationId: getPermitMessages
      parameters:
        - $ref: '#/components/parameters/AccountId'
        - $ref: '#/components/parameters/WalletId'
      responses:
        '200':
          description: List of permit messages
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PermitMessageListResponse'
              example:
                success: true
                result:
                  - supportedAssetId: aabbccdd-1122-4334-9556-7788990011ab
                    asset: USDC
                    contractAddress: '0x036CbD53842c5426634e7929541eC2318f3dCF7e'
                    status: CONFIRMED
                    typedData:
                      types:
                        EIP712Domain:
                          - name: name
                            type: string
                          - name: version
                            type: string
                          - name: chainId
                            type: uint256
                          - name: verifyingContract
                            type: address
                        Permit:
                          - name: owner
                            type: address
                          - name: spender
                            type: address
                          - name: value
                            type: uint256
                          - name: nonce
                            type: uint256
                          - name: deadline
                            type: uint256
                      primaryType: Permit
                      domain:
                        name: USDC
                        version: '2'
                        chainId: 84532
                        verifyingContract: '0x036CbD53842c5426634e7929541eC2318f3dCF7e'
                      message:
                        owner: '0x71C7656EC7ab88b098defB751B7401B5f6d8976F'
                        spender: '0x5B38Da6a701c568545dCfcB03FcB875f56beddC4'
                        value: >-
                          115792089237316195423570985008687907853269984665640564039457584007913129639935
                        nonce: 0
                        deadline: '4102444800'
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '404':
          $ref: '#/components/responses/NotFound'
        '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:
    PermitMessageListResponse:
      allOf:
        - $ref: '#/components/schemas/BaseResponse'
        - type: object
          properties:
            result:
              type: array
              items:
                $ref: '#/components/schemas/PermitMessage'
    BaseResponse:
      type: object
      properties:
        success:
          type: boolean
          description: Indicates whether the request was successful
    PermitMessage:
      type: object
      properties:
        supportedAssetId:
          type: string
          format: uuid
        asset:
          type: string
        contractAddress:
          type: string
        status:
          $ref: '#/components/schemas/PermitStatus'
        typedData:
          $ref: '#/components/schemas/Eip712PermitMessage'
    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
    Eip712PermitMessage:
      type: object
      description: EIP-712 typed-data structure to sign
      properties:
        types:
          type: object
          additionalProperties:
            type: array
            items:
              $ref: '#/components/schemas/Eip712TypeEntry'
        primaryType:
          type: string
        domain:
          $ref: '#/components/schemas/Eip712Domain'
        message:
          $ref: '#/components/schemas/PermitData'
    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.
    Eip712TypeEntry:
      type: object
      properties:
        name:
          type: string
        type:
          type: string
    Eip712Domain:
      type: object
      properties:
        name:
          type: string
        version:
          type: string
        chainId:
          type: integer
          format: int32
        verifyingContract:
          type: string
    PermitData:
      type: object
      description: EIP-2612 permit message payload
      properties:
        owner:
          type: string
        spender:
          type: string
        value:
          type: string
        nonce:
          type: integer
          format: int64
        deadline:
          type: string
  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.
    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: {}

````