Downloads
All artifacts are versioned in lockstep with this documentation and regenerated automatically whenever the API reference changes.OpenAPI 3.1 Specification (YAML)
The complete machine-readable API contract — 32 REST operations and 14 webhook events.
Canonical source of truth.
OpenAPI 3.1 Specification (JSON)
The same specification as JSON, for tooling that prefers it.
Postman Collection
Ready-to-import collection with pre-filled example requests for every endpoint, organized by
resource.
Postman Environments
Production environment
· Sandbox environment
— base URL and API-key variables for each environment.
Swagger / OpenAPI documentation
The specification is written in OpenAPI 3.1.0 and covers the entire documented Partner API:- 32 REST operations across 23 paths — Jobs, Candidates, Job Candidates, Pipelines, Custom Fields, and Custom Field Values.
- 14 webhook events modeled under the OpenAPI
webhookssection, including envelope, per-event payload schemas, and delivery headers. - Full request/response schemas, field constraints, enumerations, and error models, with examples for every operation.
Explore in the API Playground
Every operation in the specification is browsable and executable in the interactive API
Playground tab of this site — try requests against production or sandbox with your own API key.
Postman collection
1
Import the collection
In Postman: Import → drop in
taptalent-partner-api.postman_collection.json (or paste its
URL from the download card above).2
Import both environments
Import the production and sandbox environment files the same way.
3
Add your API key
Open the environment you want to use and paste your key into the
apiKey variable
(sk_live_… for production, sk_test_… for sandbox). Keys are generated in the
dashboard under Account Settings → Developers.4
Select the environment and send
Pick the environment in Postman’s environment selector. Every request inherits bearer
authentication from the collection and resolves
{{baseUrl}} from the environment.Delete Pipeline Stage sends a JSON request body with a DELETE request (required by the API).
Postman supports this natively; some other HTTP clients strip DELETE bodies — check yours if the
call fails. Webhook payloads are not part of the collection (they are inbound deliveries, not
callable requests); see the OpenAPI specification’s webhooks section or the
Webhooks documentation.API specifications
JSON data structure
Success responses use one of three envelope styles, by resource family — each endpoint’s exact shape is defined in the OpenAPI specification:
Most errors use the canonical error envelope:
{ "message": "Invalid API key" })
— see Authentication and the shared 401 response in the
specification.
Supported communication methods
All communication with the API is JSON over HTTPS. No SOAP, SFTP, or file-drop mechanisms are used or required.
For managed engagements, TapTalent can additionally deliver data directly into your HRIS—see HRIS Delivery Options.
Related pages
- API Reference — hand-written endpoint documentation with examples
- Webhooks — setup, verification, and the full event catalogue
- Authentication — obtaining and using API keys
- Open API Capabilities — what the platform offers for building integrations
.png?fit=max&auto=format&n=lKy84_BssSCy2hcz&q=85&s=ac7c949427cc2893306f6036415f087e)