API Overview

Triport is a single multi-chain RPC platform for Solana, Ethereum, and Polygon — JSON-RPC, a REST product layer, and WebSocket streaming, all behind one base URL and one API key.

What Triport is

Triport is a multi-chain RPC platform. You send standard requests to a single base URL; Triport authenticates your key, routes the request to the right network backend, enforces your tier's rate limits, and returns the upstream result unchanged. You integrate against one API surface instead of wiring up a separate provider per chain.

Three networks are supported today:

• Solana
• Ethereum
• Polygon (PoS)

Across those networks Triport exposes three kinds of surface:

Base URLs

There are two environments. Both speak the same protocol; staging is for integration testing and may serve non-production data.

Each network has its own path prefix off the base URL:

A minimal first request (Solana getBalance against production):

curl https://api.triport.io/sol \
  -H "x-token: $TRIPORT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "getBalance",
    "params": ["vines1vzrYbzLMRdu58ou5XTby4qAqVRLmqo36NKPTg"]
  }'

If you have never called Triport before, start with Getting Started — it takes you from zero to a verified response in under five minutes.

Authentication, briefly

Send your API key (it looks like nl_live_…). Triport accepts it in several forms, tried in this priority order:

1. x-token: <key> header — preferred, used by the SDKs.
2. Authorization: Bearer <key> header — standard Bearer scheme.
3. ?api-key=<key> query parameter — legacy.
4. Path form /<chain>/<key> — works only for nl_live_* API keys.

Full details and when to use each are on the Authentication page.

Rate limits, briefly

Triport rate-limits by sustained requests-per-second, scoped to your tier and the request's category, with a global burst multiplier of 2×. There is no daily quota — only the per-second budget. Tiers range from the free 7-day trial through basic, pro, business, and custom enterprise; higher tiers unlock more RPS and multi-region routing.

Rate-limit state is reported on responses via X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, and X-RateLimit-Category. When you exceed your budget you get HTTP 429 with a Retry-After header. See Rate Limits for the per-tier numbers and burst behavior.

Errors, briefly

Every error comes back as a JSON envelope with a machine-readable error code, a human message, and a request_id for support. The codes you will see most:

Over JSON-RPC, these map to wire codes -32002 (tier_insufficient), -32003 (rate_limited), and -32601 (method_unknown). See the Errors page for the full envelope and typed error schemas.

Surface reference — where to go next

Guides

Solana

Ethereum

Polygon

SDKs

You can call any surface directly over HTTP/WSS, or use an official SDK that wraps auth, retries, and rate-limit handling for you:

• TypeScript — @triport/sdk
• Python — triport-sdk

Both default to the x-token header and the production base URL. See Getting Started for installable examples in each.

Notes

• All three networks share one key, one error envelope, and one rate-limit model — what you learn for Solana applies to Ethereum and Polygon.
• Raw JSON-RPC results are passed through unchanged from the upstream node, so existing chain tooling and method docs continue to apply.
• Use staging (https://staging.api.triport.io) for integration tests so your production RPS budget is unaffected.