Design a REST API for Human Resources

You are an expert in this kind of work, and you know the Human Resources sector from the inside.

## Your task
Design a REST API for [FEATURE] at the HR department of a 500-person company. Its users are employees, candidates and hiring managers. Give: resources and endpoints (method, path, purpose), request and response JSON examples, status codes, pagination, authentication, rate limits and versioning. Respect employment law, fairness and confidentiality. Finish with an OpenAPI 3.1 YAML outline.

## About my situation
- How we measure success: time to hire and employee retention

## What matters in Human Resources
- Rules and standards that usually apply: equal-opportunity and anti-discrimination law (Title VII in the US, the Equality Act in the UK, India's labour codes); workplace-harassment law such as India's POSH Act; wage, working-hours and notice-period rules; privacy of employee records; documented, consistent performance processes.
- Common risks to plan for: bad hires; bias complaints; losing top performers; legal disputes; confidentiality leaks.
- Tools commonly used: HRMS (Workday, Darwinbox, Keka); an ATS; LinkedIn and Naukri; Google Forms for surveys.
- Words people in this field use: JD; ATS; onboarding; PIP; appraisal; CTC; notice period; attrition; eNPS.
- Rules differ by country. If I have not said where I work, ask me, and do not present one country's law as if it applied everywhere.

## How to work through it
1. List the resources and how they relate.
2. Design endpoints with methods, paths and purpose.
3. Write request and response examples for each, including errors.
4. Decide pagination, authentication, rate limits and versioning, and explain each choice.
5. Write the OpenAPI outline.

## What to deliver
- Endpoint table
- JSON request and response examples
- Error format and status codes
- Auth, pagination and rate limit rules
- OpenAPI 3.1 YAML outline

## Rules
- Make every point specific to my situation and my industry; replace generic advice with detail that fits.
- Use plain language, short sentences, and tables where they make the answer easier to scan.
- Use only the facts I give you. Do not invent figures, laws, sources or quotes. Mark anything you had to assume with "Assumption:".
- If something important is missing, ask me up to 3 short questions before you start.

## Before you answer
Check your draft against this list and fix anything that fails:
- The code works as written: no invented libraries, functions or APIs, and versions are named where they matter.
- It is written for the HR department of a 500-person company; nothing in it would read the same for any other business.
- Nothing in it breaks employment law, fairness and confidentiality.
- Every item under "What to deliver" is included.