Partner API Access Model
How Partner API access is enabled through package entitlements, rollout state, key registry controls, and contract onboarding.
Partner API Access Model
Partner API access is not a separate public self-serve pricing ladder. It is enabled through package entitlements, rollout state, key registry controls, and, for deeper integrations, contract-led onboarding.
Current access model
| Access state | Typical use | How it is enabled |
|---|---|---|
| Starter approved access | Initial integrations and sandbox validation | Access request / onboarding approval |
| Private-beta pilot | Selected workflow automation and event delivery | Waitlist / pilot enablement |
| Enterprise contract | API-heavy integrations, governance, custom limits | Contract-led rollout |
The exact API quota, webhook availability, and rollout status depend on your organisation's active entitlement set and registry key state. The dashboard and response headers are the authoritative source for current limits.
What determines access
- organisation package
- active API capability
- key registry state and scopes
- rollout state
- contract posture, if applicable
API keys
API keys prove that a caller is known and scoped. They do not, by themselves, enable public GA traffic, RFQ creation, quote automation, order automation, webhook delivery, or Master Data data-product access. Those capabilities require explicit contract and rollout enablement.
Master Data
Master Data is internal-only for external partners unless a private-beta contract and rollout explicitly enable a sanitized read projection. External GA is not enabled. Public Partner API access does not currently include externally enabled Master Data data-product endpoints, partner reads, entitlement scopes, quotas, SLAs, onboarding controls, 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
Last updated on