List wallet signing configs

Returns the active Config-owned wallet signing configurations for the requested scope, one per provider.

GET/v1/wallets/configsRun in dashboard

Requires an API key with the wallets.read action.

Headers

  • x-project-id · string · min length 1 · example prj_example

    Required for dashboard sessions. API keys use their assigned project.

Responses

  • 200 Wallet signing configurations

    • data · object · required

      Wallet signing configurations response payload.

      • configs · object[] · required

        Active wallet signing configurations for the requested scope.

        • id · string · required · example cfg_example

          Wallet signing config ID.

        • organizationId · string · required · example org_example

          Organization ID that owns this wallet signing config.

        • projectId · string | null · required · min length 1 · example prj_example

          Optional project scope for this config.

        • provider · string · required · one of local, fireblocks, privy, coinbase_cdp, para, turnkey, dfns, ibm_haven, anchorage, utila · example privy

          Wallet signing provider.

        • status · string · required · one of active, inactive · example active

          Config status.

        • createdAt · string · required · format date-time · example 2025-01-01T00:00:00.000Z

          ISO 8601 timestamp.

    • meta · object · required

      Response metadata.

      • requestId · string · required · min length 1 · example req_example

        Request identifier for tracing.

      • timestamp · string · required · format date-time · example 2025-01-01T00:00:00.000Z

        ISO 8601 timestamp.

  • 401 Unauthorized

    • error · object · required

      Standard error payload.

      • code · string · required

        Machine-readable error code.

      • message · string · required

        Human-readable error message.

      • details · object

        Optional error details for debugging.

        • * · any

    • meta · object

      • requestId · string · min length 1 · example req_example

        Request identifier for tracing.

  • 403 Forbidden. Requires the wallets.read action: an API key must hold it (a module's manage or execute also covers its read), and a signed-in member's organization role must include it. Without it the error is INSUFFICIENT_PERMISSIONS and error.details.action names the action. Any other 403 names its own reason.

    Same fields as 401.

  • 500 Internal Server Error

    Same fields as 401.

Example request

curl 'https://api.solana.com/v1/wallets/configs' \
  -H "Authorization: Bearer $SDP_API_KEY"

Example responses

{
  "data": {
    "configs": [
      {
        "id": "cfg_example",
        "organizationId": "org_example",
        "projectId": "prj_example",
        "provider": "privy",
        "status": "active",
        "createdAt": "2025-01-01T00:00:00.000Z"
      }
    ]
  },
  "meta": {
    "requestId": "req_example",
    "timestamp": "2025-01-01T00:00:00.000Z"
  }
}

Error responses use the standard error shape.

Is this page helpful?