[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup) # CharlieHR API > Every CharlieHR endpoint on Cotlet: inputs, JSON Schema, cURL, Python and Node.js examples and an example response for each call. Source: https://cotlet.dev/docs/api/charliehr Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md) 12 endpoints for CharlieHR, each at its own method and path, called with your API key. Open an endpoint for its inputs, examples and response. - Base URL: `https://cotlet.dev/api/v1/charliehr` - Connects with: Your own CharlieHR account (Super Admin or Admin for company-wide work, Line Manager or Team Lead for your own reports) - Integration page: https://cotlet.dev/integrations/charliehr-api-mcp-server ## Read Return data and change nothing in the account. | Endpoint | Description | |---|---| | [`GET /team-members`](https://cotlet.dev/docs/api/charliehr/list_team_members.md) | People in your CharlieHR account with office, team, line manager and start date. | | [`GET /team-member`](https://cotlet.dev/docs/api/charliehr/get_team_member.md) | One profile: office, team, line manager, start date, role and working week. | | [`GET /time-off-requests`](https://cotlet.dev/docs/api/charliehr/list_time_off_requests.md) | Time off requests with person, type, dates, days and status. | | [`GET /members/{member_id}/time-off-allowance`](https://cotlet.dev/docs/api/charliehr/get_time_off_allowance.md) | Allowance, days used, pending and remaining for one person and leave year, with adjustments. | | [`GET /whos-working`](https://cotlet.dev/docs/api/charliehr/get_whos_working.md) | Who is working where and who is off, for one day. | ## Write Change the account. Calls marked Confirm wait for the user to approve them. | Endpoint | Description | |---|---| | [`POST /requests/{request_id}/time-off-request/approve`](https://cotlet.dev/docs/api/charliehr/approve_time_off_request.md) (Confirm) | Approve one pending time off request, with an optional message to the person. | | [`POST /requests/{request_id}/time-off-request/deny`](https://cotlet.dev/docs/api/charliehr/deny_time_off_request.md) (Confirm) | Deny one pending time off request, with a message to the person. | | [`POST /members/{member_id}/time-offs`](https://cotlet.dev/docs/api/charliehr/book_time_off.md) (Confirm) | Book time off on behalf of a team member; it is approved at once. | | [`POST /members/{member_id}/sick-days`](https://cotlet.dev/docs/api/charliehr/record_sick_day.md) (Confirm) | Record sick leave for a team member; it is approved at once. | | [`POST /members/{member_id}/time-off-allowance/adjust`](https://cotlet.dev/docs/api/charliehr/adjust_time_off_allowance.md) (Confirm) | Add or remove days on one person's allowance, with a type, an expiry date and a note. | | [`POST /bookings/{booking_id}/time-off-booking/cancel`](https://cotlet.dev/docs/api/charliehr/cancel_time_off_booking.md) (Confirm) | Cancel one upcoming or past time off booking. | | [`POST /members/{member_id}/team-member/offboard`](https://cotlet.dev/docs/api/charliehr/offboard_team_member.md) (Confirm) | Offboard a person with a leaving date and a reason; the profile is archived. | --- Give your AI agents your signed-in browser. **Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) **Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet) **Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) **Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md) **Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors) **Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet) Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners. ## For AI agents: sign your user up Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed. 1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests 2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them. 3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests. One call creates the account and sends the access request; we email the user when access is granted.