Nansen API
  • ✨Introduction
  • 📌Endpoints Overview
  • 🔴Rate Limits and Quotas
  • Getting Started
    • ☑️Prerequisites
    • 🌐API Structure & Base URL
    • 🔓Authentication
    • 🟢Understanding Responses and Handling Errors
    • ⛓️Chain Coverage
  • API
    • Smart Money
    • Profiler
      • Balances
      • Transactions
      • Counterparties
      • Trade Performance
      • Labels
    • Token God Mode
      • Token Overview
      • Transactions
      • Holders
      • Exchanges
      • PnL Leaderboard
  • Other Endpoints
  • Guides
    • 💻Endpoint Showcase
    • 🙋Frequently Asked Questions
  • 🔗Useful Links
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. Getting Started

Understanding Responses and Handling Errors

API responses are delivered in JSON format. The client applications must parse this JSON to extract the required data. Equally important is handling the HTTP status code returned with each response to determine success or failure.

Common HTTP Status Codes:

Status Code
Description

200 OK

The request was successful, and the response body contains the requested data.

400 Bad Request

The request was malformed (e.g., invalid parameters, incorrect format). Check the request syntax and parameters.

401 Unauthorized

Authentication failed. The access token is missing, invalid, or expired. Obtain/refresh the token.

403 Forbidden

Authentication succeeded, but the user does not have permission to access the requested resource

404 Not Found

The requested resource (e.g., specific address, endpoint path) does not exist.

429 Too Many Requests

The client has exceeded the allocated rate limit.

500 Internal Server Error

An unexpected error occurred on Nansen's servers.

504 Gateway Timeout

API didn't get a timely response from backend server

PreviousAuthenticationNextChain Coverage

Last updated 2 days ago

Was this helpful?

🟢