API Reference

Complete reference for the Solami RPC and REST APIs.

Solami exposes two API surfaces: a JSON-RPC API for all Solana node methods and a REST API for managing your account, keys, billing, and usage.

Base URLs

Service	Base URL
RPC	https://rpc.solami.fast/sol
REST	https://api.solami.fast
gRPC	https://grpc.solami.fast
WebSocket	wss://rpc.solami.fast/ws/sol

Authentication

All requests require an API key passed as the api_key query parameter:

https://rpc.solami.fast/sol?api_key=YOUR_API_KEY

You can create and manage API keys in the Dashboard or via the API Keys REST endpoint.

Your API key is tied to your plan’s rate limits. Keep it secret and rotate it immediately if it is compromised.

JSON-RPC request format

All RPC requests use POST with a JSON-RPC 2.0 body:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "METHOD_NAME",
  "params": []
}

Field	Description
jsonrpc	Always "2.0".
id	Client-chosen identifier echoed back in the response.
method	The RPC method name (e.g. getBalance).
params	Array of method-specific parameters.

Responses follow the same envelope:

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {}
}

On error, the response includes an error object with a code and message instead of result.

Rate limits

Rate limits apply per API key based on your plan.

Plan	Requests/s	sendTransaction/s
Free	5	1
Dev	50	5
Pro	200	20
Ultra	500	50
Shared Metal	2,000	200

When you exceed the limit, the API returns 429 Too Many Requests. Upgrade your plan on the pricing page or contact support for higher limits.

HTTP error codes

Code	Meaning
200	Success.
400	Bad request — malformed JSON or invalid parameters.
401	Unauthorized — missing or invalid API key.
403	Forbidden — your plan does not include this feature.
429	Too many requests — you have exceeded your plan’s rate limit.
500	Internal server error — something went wrong on Solami’s end.
503	Service unavailable — the node is temporarily unreachable. Retry with backoff.

REST API

The REST API at https://api.solami.fast provides endpoints for account management. All REST requests require your API key as the api_key query parameter or in the Authorization: Bearer header.

See the REST reference pages:

• API Keys — create, list, and revoke keys
• Billing — subscription and balance info
• Usage — request counts and method breakdowns