Hamsa · Authentication Profile

Hamsa Authentication

Authentication

Hamsa secures its APIs with signature across 1 declared security scheme, as derived from its OpenAPI definitions.

CompanyFinancial-ServicesBlockchainPaymentsTokenizationPrivacyZero-Knowledge ProofsCBDCSettlementDeFiEVMJSON-RPC

Methods: signature Schemes: 1 OAuth flows: API key in:

Security Schemes

EthereumMessageSignature signature

scheme: ethereum-eip191

Source

Authentication Profile

generated: '2026-07-19'
method: searched
source: https://developer.hamsa.com/reference/api-documentation
docs: https://developer.hamsa.com/reference/api-documentation
summary:
  types:
  - signature
  scheme: ethereum-message-signature
  note: >-
    The Hamsa Unified Confidential Ledger (UCL) / Hamsa Privacy JSON-RPC API does
    not use API keys or OAuth. Callers authenticate protected methods by signing
    an Ethereum message with their private key and supplying their address plus
    the resulting signature (EIP-191 personal_sign style). Authorization is
    role-based access control (RBAC) enforced on-chain.
schemes:
- name: EthereumMessageSignature
  type: signature
  scheme: ethereum-eip191
  description: >-
    Sign a message with the account private key (e.g. deployer.signMessage) and
    pass the signer address and signature. Used to gate privacy-sensitive
    (protected) JSON-RPC methods.
  sources:
  - https://developer.hamsa.com/reference/api-documentation
roles:
- id: 0
  name: normal-user
  description: Can query own balances and transactions only.
- id: 1
  name: administrator
  description: Can query all balances and transactions.
protected_methods:
- eth_safeGetBalance
- eth_getTransactionHistory
unprotected_methods:
- eth_estimateGas
- eth_getNonce
- eth_getBalance
- eth_getTransactionByHash
- eth_checkTransactionBundle
- eth_blockNumber
- eth_call
- eth_chainId
- eth_gasPrice
- eth_getBlockByHash
- eth_getBlockByNumber
- eth_getBlockTransactionCountByHash
- eth_getBlockTransactionCountByNumber
- eth_getTransactionReceipt
- eth_sendRawTransaction

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This security artifact

curl "https://apis.io/api/v1/security/hamsa-authentication"

All security posture

curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.