Partner API Access Model
How Partner API access is enabled through package entitlements, rollout state and contract onboarding.
Partner API Access Model
Partner API access is no longer described as a separate public self-serve pricing ladder. It is enabled through package entitlements, rollout state and, for deeper integrations, contract-led onboarding.
Current access model
| Access state | Typical use | How it is enabled |
|---|---|---|
| Starter approved access | Initial integrations, sandbox validation and selected production workflows | Access request / onboarding approval |
| Pro pilot | Advanced automation and expanded workflow pilots | Waitlist / pilot enablement |
| Enterprise contract | API-heavy integrations, governance, higher limits and custom support | Contract-led rollout |
The exact API quota, webhook availability and rollout status depend on your organisation's active entitlement set. The dashboard and response headers are the authoritative source for current limits.
What determines access
- organisation package
- active API capability
- rollout state
- contract posture, if applicable
Master Data
Master Data is internal-only for public Partner API users. External data-product access, partner entitlement scopes, quotas, SLAs and onboarding controls remain a future maturity track. Public Partner API access does not currently include externally enabled Master Data data-product endpoints or canonical write authority.
Master Data external-dark
Contract-ready does not mean externally enabled. Keep Master Data partner reads dark until runtime auth, audit, quota, onboarding, legal controls, certification controls, and production evidence are complete. Public/partner payloads must stay sanitized and cannot leak private evidence, cost, margin, payout, supplier source or rate-card fields.
FAQ
Can I just upgrade from a self-serve billing page?
Not always. Partner API access is usually enabled through approval, pilot or contract workflow rather than a generic checkout flow.
What happens if I exceed my quota?
If you exceed your current entitlement quota, the API returns 429 Rate Limit Exceeded. Review your current access level or request broader access.
War dieser Artikel hilfreich?
Verwandte Artikel
Zuletzt aktualisiert