In the companion profile I walked the 15Five platform from the outside. This onboarding run is shorter than most in the series — and the reason it’s short is the finding.
I run these onboarding walks as a real first-time developer would — cold, no shortcuts — because the gap between what the docs promise and what a newcomer can actually do is the truest read on developer experience.
There is no signup
The run starts at the login page: username and password, or sign in with Google. I try to create an account and hit “you need to join an existing team.” Hunting for a signup link goes nowhere, because there isn’t one — the only path into 15Five is book a demo. I don’t need a demo, I need an API key, but you can’t have one without the other.
That’s the whole onboarding, honestly: for a first-time developer, the front door is a sales conversation.
The docs themselves are open — and decent
What you can do without an account is read. The Public API documentation is a Redocly-style reference with a downloadable OpenAPI spec (one broken image up in the corner, but otherwise clean). It covers authentication — API keys are managed in 15Five under settings → features → integrations → public API — plus pagination, rate limiting, versioning, and a changelog. The endpoints span user, group, and company management, check-ins, 1-on-1s, High Fives, objectives, and self-reviews.
So the contract is evaluable before you ever talk to sales — that matters, and plenty of demo-gated platforms don’t even give you that.
What the run surfaced
- No self-serve path to a key. The API is a customer feature, not a developer platform. If you’re not already a 15Five customer (or willing to book a demo), the hello world simply isn’t available.
- The docs deserve better than the gate. An open OpenAPI spec, versioning, and a changelog are the bones of a real developer program — a free sandbox tenant or trial key would put a working first call within reach and change the whole first impression.
- Know before you build. If you’re evaluating 15Five for an HR integration, the spec download is your friend: you can model against the contract while procurement does its thing.
Dig into the details
- Provider profile: apis.io/providers/15five
- Open provider data (APIs.json, JSON-LD, GraphQL schema): github.com/api-evangelist/15five
- Watch the profile first: Profiling 15Five — The Public API Behind Performance Management
More provider profile-and-onboard pairs are coming on YouTube @APISearch.