Requests & Limits

API variables and rate limit information for Tetreum Testnet APIs.

Tetreum Testnet is a Geth-based PoA network. Rate limits may be updated over time to ensure RPC stability and fair usage.

Public RPC Limits

Access Type

Rate Limit

Description

Public RPC (no API key)

5 req/sec

Default limit for all public requests

Temporary protected access

5 req/sec

May be used for frontend/session-based protection if enabled

Individual API key

10 req/sec

Optional higher limit for registered users or partners

Whitelisted IP

25 req/sec

Higher limit for approved server IPs

Static instance API key

10 req/sec

Optional per-instance access key

Admin key

Unlimited

Reserved for internal infrastructure and administration

Default Policy

  • Requests without an API key are limited by IP

  • Public usage is intended for wallets, developers, and light integrations

  • Heavy indexing, scraping, and bulk export usage should use dedicated infrastructure

  • Repeated abuse may result in temporary blocking

Endpoint-Specific Limits

API Endpoint

Requests per Period

Period

/api/health/*

5

1 second

/api/v2/key

Unlimited

/api/v2/import/token-info

Unlimited

/api/v2/import/smart-contracts/:param

Unlimited

/api/account/v2/authenticate_via_wallet

1

1 hour

/api/account/v2/send_otp

1

1 hour

/api/v2/tokens/:param/instances/:param/refetch-metadata

50

1 hour

/api/v2/advanced-filters/csv

50

1 hour

/api/v2/tokens/:param/holders/csv

50

1 hour

/api/v2/addresses/:param/transactions/csv

50

1 hour

/api/v2/addresses/:param/token-transfers/csv

50

1 hour

/api/v2/addresses/:param/internal-transactions/csv

50

1 hour

/api/v2/addresses/:param/logs/csv

50

1 hour

/api/v2/addresses/:param/election-rewards/csv

50

1 hour

/api/v2/smart-contracts/:param/audit-reports

50

1 hour

RPC Endpoint

Explorer

Network Details

Notes

  • Tetreum Testnet is intended for testing and development

  • Rate limits help keep the network stable for all users

  • For higher throughput access, contact the Tetreum team

  • Production integrations should avoid aggressive polling where possible

Last updated