Skip to content
Nodely

Make your first Algorand API call

View Markdown · Agent resources · Search all content

Nodely provides two Algorand APIs: Algod reads node state and submits transactions; Indexer searches indexed blockchain data. Begin on testnet. These read-only examples need curl, internet access and no API key.

1. Read node status

Section titled “1. Read node status”
Terminal window
curl --fail-with-body https://testnet-api.4160.nodely.dev/v2/status

A successful response is a JSON object containing last-round, the node’s current round. The value changes as the network produces blocks. This request does not create or submit a transaction.

2. Read indexer data

Section titled “2. Read indexer data”
Terminal window
curl --fail-with-body 'https://testnet-idx.4160.nodely.dev/v2/transactions?limit=1'

The response contains a transactions array and current-round. An empty array is valid. For larger result sets, use the returned pagination token as described in the Indexer specification.

3. Choose the right network and access plan

Section titled “3. Choose the right network and access plan”
  • Use the endpoint matrix to select mainnet, testnet or another supported AVM chain.
  • Free endpoints work without tokens, subject to the usage policy.
  • Boost uses public nodely.dev hosts with paid authentication.
  • Unlimited and Enterprise use the commercial endpoints in the Unlimited guide.
  • Compare current prices and included services on Pricing.

When using an Algorand SDK, configure the base host without appending /v2. The SDK constructs operation paths. See the JavaScript and Python examples.

4. Authenticate when using a paid plan

Section titled “4. Authenticate when using a paid plan”

Keep tokens in your backend environment. For example, with a token from the Nodely portal:

Terminal window
curl --fail-with-body \
  -H "X-API-Key: $NODELY_TOKEN" \
  https://mainnet-api.4160.nodely.io/v2/status

Use the host appropriate to your plan. Browser applications should use verified sites instead of embedding a secret token. The authentication guide covers SDK headers, verified sites, and eligible IP whitelists.

5. Handle errors and reduce repeated work

Section titled “5. Handle errors and reduce repeated work”
  • On 429, reduce concurrency and use exponential backoff with jitter. Honor Retry-After when supplied.
  • On a 403 quota response, inspect the response body and current quota. Retrying continuously will not restore a used daily allowance.
  • Cache immutable block and transaction data; avoid requesting identical history repeatedly.
  • Limit pagination concurrency and request only the new data your application needs.

Read the current limits and quota reset rules and free-tier usage policy before increasing traffic.

Next steps

Section titled “Next steps”