Skip to main content

​
Authentication

TeQoin exposes public infrastructure with different authentication expectations depending on the surface you use.

​
JSON-RPC

The public RPC endpoint shown in this docs repo is:
The examples in this documentation use it without an API key.

​
REST-style APIs

The TeQoin docs also reference https://api.teqoin.io for application-facing APIs. When TeQoin publishes protected endpoints, expect one of these common patterns:
  • Bearer token in the Authorization header
  • API key in a custom header
  • IP-based access for dedicated infrastructure

​
Recommendation

If your team issues API credentials:
  • Store them in environment variables
  • Never hardcode them in frontend bundles
  • Rotate them when you change environments