---
title: API Usage Guide
description: Authentication, pricing, base URL, error codes, rate limits, SDKs, and MCP support for integrating JustOneAPI.
---

# API Usage Guide

Welcome to the **JustOneAPI** Official Documentation. We provide professional, stable, and high-performance data integration services, offering high-quality API interfaces across multiple sectors.

This guide will help you quickly integrate our services, covering pricing, the base URL, authentication, response handling & error codes, and rate limits.

## 💰 Pricing

You can view the specific pricing for each endpoint by logging into the system:
👉 [View Pricing](https://dashboard.justoneapi.com/en)

> **💡 Tip:** You don't need to top up immediately after registration. We provide a limited number of free calls for testing. You can recharge your account once the free credits have been used.

## 🌐 Base URL {#environment-selection}

Use the following production base URL for all API requests:

```text
https://api.justoneapi.com
```

All code samples use this base URL.

## 🔐 Authentication

To access our API, you must include your access token as a URL parameter in every request:

```
https://api.justoneapi.com/your-endpoint?token=your_access_token
```

To request a token, please [sign up](https://dashboard.justoneapi.com/en).

## 🚨 Response Handling & Error Codes

Business results should be determined by the `code` field in the response body (`code: 0` indicates success).

### Example Response

```json
{
  "code": 0,
  "message": "",
  "data": { ... }
}
```

### Business Code Reference

| `code` | Meaning                                 | Billed |
|--------|------------------------------------------|--------|
| `0`    | Success                                  | Yes 💰 |
| `100`  | Invalid or Inactive Token                | No     |
| `101`  | Whitelist Validation Failed              | No     |
| `202`  | This API version does not support the provided parameter value. Please try another version. | No |
| `300`  | API Does Not Exist or Is Inactive         | No     |
| `301`  | Collection Failed. Please Retry.         | No     |
| `302`  | Rate Limit Exceeded                      | No     |
| `303`  | Daily Quota Exceeded                     | No     |
| `400`  | Invalid Parameters                       | No     |
| `404`  | Requested API Path or Server Resource Not Found | No |
| `500`  | Internal Server Error                    | No     |
| `503`  | Service Temporarily Unavailable. Please Retry Later. | No |
| `600`  | Permission Denied                        | No     |
| `601`  | Insufficient Balance                     | No     |
| `602`  | Token Budget Exceeded                    | No     |

`601` means the shared account balance is insufficient. `602` means the API token's own cumulative budget limit has been reached. Token budget limits do not move funds out of the shared account balance; all tokens still spend from the same account balance.

## ⏱ Timeout Recommendation

Although most API requests respond within a few seconds, we recommend setting your request timeout to 120 seconds. If 120 seconds is too long for your use case, set it to at least 60 seconds, but a small number of requests may time out before receiving a result.

This does not indicate that our API is slow — it simply helps avoid unintended errors or duplicate charges due to temporary network issues or client-side timeouts.

## 🚦 Rate Limits & Quota

There are **no general rate limits** for API usage.

However, a few high-traffic endpoints may have specific rate restrictions (e.g., per minute/hour), which will be indicated in their respective documentation.

An administrator may configure a daily successful-request quota for a specific user and endpoint. No quota applies when one is not configured. Quota days follow the `Asia/Shanghai` time zone (UTC+8): synchronous requests count toward the day they are initiated, while asynchronous tasks count toward the day they are submitted. Requests from all tokens under the same account are aggregated, and only successful business responses with `code=0` count toward the quota.

After the daily quota is reached, requests to that endpoint return business code `303` with HTTP status `429` and are not billed.

## 📦 SDKs

To simplify your integration, we offer official SDKs:

- **Python SDK** <svg role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg" width="18" height="18" style="display:inline-block;vertical-align:middle;margin-top:-2px;fill:currentColor;"><path d="M12 .297c-6.63 0-12 5.373-12 12 0 5.303 3.438 9.8 8.205 11.385.6.113.82-.258.82-.577 0-.285-.01-1.04-.015-2.04-3.338.724-4.042-1.61-4.042-1.61C4.422 18.07 3.633 17.7 3.633 17.7c-1.087-.744.084-.729.084-.729 1.205.084 1.838 1.236 1.838 1.236 1.07 1.835 2.809 1.305 3.495.998.108-.776.417-1.305.76-1.605-2.665-.3-5.466-1.332-5.466-5.93 0-1.31.465-2.38 1.235-3.22-.135-.303-.54-1.523.105-3.176 0 0 1.005-.322 3.3 1.23.96-.267 1.98-.399 3-.405 1.02.006 2.04.138 3 .405 2.28-1.552 3.285-1.23 3.285-1.23.645 1.653.24 2.873.12 3.176.765.84 1.23 1.91 1.23 3.22 0 4.61-2.805 5.625-5.475 5.92.42.36.81 1.096.81 2.22 0 1.606-.015 2.896-.015 3.286 0 .315.21.69.825.57C20.565 22.092 24 17.592 24 12.297c0-6.627-5.373-12-12-12"/></svg>: [justoneapi-python](https://github.com/justoneapi-official/justoneapi-python)

## 🤖 MCP Support

To help AI assistants discover and call endpoints, we offer an official MCP server:

- **MCP Server** <svg role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg" width="18" height="18" style="display:inline-block;vertical-align:middle;margin-top:-2px;fill:currentColor;"><path d="M12 .297c-6.63 0-12 5.373-12 12 0 5.303 3.438 9.8 8.205 11.385.6.113.82-.258.82-.577 0-.285-.01-1.04-.015-2.04-3.338.724-4.042-1.61-4.042-1.61C4.422 18.07 3.633 17.7 3.633 17.7c-1.087-.744.084-.729.084-.729 1.205.084 1.838 1.236 1.838 1.236 1.07 1.835 2.809 1.305 3.495.998.108-.776.417-1.305.76-1.605-2.665-.3-5.466-1.332-5.466-5.93 0-1.31.465-2.38 1.235-3.22-.135-.303-.54-1.523.105-3.176 0 0 1.005-.322 3.3 1.23.96-.267 1.98-.399 3-.405 1.02.006 2.04.138 3 .405 2.28-1.552 3.285-1.23 3.285-1.23.645 1.653.24 2.873.12 3.176.765.84 1.23 1.91 1.23 3.22 0 4.61-2.805 5.625-5.475 5.92.42.36.81 1.096.81 2.22 0 1.606-.015 2.896-.015 3.286 0 .315.21.69.825.57C20.565 22.092 24 17.592 24 12.297c0-6.627-5.373-12-12-12"/></svg>: [justoneapi-mcp](https://github.com/justoneapi-official/justoneapi-mcp)

## Third-party access via FluxA {#fluxa-access}

Some JustOneAPI endpoints are available to AI agents through FluxA, a third-party platform offering pay-per-call access. This route does not require you to create a separate JustOneAPI account or manage an API key for JustOneAPI.

To use it, you need a FluxA wallet or another payment method supported by FluxA. Available endpoints, prices, and payment terms are listed on FluxA. You can continue using your existing JustOneAPI account or official MCP setup.

👉 [View supported APIs and access options on FluxA](https://agentmarket.fluxapay.xyz/marketplace/apis/justoneapi)

## 🛠 Support & Feedback

For any questions, integration support, or to request a custom solution, feel free to reach out via our support page:

👉 [contact us](https://justoneapi.com/en/contact)
