Server-to-server

GET /v1/s2s/wallets HTTP/1.1
Host: api.sigilkeys.com
Authorization: Bearer sk_live_xxx

GET /v1/s2s/wallets

List all wallets in your org. For back-office tools, billing, reconciliation. Joins wallets ⨝ user_identities.

Query params:

Name	Type	Default	Notes
limit	int	50	Max 200.
offset	int	0

Response:

{
  "data": {
    "items": [
      {
        "id": "wal_xxx",
        "address": "0x…",
        "user_identity_id": "usr_xxx",
        "email": "alice@example.com",
        "provider_user_id": "alice@example.com",
        "auth_provider": "sigil",
        "chain_type": "evm",
        "status": "active",
        "created_at": "2026-05-04T22:00:00Z"
      }
    ],
    "total": 42,
    "limit": 50,
    "offset": 0
  },
  "error": null
}

GET /v1/s2s/wallets/{wallet_id}

Single wallet by id. Same fields as the list item.

What this lane does NOT expose

• Read or write any share (encrypted or not).
• Sign on behalf of an end user.
• Modify org settings.
• Mint or revoke API keys.

If you need a flow not covered here, file an issue and we’ll evaluate adding it under S2S.