---
updatedAt: 2026-09-14T13:59:17.000Z
agentTools:
  projectIndex: https://docs.caliza.com/llms.txt
---

# Issue the attestation for a manual-signing ownership proof

Returns the exact attestation text the wallet holder must sign with the wallet's own key, and the signature scheme to submit it under — for wallets that cannot use the SafeConnect components. The signed result is submitted via the submit ownership proof endpoint.

# OpenAPI definition

```json
{
  "openapi": "3.0.1",
  "info": {
    "title": "Caliza API documentation reference",
    "description": "The Caliza API enables seamless integration of financial services including payments, payouts, currency conversions, and compliance workflows. \n\n## Key Features\n- **Transaction Management**: Create, simulate, and track financial transactions across multiple currencies and payment rails\n- **Beneficiary Management**: Onboard and manage individuals and businesses with built-in KYC/KYB verification\n- **Multi-Currency Support**: Handle USD, BRL, MXN, EUR, and cryptocurrencies (USDT, USDC) with real-time exchange rates\n- **Payment Rails**: Support for ACH, Wire, PIX, SPEI, SWIFT, and blockchain networks (Ethereum, Polygon, Tron, Stellar, Base, Solana)\n- **Compliance**: Automated KYX workflows, document verification, and regulatory compliance features\n- **Webhooks**: Real-time event notifications for transaction status updates and system events\n\n## Getting Started\n1. Obtain your API credentials from the Caliza dashboard\n2. Authenticate using Bearer token (JWT)\n3. Create a simulation to preview transaction costs\n4. Execute transactions using the simulation ID\n5. Track status via webhooks or polling\n\n## Base URLs\n- **Sandbox**: `https://api.sandbox.caliza.com` - For testing and integration development\n- **Production**: `https://api.caliza.com` - For live transactions\n\n## Rate Limits\nAPI requests are rate-limited to ensure system stability. Contact support for rate limit increases.\n\n## Support\nFor technical support, integration questions, or API issues, contact our developer support team.\n",
    "version": "v1",
    "contact": {
      "name": "Caliza API Support",
      "email": "api-support@caliza.com",
      "url": "https://docs.caliza.com"
    },
    "termsOfService": "https://caliza.com/terms"
  },
  "security": [
    {
      "bearerAuth": []
    }
  ],
  "servers": [
    {
      "url": "https://api.sandbox.com",
      "description": "Sandbox Environment"
    },
    {
      "url": "https://api.caliza.com",
      "description": "Production Environment"
    },
    {
      "url": "https://api.sandbox.caliza.com",
      "description": "Sandbox Environment (backoffice)"
    }
  ],
  "tags": [
    {
      "name": "Travel Rule V1",
      "description": "Crypto Travel Rule compliance endpoints. Collect wallet ownership proofs for self-hosted (non-custodial) wallet recipients — via wallet signature or microtransfer (Satoshi test) — and retrieve the Travel Rule information a depositor's VASP needs to originate the Travel Rule message for an inbound crypto deposit."
    }
  ],
  "paths": {
    "/v1/travel-rule/proofs/manual-attestation": {
      "post": {
        "tags": [
          "Travel Rule V1"
        ],
        "summary": "Issue the attestation for a manual-signing ownership proof",
        "description": "Returns the exact attestation text the wallet holder must sign with the wallet's own key, and the signature scheme to submit it under — for wallets that cannot use the SafeConnect components (keystore or seed-phrase holders, MPC/custody consoles, TRON wallets). The wallet holder signs the text in their own tooling (`personal_sign` / \"Sign message\"); the resulting signature is then submitted via the submit ownership proof endpoint, which validates it cryptographically. Applies to externally owned accounts only — smart-contract accounts cannot produce this signature.",
        "operationId": "issueManualAttestation",
        "requestBody": {
          "content": {
            "application/json": {
              "schema": {
                "$ref": "#/components/schemas/TravelRuleManualAttestationRequest"
              }
            }
          },
          "required": true
        },
        "responses": {
          "200": {
            "description": "OK",
            "content": {
              "application/json": {
                "schema": {
                  "$ref": "#/components/schemas/TravelRuleManualAttestationResponse"
                }
              }
            }
          }
        }
      }
    }
  },
  "components": {
    "schemas": {
      "TravelRuleManualAttestationRequest": {
        "required": [
          "recipientId"
        ],
        "type": "object",
        "properties": {
          "recipientId": {
            "type": "string",
            "description": "Unique identifier of the self-hosted wallet recipient."
          }
        }
      },
      "TravelRuleManualAttestationResponse": {
        "type": "object",
        "description": "The manual-signing instructions: the exact attestation text the wallet holder must sign with the wallet's own key, and how to submit the resulting signature.",
        "properties": {
          "attestation": {
            "type": "string",
            "description": "The attestation text to sign, exactly as returned (for example `I certify that Ethereum account 0x71c7... belonged to did:pkh:eip155:1:0x71c7... on Mon, 14 Sep 2026 12:00:00 GMT.`)."
          },
          "type": {
            "type": "string",
            "description": "The signature scheme to pass when submitting the proof — `eip-191` for EVM wallets, `tip-191` for TRON wallets."
          },
          "walletAddress": {
            "type": "string",
            "description": "The recipient's wallet address; the signature must be produced by this address's key."
          }
        }
      }
    },
    "securitySchemes": {
      "bearerAuth": {
        "type": "http",
        "description": "JWT Bearer token authentication. Include your access token in the Authorization header:\n\n`Authorization: Bearer YOUR_ACCESS_TOKEN`\n\nTokens are obtained through the Caliza authentication flow and typically expire after 24 hours.\nRefresh your token before expiration to maintain uninterrupted access.\n",
        "scheme": "bearer",
        "bearerFormat": "JWT"
      }
    }
  }
}
```