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.

🌐 Environment Selection

To ensure the best possible access speed and stability for users worldwide, we provide multiple API environment nodes. You can choose the most suitable node based on your location:

RegionRecommended EnvironmentEnvironment URLNote
Mainland Chinaprod-cnhttp://47.117.133.51:30015Recommended: Deeply optimized for China, fastest speed
Outside Mainland Chinaprod-globalhttps://api.justoneapi.comBroad compatibility, supports HTTPS

💡 Integration Tip

If you are developing from Mainland China, we strongly recommend using the prod-cn node in your production code.

Note: Due to browser security policies, the "Try it" feature in this documentation only supports the HTTPS-enabled prod-global node. This does not affect your ability to use prod-cn in local code (e.g., Python, Java, Go, etc.).

Latency Testing

If you are unsure about the latency of your current environment, you can test it using the /ping endpoint:

  • Normal responses typically return within a few hundred milliseconds;
  • If the /ping request is significantly delayed, please try switching to another environment.

🔐 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

⏱ Timeout Recommendation

Although most API requests respond within a few seconds, we recommend setting your request timeout to at least 60 seconds.

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.

🛠 Support & Feedback

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

👉 contact us