> ## Documentation Index
> Fetch the complete documentation index at: https://79cdaa32-9b19-4e9d-ab9d-a89800ef0f46.valox.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Retrieve Signature Data for Account Setup

> Returns the domain, types, and message objects needed for EIP-712 typed data signing.
This is typically used to prepare the data that needs to be signed by the user's wallet
to set up account allowances and delays.

The response contains structured data compatible with the EIP-712 signature standard.
After obtaining this data and signing it with the user's wallet, the signature can be
sent to the `/api/v1/account/deploy-safe-modules` endpoint to complete the setup process.

Prerequisites:
- User must have a deployed Safe account
- The Safe account must have a currency set (via `/api/v1/safe/set-currency`)




## OpenAPI

````yaml specs/api/spec.json get /api/v1/account/signature-payload
openapi: 3.0.0
info:
  title: ValoX API
  version: 1.0.0
  description: OpenAPI documentation for ValoX
servers:
  - url: https://api.valox.co
security: []
tags:
  - name: Account Management
    description: Information about your Account
  - name: Authentication
    description: Authenticate to our API using SIWE
  - name: Card Management
    description: Manage all your Cards
  - name: IBAN
    description: Integrate with Monerium to issue IBANs
  - name: KYC
    description: KYC using Sumsub SDK
  - name: Physical Card Order
    description: Order a Physical Card and manage the process
  - name: Rewards
    description: Cashback Rewards
  - name: Safe Management
    description: Manage your Safe
  - name: Transactions
    description: Manage Card Transactions
  - name: User
    description: Manage User Information
  - name: Webhooks
    description: Manage Webhooks
paths:
  /api/v1/account/signature-payload:
    get:
      tags:
        - Safe Management
      summary: Retrieve Signature Data for Account Setup
      description: >
        Returns the domain, types, and message objects needed for EIP-712 typed
        data signing.

        This is typically used to prepare the data that needs to be signed by
        the user's wallet

        to set up account allowances and delays.


        The response contains structured data compatible with the EIP-712
        signature standard.

        After obtaining this data and signing it with the user's wallet, the
        signature can be

        sent to the `/api/v1/account/deploy-safe-modules` endpoint to complete
        the setup process.


        Prerequisites:

        - User must have a deployed Safe account

        - The Safe account must have a currency set (via
        `/api/v1/safe/set-currency`)
      responses:
        '200':
          description: Signature data for EIP-712 typed data signing
          content:
            application/json:
              schema:
                type: object
                properties:
                  domain:
                    type: object
                    description: Domain data for EIP-712 signature
                  primaryType:
                    type: string
                    description: Primary type for EIP-712 signature
                  types:
                    type: object
                    description: Type definitions for EIP-712 signature
                  message:
                    type: object
                    description: Message data for EIP-712 signature
        '400':
          description: Bad request (missing account, token, or signer)
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
                    description: Error message explaining why the request failed
              examples:
                accountNotFound:
                  value:
                    error: Account not found
                currencyNotSet:
                  value:
                    error: Safe currency not set
                missingSigner:
                  value:
                    error: Missing signer address
        '401':
          $ref: '#/components/responses/UnauthorizedError'
        '500':
          $ref: '#/components/responses/InternalServerError'
      deprecated: true
      security:
        - bearerAuth: []
components:
  responses:
    UnauthorizedError:
      description: Unauthorized Error
      content:
        application/json:
          schema:
            type: object
            properties:
              message:
                type: string
    InternalServerError:
      description: Internal Server Error
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  schemas:
    Error:
      type: object
      properties:
        error:
          type: string
          description: Error message
          example: Internal server error
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT

````