Operational expectations

How partner integrations should behave: scheduled exchange, issued revisions, and limits defined in the implementation agreement.

Rate limits and operational windows protect tenants and shared infrastructure. They are not published as a public numeric quota on this site because there is no generally available self-serve API to attach them to.

When partner access is provisioned, limits are part of that agreement. Bursting an application URL to scrape projects is not an approved integration pattern.

If you are designing a connector, assume:

  • you will be limited
  • you should cache issued revisions, not poll drafts every second
  • bulk export will be scheduled, not scraped
  • commercial terms remain agreement-based — there is no self-serve plan upgrade that unlocks an API

Discuss an integration to scope access.