API Usage Guide

Welcome to the Just One API 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

💡 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

Use the following production base URL for all API requests:

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.

🚨 Response Handling & Error Codes

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

Example Response

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

Business Code Reference

code	Meaning	Billed
0	Success	Yes 💰
100	Invalid or Inactive Token	No
301	Collection Failed. Please Retry.	No
302	Rate Limit Exceeded	No
303	Daily Quota Exceeded	No
400	Invalid Parameters	No
500	Internal Server Error	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 : justoneapi-python

🤖 MCP Support

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

• MCP Server : justoneapi-mcp

🛠 Support & Feedback

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

👉 contact us