Partners are the business relationship that sits between public developers and enterprise customers, and the partner tier is one of the most valuable and most underdeveloped parts of most API programs. A partner is an organization granted elevated, often privileged, API access to build joint business value — not a random developer who signed up for a key, and not exactly a customer who pays for a product, but a business with whom you have a deliberate, mutual relationship mediated through the API. The partner relationship is where APIs do some of their most strategically important business work, because partners build deep integrations, extend your reach, and create value that flows both ways. I’ve long argued that the partner tier deserves far more attention than it gets, because it’s where some of the highest-value, most durable business relationships in the entire API economy live.
The foundational insight, which I wrote about in 2011, is that APIs power partner relationships — they’re a new and more efficient mechanism for doing business development. Before APIs, partnerships required lengthy negotiations, custom integrations, and formal contracts for every relationship. APIs changed this by providing a standardized, self-service-capable interface through which partners could integrate, which is the Biz Dev 2.0 insight applied to the partner tier specifically. The API partner platform, which I wrote about in 2011, is the infrastructure for this — a distinct tier of access and capability designed for partners, separate from the public developer program and the internal teams. Recognizing partners as their own tier, with their own access, their own onboarding, and their own relationship management, is the first step toward doing the partner business well.
The partner tier’s place in the API business ecosystem is precise, and I mapped it in 2012 with the four levels of an API business ecosystem — internal, partner, public developer, and broadly open. The partner level is distinct: partners get more access than public developers (often including write access, higher rate limits, and capabilities not exposed publicly) because there’s a trusted business relationship and mutual accountability. The partner tier is where you can do things you can’t do with anonymous public developers — share more sensitive capabilities, build deeper integrations, take on more risk — because the relationship is known and the incentives are aligned. The distinction between the partner tier and the public tier is fundamentally about trust and mutual value: partners get elevated access because they’re bringing something to the relationship, and the access is calibrated to the depth of the business relationship.
The leading partner programs offer real lessons, and I studied them deliberately. I took a look at the leading API partner programs in 2014 — Salesforce, Amazon, eBay, Facebook, Twitter, LinkedIn, and others — because the companies that built the strongest partner ecosystems had figured out something important about structuring these relationships. The best partner programs have clear tiers, defined benefits, real revenue-sharing or business incentives, certification processes, and dedicated support. The building blocks of API partner programs, which I documented comprehensively in 2020, include purpose, onboarding, access, education, business incentives, innovation, exposure, marketing, branding, communications, events, support, platform resources, observability, and accreditation — a full apparatus for managing partner relationships at scale. A serious partner program is a substantial operation, because the partner relationships are valuable enough to warrant the investment.
Working with partners to iterate is one of the highest-value uses of the partner relationship, and it’s something I’ve emphasized repeatedly. I wrote in 2014 about working with your partners to iterate on your APIs — because your trusted partners are your most engaged, most knowledgeable early users, and co-developing with them in a closed, trusted environment produces better APIs than designing in isolation. Partners give you real feedback from real integration work, they tolerate the rough edges of early versions, and they help you understand what the API actually needs to do. The partner tier is, in this sense, a product development asset as much as a distribution channel — the place where you can develop and refine capabilities with engaged collaborators before exposing them more broadly. Certified partner applications and ecosystems, which I wrote about in 2016, extend this trust outward, letting you vouch for the quality of what partners build.
The fluidity between tiers is the strategic nuance that completes the picture, and it’s where partner strategy gets interesting. APIs move between tiers over their lifecycle — I wrote in 2017 about moving APIs out of the partner realm and making them more public, the progression where a capability is first developed and proven with partners, then graduated to public availability once it’s mature. This is a deliberate strategy: use the trusted partner tier to develop and prove a capability, then open it more broadly when it’s ready. The reverse happens too, where capabilities get restricted to the partner tier for business or trust reasons. The “can I resell your API” question I raised in 2018 points at another partner dynamic — the reseller relationship, where partners don’t just consume your API but redistribute it, which requires its own business and legal structure. The partner tier is dynamic, with capabilities flowing in and out of it based on maturity, trust, and business strategy. The deepest lesson about partners is that they represent the API economy’s most relationship-intensive, highest-trust, and often highest-value tier — the place where APIs do genuine business development, where capabilities get developed with engaged collaborators, and where the mutual value of a real business relationship gets realized through technical integration. Most API programs over-invest in the public developer tier, which gets the attention, and under-invest in the partner tier, which often generates more durable value. Getting the partner relationship right — the elevated access, the mutual accountability, the co-development, the clear program structure — is one of the most underrated ways to build a successful API business.
References
- APIs Power Partner Relationships
- Beyond Partners And Developers With Your API
- API Partner Platforms
- Four Potential Levels Of An API Business Ecosystem
- Work With Your Partners To Iterate On Your APIs
- Taking A Quick Look At The Leading API Partner Programs
- How Do I Provide A List Of Certified Applications To My API Ecosystem Partners
- Moving APIs Out Of The Partner Realm And Making Them More Public
- Can I Resell Your API?
- The Building Blocks Of API Partner Programs
