APIs as Products
Ownership, lifecycle, deprecation policy and developer experience.
5 to work through
-
intermediate
A platform's API is used more heavily than its web interface, and third-party tools built on it drive most adoption. What changes when the API is treated as the primary product rather than as an access mechanism?
2 min answer -
intermediate Multiple choice
How do you know it is safe to remove a field from a public API, and what would you have needed to build to know that?
2 min answer -
advanced
A business-banking platform must expose payouts, balances, approvals and reconciliation to customer developers. How should the API surface be structured, and what determines what is exposed?
2 min answer -
advanced
API traffic is dominated by a few automation-heavy customers whose bursts affect everyone. How do you introduce per-tenant quotas and priority without breaking existing integrations?
3 min answer -
advanced
You must make a breaking change to an API used by 200 internal services and 40 external partners. Design the change and the migration.
2 min answer
3 terms in this topic
API Deprecation Policy
The published commitment about how long a version is supported, how notice is given, and what consumers can expect — without which nothing is ever retired.
practiceAPI Product Management
Treating an API as a product with a lifecycle — versioning, deprecation, adoption metrics and a support commitment — rather than as an implementation…
toolDeveloper Portal
The self-service surface where consumers discover APIs, read documentation, obtain credentials and test calls — the main determinant of adoption.
Neighbouring topics
API & Integration
General material on integrating systems through contracts.
REST Design
Resources, uniform methods, status codes and statelessness.
GraphQL
Client-specified queries, N+1 resolution and query-cost control.
gRPC APIs
Contract-first RPC, generated clients and protobuf compatibility rules.
Webhooks
Push callbacks, signature verification, ordering and at-least-once delivery.
API Versioning
URL, header and account-pinned versioning, and who carries the burden.
Backward Compatibility
Which changes are safe, and how to make breakage a build failure.
Contract Testing
Verifying what consumers actually rely on, without a shared environment.
API Documentation
OpenAPI as a machine-checked contract rather than as prose.
Rate Limiting
Algorithms, shared counters, and signalling rejection properly.
Idempotency Keys
Client-generated keys stored atomically with the operation they guard.
Pagination & Filtering
Offset versus cursor, stable ordering and unbounded result sets.
API Error Handling
Error shapes, retryability signals and machine-readable causes.
Event-Driven Integration
Publishing facts rather than commands, and versioning event schemas.
Message Formats
JSON, Protobuf, Avro — schema evolution and payload economics.
Schema Registry
Enforcing compatibility on events the way CI enforces it on code.
Integration Patterns
Routers, translators, splitters, aggregators and dead letter channels.
Legacy Integration
Reaching systems that cannot change, without importing their model.
Partner & B2B Integration
External contracts, onboarding, sandboxes and long deprecation windows.