# Torre Public APIs

> Partner-facing APIs for creating people from resumes, tracking referrals, managing openings, and recruiting candidates.

## Authentication

API operations require an issued bearer token with the matching Partners or Recruiting grant. This
file, [health](/health), the generated OpenAPI documents, and the reference UIs are public.

## Recruiting API

The current operation list and request schemas are published in the live OpenAPI document.
Account, subscription, and automatic reload settings retrieval are active. Opening creation, listing, retrieval, update, publication, closure and alignment; stage and screening-question management; applicant listing, retrieval, update and review; candidate search and contact-free person profiles; candidate messaging, outreach requests and polling, balance and current-pricing retrieval, checkout-session creation, Reach activation, reading and stopping, webhook endpoint management, and account-owned webhook event history are active.
Financial usage history belongs to the authenticated account, is newest-first, filterable, and cursor-paginated.
Published job retrieval is active at GET /v1/jobs/{jobId}. Ownership is not required. Hidden pay and recruiting data are excluded.
Skill search is active at GET /v1/skills/search with required nonblank q and optional en/es locale. It returns up to 30 skill IDs and names without changing a profile or charging credits.

- [OpenAPI document](/v1/openapi.json)
- [Guides and workflows](/docs)
- [Create a community-created genome](/docs/workflows/create-community-genome)
- [Scalar API reference](/docs/reference/)
- [Legacy Swagger UI](/v1/docs)

## Partners API

The Partners API exposes three active operations for person creation, referral metrics, and partner
profile access.

- [OpenAPI document](/v1/partners/openapi.json)
- [Scalar API reference](/docs/reference/)
- [Legacy Swagger UI](/v1/partners/docs)