An API is a contract. Once it is published, every change is a customer-facing decision; every breaking change is a migration. We are still learning how customers use the product; pinning the API shape before the V1 surface has run for a full hiring cycle would mean either shipping an API we will regret or shipping one we constantly version away from.

The V2 API ships when the V1 product has run long enough for the data model to settle, when we have the engineering team to maintain it alongside the UI surfaces, and when we have a meaningful sample of customers asking for specific endpoints (rather than asking for "an API" in the abstract). The combination is V2 in mid-2027.

V1 has no public API. Customers who need programmatic access today have two options: the ATS export at finalist-decision time (covered by the integrations directory), which pushes finalist records to Greenhouse, Ashby, Workable, or Lever; or the Picked-managed CSV export, which is available on demand from the admin console.

For customers building custom internal tooling against Picked, the V1 path is to register early-access interest below and start a conversation. We can sometimes accommodate specific use cases with a limited custom integration even before V2; this is by exception, not a sustainable pattern.