Skip to content

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, environment selection, 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 URLs

Use prod-global by default. Mainland China users can also use prod-cn.

EnvironmentURLNote
prod-globalhttps://api.justoneapi.comDefault recommendation
prod-cnhttp://47.117.133.51:30015Optional for Mainland China

Code samples use https://api.justoneapi.com by default. To use prod-cn, use http://47.117.133.51:30015 instead.

🔐 Authentication

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

http://<ip:port>/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

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

Business Code Reference

codeMeaningBilled
0SuccessYes 💰
100Invalid or Inactive TokenNo
301Collection Failed. Please Retry.No
302Rate Limit ExceededNo
303Daily Quota ExceededNo
400Invalid ParametersNo
500Internal Server ErrorNo
600Permission DeniedNo
601Insufficient BalanceNo
602Token Budget ExceededNo

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.

📦 SDKs

To simplify your integration, we offer official SDKs:

🛠 Support & Feedback

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

👉 contact us