Build with Tabbio

Let people bring their Tabbio identity and their CV into your product, and post jobs and read applicants from your own systems. Two APIs, one set of credentials, 23 endpoints.

Apps, client credentials, API keys, usage and limits live on the Tabbio Developer Platform. Sign in with your Tabbio account or create a developer login there.

Two ways in

Pick the one that matches who you are building for. Nothing stops you from using both: they share an app record and a developer account.

Sign in with Tabbio

For products where a person signs in. They approve once on a Tabbio consent screen, choose which CV to share, and your app reads it from then on.

  • OAuth 2.0 authorization code with PKCE
  • Identity, verified email, and the CV as JSON or PDF
  • The CV follows the user's edits, so it never goes stale
  • The user can change or end the sharing at any time

Partner API

For platforms acting on behalf of employers. Create company pages, post and publish jobs, and read the people who applied.

  • Server to server API keys, no user interaction
  • Idempotent company creates keyed on your own identifiers
  • Jobs land on the Tabbio job board when you publish them
  • Candidates arrive with a CV snapshot and their answers

Start here

API reference

Generated from the API source, so it cannot describe an endpoint that does not exist. Base URL https://server.tabbio.com.