[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"glossary-partner-api::en":3,"gloss-cluster-partner-api::en":26,"gloss-next-partner-api::en":9},{"slug":4,"category":5,"name":6,"definition":7,"meta_desc":8,"faq":9,"schema_markup":9,"related":10},"partner-api","integration","Partner API","A partner API is a tier of access a provider offers only to approved partners, separate from the public API anyone can call with a key. What sits behind the gate varies, but the pattern is recognisable: endpoints that are not publicly documented, limits that are higher or shaped differently, the ability to act across many of the provider's customers rather than one at a time, provisioning and bulk operations, and data the public surface does not expose.\n\nThe gate is commercial rather than technical. Getting through it means an agreement, sometimes a revenue arrangement, usually a review of what you intend to build, and always terms that can be changed or withdrawn. That is the part worth thinking about before you design a product around it, because a partner API is a dependency plus a relationship, and the relationship can end for reasons that have nothing to do with your engineering — a change of strategy, the provider shipping the feature you built, or an acquisition on either side.\n\nThe questions to settle in writing, while goodwill is high and nobody needs anything. What notice do you get if access is reduced or removed, and is that notice a commitment or a courtesy? Do the terms restrict what you may build, since many exclude competing with the provider's own functionality — a clause that matters most precisely when your product succeeds. Whose agreement governs your customers' data as it moves through this tier, because that determines who has to answer when a customer asks where their records went. And what are the support and escalation paths, given that partner-tier failures are usually invisible to a public status page.\n\nThen answer the internal question honestly: what does your product degrade to if this access disappears. If the answer is that it stops, that is a business risk to be held consciously and priced, not a technical detail to leave in an integration document.","A partner API is access gated by an agreement rather than a key — a dependency plus a relationship, withdrawable for reasons that are not technical.",null,[11,14,17,20,23],{"slug":12,"name":13},"api-first","API-First",{"slug":15,"name":16},"api-gateway","API Gateway",{"slug":18,"name":19},"rate-limit","Rate Limit",{"slug":21,"name":22},"sla","Service-Level Agreement (SLA)",{"slug":24,"name":25},"vendor-lock-in","Vendor Lock-In",[27,31,34,38,41,44,47,50,53,56,59,62],{"slug":28,"category":5,"name":29,"updated_at":30},"api-deprecation","API Deprecation","2026-09-08T21:32:37+00:00",{"slug":32,"category":5,"name":33,"updated_at":30},"app-review","App Review",{"slug":35,"category":5,"name":36,"updated_at":37},"backend-for-frontend","Backend for Frontend (BFF)","2026-09-08T21:32:36+00:00",{"slug":39,"category":5,"name":40,"updated_at":30},"bulk-api","Bulk API",{"slug":42,"category":5,"name":43,"updated_at":37},"concurrency-limit","Concurrency Limit",{"slug":45,"category":5,"name":46,"updated_at":30},"connector-versioning","Connector Versioning",{"slug":48,"category":5,"name":49,"updated_at":30},"delete-propagation","Delete Propagation",{"slug":51,"category":5,"name":52,"updated_at":30},"effective-permissions","Effective Permissions",{"slug":54,"category":5,"name":55,"updated_at":37},"event-ordering","Event Ordering",{"slug":57,"category":5,"name":58,"updated_at":37},"field-mapping","Field Mapping",{"slug":60,"category":5,"name":61,"updated_at":37},"function-schema","Function Schema",{"slug":63,"category":5,"name":64,"updated_at":37},"grpc","gRPC"]