API & Platform Products

APIs run as products: an inventory and design rules, versioning and auth decisions, a developer portal people succeed with, routines that keep the platform healthy, and the partners and enterprises building on it.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for API & Platform Products, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

198

Starter tasks

🧩 Product Management

API & Platform Products

Managing APIs and developer platforms as products, with documentation, versioning, developer experience and partners treated as real customers.

  1. API product inventory and ownership map
  2. Developer personas and top integration use cases
  3. Developer experience metrics baseline
  4. API design guidelines for every team
  5. Contract-first API specification workflow
  6. Authentication and authorisation model decision
  7. Versioning and breaking change policy
  8. Rate limits and quota policy
  9. Developer portal first release
  10. Weekly API health review
  11. API design review routine
  12. Developer support triage and pain point themes
  13. Deprecation calendar for endpoints and versions
  14. Monthly developer experience metrics review
  15. Documentation testing against the live API
  16. Quarterly reviews with top API partners
  17. Consumer contract tests in the release pipeline
  18. API status page and uptime reporting
  19. API security review against common risks
  20. REST resource modelling and HTTP semantics
  21. Hands-on first hundred calls to your own API
  22. Webhooks and event delivery fundamentals
  23. GraphQL, gRPC and REST trade-offs
  24. Idempotency, pagination and concurrency patterns
  25. OAuth 2.0 flows for product people
  26. Reading API traffic data yourself
  27. Cutting time to first successful call
  28. Error responses developers can act on
  29. SDK and client library strategy
  30. API gateway and management platform choice
  31. Sandbox environment developers can trust
  32. Use-case recipes and code samples library
  33. Webhooks product specification
  34. Public, partner and internal exposure decisions
  35. Public API launch readiness and go decision
  36. Major version migration programme
  37. Planned brownouts before a version shutoff
  38. Developer conference or hackathon
  39. Annual developer survey
  40. Engineer moving into API product management
  41. Taking over an API nobody owns
  42. Internal API platform for other engineering teams
  43. Enterprise customer API onboarding
  44. Partner programme for companies building on the API
  45. First public API at a small company
  46. API ecosystem health metrics
  47. API governance across many teams
  48. Regional endpoints and data residency
  49. API abuse, scraping and leaked key defence
  50. API readiness for AI agents and assistants

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

API product inventory and ownership map

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Most companies that have shipped APIs for a few years cannot say how many they run: the public REST API, two partner endpoints built for one deal, a webhook service and a dozen internal APIs other teams quietly depend on.

First tasks

  • Export the list of hosts and routes seen by the API gateway in the last 90 days
  • Match each route to a documented API or mark it undocumented
  • Ask each engineering lead to confirm the owner of their APIs
  • Flag APIs with no owner or no recent traffic for a keep or retire decision
  • Refresh the inventory against gateway traffic @recurring(quarterly)

Developer personas and top integration use cases

Developers who call your API are not one audience: an integration engineer at a large customer, a solo developer at an agency building for clients, a partner company shipping a connector and an internal team on a deadline all want different things. Writing down who they are and the five jobs they most often use the API for gives docs, SDKs and the roadmap a shared target.

First tasks

  • Pull the job titles and company sizes of the last 200 API key sign-ups
  • Interview five developers who built a live integration in the last six months
  • Rank integration use cases by count of active apps
  • Write a one-page persona for each distinct type of developer
  • Revisit the personas against the year's sign-up data @recurring(yearly)

Developer experience metrics baseline

Teams that run an API without numbers end up arguing from anecdotes about whether the docs are good or onboarding is slow. Measuring a small set of baselines now, such as time to first successful call, weekly active apps, the share of keys that never make a call and error rate by endpoint, turns every later improvement into something you can prove.

First tasks

  • Write one-sentence definitions for time to first call, active app and activated developer
  • Ask engineering for a query that returns the first 2xx response per new key
  • Record the current value and source of each metric in the log
  • Agree with the team which two metrics to move this half

Make it yours.

Install API & Platform Products, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.