> ## Documentation Index > Fetch the complete documentation index at: https://docs.spritz.finance/llms.txt > Use this file to discover all available pages before exploring further. # Submit Solana transaction > Submits the user's detached signature for a previously prepared Solana transaction. The server verifies the signature against the stored message, adds any Spritz-owned signatures such as the fee payer, serializes the transaction, and broadcasts it. If submit returns `TX_EXPIRED`, call prepare again and sign the new `messageBytes`. Retrying after a successful broadcast returns the existing transaction signature. ## OpenAPI ````yaml https://platform.spritz.finance/openapi.json post /v1/wallet-kit/solana/transactions/submit openapi: 3.0.3 info: title: Spritz Finance API version: 1.0.0 description: API for the Spritz Finance platform with RFC 9457 error handling servers: - url: https://platform.spritz.finance description: Production - url: https://sandbox.spritz.finance description: Sandbox security: [] tags: - name: Users description: User management endpoints - name: Bank Accounts description: Manage bank accounts for off-ramp destinations - name: Bills description: Manage bill pay accounts - name: Cards description: Spritz-issued debit cards - name: Auto-Ramp Accounts description: Virtual bank accounts that automatically convert fiat deposits to crypto - name: Spritz App description: >- Endpoints used by the Spritz app and internal SDKs. Excluded from the public partner spec. paths: /v1/wallet-kit/solana/transactions/submit: post: tags: - Wallet Kit summary: Submit Solana transaction description: >- Submits the user's detached signature for a previously prepared Solana transaction. The server verifies the signature against the stored message, adds any Spritz-owned signatures such as the fee payer, serializes the transaction, and broadcasts it. If submit returns `TX_EXPIRED`, call prepare again and sign the new `messageBytes`. Retrying after a successful broadcast returns the existing transaction signature. operationId: postV1Wallet-kitSolanaTransactionsSubmit requestBody: description: >- Request body for submitting the user's detached signature for a previously prepared Solana transaction. The server verifies this signature against the stored `messageBytes`, adds any Spritz-owned signatures such as the fee payer, serializes the final transaction, and broadcasts it. required: true content: application/json: schema: description: >- Request body for submitting the user's detached signature for a previously prepared Solana transaction. The server verifies this signature against the stored `messageBytes`, adds any Spritz-owned signatures such as the fee payer, serializes the final transaction, and broadcasts it. type: object properties: txId: minLength: 1 description: Server transaction id returned by the prepare endpoint. type: string userSignature: minLength: 1 description: >- Base64-encoded 64-byte ed25519 signature over the decoded `messageBytes` returned by prepare. Never send a fully signed transaction here — only the detached user signature. type: string required: - txId - userSignature application/x-www-form-urlencoded: schema: description: >- Request body for submitting the user's detached signature for a previously prepared Solana transaction. The server verifies this signature against the stored `messageBytes`, adds any Spritz-owned signatures such as the fee payer, serializes the final transaction, and broadcasts it. type: object properties: txId: minLength: 1 description: Server transaction id returned by the prepare endpoint. type: string userSignature: minLength: 1 description: >- Base64-encoded 64-byte ed25519 signature over the decoded `messageBytes` returned by prepare. Never send a fully signed transaction here — only the detached user signature. type: string required: - txId - userSignature multipart/form-data: schema: description: >- Request body for submitting the user's detached signature for a previously prepared Solana transaction. The server verifies this signature against the stored `messageBytes`, adds any Spritz-owned signatures such as the fee payer, serializes the final transaction, and broadcasts it. type: object properties: txId: minLength: 1 description: Server transaction id returned by the prepare endpoint. type: string userSignature: minLength: 1 description: >- Base64-encoded 64-byte ed25519 signature over the decoded `messageBytes` returned by prepare. Never send a fully signed transaction here — only the detached user signature. type: string required: - txId - userSignature responses: '200': description: >- Submit response. The transaction has been broadcast to the Solana cluster. If submit is retried after a successful broadcast, the existing signature is returned. content: application/json: schema: description: >- Submit response. The transaction has been broadcast to the Solana cluster. If submit is retried after a successful broadcast, the existing signature is returned. type: object properties: txId: description: Server transaction id. type: string signature: description: Solana transaction signature (base58). type: string signatureRole: description: Role of the signature returned (e.g., `fee_payer`). type: string example: fee_payer status: description: Transaction status (e.g., `submitted`). type: string example: submitted explorerUrl: description: URL to view the transaction on a Solana explorer. type: string required: - txId - signature - signatureRole - status - explorerUrl '401': description: Response for status 401 content: application/json: schema: type: object properties: type: default: about:blank description: A URI reference that identifies the problem type type: string example: urn:problem-type:auth:unauthorized title: description: A short, human-readable summary of the problem type type: string example: Unauthorized status: description: The HTTP status code type: number example: 401 detail: description: A human-readable explanation specific to this occurrence type: string example: Bearer token required instance: description: A URI reference that identifies the specific occurrence type: string realm: description: The authentication realm type: string example: API scope: description: The required scope for this resource type: string example: read:users required: - title - status additionalProperties: false '409': description: Response for status 409 content: application/json: schema: type: object properties: type: default: about:blank description: A URI reference that identifies the problem type type: string example: urn:problem-type:auth:unauthorized title: description: A short, human-readable summary of the problem type type: string example: Unauthorized status: description: The HTTP status code type: number example: 400 detail: description: A human-readable explanation specific to this occurrence type: string instance: description: A URI reference that identifies the specific occurrence type: string example: /errors/1234567890 code: description: >- Machine-readable cause, present when exactly one thing failed. Branch on this, never on `detail`, which is human-facing copy and may change. For deposit limits the vocabulary matches the `reason` values the limits API returns pre-flight. type: string example: transaction_limit field: description: The offending request field, present alongside `code`. type: string example: amountUsd retryable: description: >- Whether retrying the same request later may succeed without changing its inputs. type: boolean example: true required: - title - status additionalProperties: false '422': description: Response for status 422 content: application/json: schema: type: object properties: type: default: about:blank description: A URI reference that identifies the problem type type: string example: urn:problem-type:auth:unauthorized title: description: A short, human-readable summary of the problem type type: string example: Unauthorized status: description: The HTTP status code type: number example: 400 detail: description: A human-readable explanation specific to this occurrence type: string instance: description: A URI reference that identifies the specific occurrence type: string example: /errors/1234567890 code: description: >- Machine-readable cause, present when exactly one thing failed. Branch on this, never on `detail`, which is human-facing copy and may change. For deposit limits the vocabulary matches the `reason` values the limits API returns pre-flight. type: string example: transaction_limit field: description: The offending request field, present alongside `code`. type: string example: amountUsd retryable: description: >- Whether retrying the same request later may succeed without changing its inputs. type: boolean example: true required: - title - status additionalProperties: false '500': description: Response for status 500 content: application/json: schema: type: object properties: type: default: about:blank description: A URI reference that identifies the problem type type: string example: urn:problem-type:auth:unauthorized title: description: A short, human-readable summary of the problem type type: string example: Unauthorized status: description: The HTTP status code type: number example: 400 detail: description: A human-readable explanation specific to this occurrence type: string instance: description: A URI reference that identifies the specific occurrence type: string example: /errors/1234567890 code: description: >- Machine-readable cause, present when exactly one thing failed. Branch on this, never on `detail`, which is human-facing copy and may change. For deposit limits the vocabulary matches the `reason` values the limits API returns pre-flight. type: string example: transaction_limit field: description: The offending request field, present alongside `code`. type: string example: amountUsd retryable: description: >- Whether retrying the same request later may succeed without changing its inputs. type: boolean example: true required: - title - status additionalProperties: false '502': description: Response for status 502 content: application/json: schema: type: object properties: type: default: about:blank description: A URI reference that identifies the problem type type: string example: urn:problem-type:auth:unauthorized title: description: A short, human-readable summary of the problem type type: string example: Unauthorized status: description: The HTTP status code type: number example: 400 detail: description: A human-readable explanation specific to this occurrence type: string instance: description: A URI reference that identifies the specific occurrence type: string example: /errors/1234567890 code: description: >- Machine-readable cause, present when exactly one thing failed. Branch on this, never on `detail`, which is human-facing copy and may change. For deposit limits the vocabulary matches the `reason` values the limits API returns pre-flight. type: string example: transaction_limit field: description: The offending request field, present alongside `code`. type: string example: amountUsd retryable: description: >- Whether retrying the same request later may succeed without changing its inputs. type: boolean example: true required: - title - status additionalProperties: false '503': description: Response for status 503 content: application/json: schema: type: object properties: type: default: about:blank description: A URI reference that identifies the problem type type: string example: urn:problem-type:auth:unauthorized title: description: A short, human-readable summary of the problem type type: string example: Unauthorized status: description: The HTTP status code type: number example: 400 detail: description: A human-readable explanation specific to this occurrence type: string instance: description: A URI reference that identifies the specific occurrence type: string example: /errors/1234567890 code: description: >- Machine-readable cause, present when exactly one thing failed. Branch on this, never on `detail`, which is human-facing copy and may change. For deposit limits the vocabulary matches the `reason` values the limits API returns pre-flight. type: string example: transaction_limit field: description: The offending request field, present alongside `code`. type: string example: amountUsd retryable: description: >- Whether retrying the same request later may succeed without changing its inputs. type: boolean example: true required: - title - status additionalProperties: false security: - bearerAuth: [] components: securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: Cognito JWT token for regular user authentication ````