APIFree

Free endpoints and info


Free (as in 🍺) Algorand API access

  • 6000 requests/s globally per site
  • 50 requests/s per IP/browser (boost available upon Discord DM)
  • Vanilla API (so you can migrate to you own hosting)
  • No tokens, no setup, no surprises

Highly available Algorand Endpoints

  • Cloudflare automatic geo balancing to 20 geo locations
  • Preflight acceleration (200+ locations)
  • Best for production (backend & frontend)
NetworkFull Indexer v2 APIFull Algod v2 API
MainNethttps://mainnet-idx.algonode.cloudhttps://mainnet-api.algonode.cloud
TestNethttps://testnet-idx.algonode.cloudhttps://testnet-api.algonode.cloud
BetaNethttps://betanet-idx.algonode.cloudhttps://betanet-api.algonode.cloud

Ultra low latency DNS balanced Algorand Endpoints

  • Bunny.net Geo DNS balanced across 30+ locations
  • Best for dev/batch/analytics
  • Lower latencies in Africa/Nigeria and South America
NetworkFull Indexer v2 APIFull Algod v2 API
MainNethttps://mainnet-idx.algonode.networkhttps://mainnet-api.algonode.network
TestNethttps://testnet-idx.algonode.networkhttps://testnet-api.algonode.network
BetaNetn/an/a

2023 will introduce fully decentralized (no DNS, no centralized CA, censorship resistant) algo.api endpoints.

Documentation

AlgoNode hosts vanilla Algod API and indexer API - just drop the URL in your SDK and you are good to go.
Do not add /v2 or / at the end of the endpoint.

Click on a Front-End URL to proceed to online Algod Swagger or Indexer Swagger documentation / API playground

HA endpoints
  • can be used by all Algorand SDKs
  • preflight queries are answered at the edge
  • are SSL and CORS enabled
  • are geographically balanced by Cloudflare
  • have per source IP limits of 50 rps with request shaping
  • can be used universally by frontend and backend
LL endpoints:
  • have lower latency than front HA endpoints
  • are better suited for backend
  • are geographically balanced by Bunny.net
  • have per source IP limits of 50 rps with request shaping
Latencies

Click the Keycdn report below to test the latencies yourself.

aa

API Changes

We lied - the hosted API has some minor differences:

  • our /v2/transactions/pending/{txid} is 600 times faster than vanilla implementation

Limits

The API requests are rate limited per source IP address with request shaping. A burst of 90 rps is allowed and all responses are delayed artificially to make sure that (if called sequentially) they will not exceed the quota. Queries exceeding the 90rps in burst or sustained 60rps will get HTTP 429 error.

If your code is doing synchronous (as in await) requests in sequence (one after another) then our load balancers will make sure they do not exceed 60 rps. Otherwise please make sure that parallel threads follow the rules:

  • add 100ms delay between requests
  • use no more than 5 parallel threads
  • use back off algorithm for retries in case of errors, unexpected results, loops

AlgoNode is able to issue temporary tokens that allow TENFOLD increase of limits in case of major events (Airdrops, Shuffles, product launch, etc)

What happens if I abuse the limits … ?

We reserve the right to automagically forward your traffic away from edge regions to central regions. This adds +200ms latency but makes sure our edges serve low-latency responses to casual users.

This defense mechanism is triggered when :

  • a single IP range generates > 25rps on average for more then 1hr
  • a single IP range generates > 10 000 requests that end up in code 429 (request limit)

We have our secret ways of identifying single source of requests even if it jumps across a pool of IP addresses 😈

Tokens

  • All APIs are accessible without any tokens.

Rulez

See FAQ for extra info on why all this is free - with no strings attached.
Just consider becoming a commercial customer once your project becomes profitable.

Monitoring

Anonymized logs with all requests to the free endpoints are public and accessible through our dashboard Dashboard

Read more about our dashboard in this blog post.

Example usage in SDK

Javascript
const token = '';
const server = 'https://testnet-api.algonode.cloud';
const port = 443;
const client = new algosdk.Algodv2(token, server, port);

(async () => {
  console.log(await client.status().do());
})().catch((e) => {
  console.log(e);
});
REACH

Algonode is default API provider here :D

API geographic regions

AlgoNode hosts APIs in multiple regions around the World. The table below show network API availability per region.
When a region has no dedicated infra for a network the API queries are redirected to the nearest supported region.
All regions handle Free API endpoints. Full regions have the ability to host commercial API as well.

Full RegionMainNetTestNetBetaNet
US-East (Ashburn)✅Free
✅Commercial
✅Free-
EU-Central (Germany)✅Free
✅Commercial
✅Free✅Free
EU-North (Finland)✅Free
✅Commercial
✅Free-
Singapore✅Free
✅Commercial
✅Free-
Edge RegionMainNetTestNetBetaNet
UK (London)✅Free✅Free-
USA (San Jose)✅Free✅Free-
USA (Honolulu)✅Free✅Free-
Australia (Melbourne)✅Free✅Free-
Japan (Osaka)✅Free✅Free-
India (Mumbai)✅Free✅Free-
Brasil (Vinhedo)✅Free✅Free-
South Africa (Johannesburg)✅Free✅Free-
Israel (Jerusalem)✅Free✅Free-
Nigeria (Lagos)✅Free✅Free-
Chile (Santiago)✅Free✅Free-
Mexico (Queretaro)✅Free✅Free-
UAE (Dubai)✅Free✅Free-
US/DallasQ3'22Q3'22-
US/SeattleQ3'22Q3'22-
US/MiamiQ3'22Q3'22-
US/ChicagoQ3'22Q3'22-
SpainQ4'22Q4'22-
China (HGK)Q2'30Q2'30-
  • Full regions contain both edge and archive nodes & indexers
  • Edge regions serve 85% to 95% of requests locally from edge nodes/indexers and forward the rest to the closest Full region

Preflight (CORS) queries are handled locally in 200+ locations to speed up front-end API requests that generate OPTIONS requests before each call.

Secret APIs

Some secret endpoints exists but they :

  • are supported only in commercial offerings
  • are made possible with our open source code

Apps that use AlgoNode free endpoints

SDKs that set AlgoNode as default API provider (❤️)