How to Avoid API and OData Throttling in OnePlan

  • Updated
What is throttling, and why is it happening?
OnePlan now enforces request rate limits on REST API and OData connections to ensure consistent platform performance for all users. If your integrations, reports, or automated processes send too many requests in a short period of time, OnePlan will throttle those requests — and if usage continues to exceed the limits, you may receive a 429 Too Many Requests response until your usage returns within the allowed thresholds.
What are the rate limits?
Connection Type
Per Minute
Per Hour
Per Day
REST API
500 requests
25,000 requests
300,000 requests
OData
1,000 requests
25,000 requests
300,000 requests
Limits apply per OnePlan group.
How do I check my group's current usage?

You can check the current request usage for your OnePlan group using the following URLs. Replace [ConfigID] with your group's Config ID before navigating to the link.

REST API Usage:

https://global.oneplan.ai/api/apilog?ConfigId=[ConfigID]&Target=API

OData Usage:

https://global.oneplan.ai/api/apilog?ConfigId=[ConfigID]&Target=OData

To find your Config ID:

  1. Open OnePlan and select your Profile from the top-right dropdown.
  2. Locate the Share With URL — your Config ID is included in that URL.
What should I check first if I'm being throttled?
The most common cause of throttling is multiple connections or processes running at the same time and collectively exceeding the limits. Review the following:
  • OneConnect integrations — Check whether any OneConnect jobs are scheduled to run concurrently. Stagger their execution so they run sequentially rather than simultaneously.
  • Other API integrations — If you have additional third-party or custom integrations calling the OnePlan API, review their scheduling alongside OneConnect to avoid overlapping request spikes.
  • Power BI or OData report refreshes — Multiple reports refreshing at the same time can generate a high volume of OData requests in a short window. Stagger your refresh schedules to spread the load across time.
  • Automated processes — Any scheduled jobs, workflows, or scripts that call the OnePlan API should be reviewed to ensure they are not triggering simultaneously.
Are there any endpoint changes I need to make?
Yes. API and OData requests should be made through the mygraph.oneplan.ai endpoint. Connections using the my.oneplan.ai endpoint should be updated. This applies to integrations, applications, and OData-based reports such as those built in Power BI. 
Learn More on updates needed to the endpoints.
What's the best practice to avoid throttling going forward?
  • Use the mygraph.oneplan.ai endpoint for all REST API and OData connections.
  • Stagger scheduled processes — avoid running integrations, report refreshes, and automated jobs concurrently.
  • Audit all connection sources — consider the combined request volume of OneConnect, third-party integrations, and reporting tools together, not individually.
What happens if I hit the limit?
Requests that exceed the rate limits will be throttled. If usage continues beyond the thresholds, affected requests will receive a 429 Too Many Requests response. Normal access resumes automatically once usage returns within the allowed limits.

Was this article helpful?

0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.