# Lovelio API reference

Recruitment automation API. Create jobs, manage candidates, run ad-hoc actions, integrate with your tools.

Generated from the OpenAPI 3.1 document at https://lovelio.ai/api/v1/openapi.json.
API version 7.2.0. 157 paths, 234 operations.

This is the plain-markdown copy of the reference rendered at https://lovelio.ai/docs/api.

## Fetch less than all of this

| URL | What you get |
| --- | --- |
| `https://lovelio.ai/docs/api.md` | Everything: this header plus every operation in full. |
| `https://lovelio.ai/docs/api.md?index=1` | This header plus the endpoint index. No per-operation detail. |
| `https://lovelio.ai/docs/api.md?tag=Jobs` | This header plus one section in full. Comma-separate for several: `?tag=Jobs,Applications`. |
| `https://lovelio.ai/api/v1/openapi.json` | The machine-readable source this file is generated from. |

Tags: System, Accounts, Jobs, Job Ads, Candidates, Candidate Imports, Applications, Interviews, Submissions, Placements, Quotas, Marketplace, Webhooks, Batch, Activities, Documents, Tasks, Outreach, Talent Pools, Review Queue, Forms, Referees, Integrations, Chat Integrations, Analytics, Calendar, Scheduled Emails, Workflow Rules, Email Templates, Stages, Distribution, Clients, Specs, Search, Business Development.

## Base URL

Docs live on lovelio.ai. The API does not. Every workspace belongs to a region and an API key only works on its own region's host. Calling `lovelio.ai/api/v1/...` returns a JSON error naming all three hosts rather than data.

| Region | Base URL |
| --- | --- |
| Production (US (N. California)) | `https://us.lovelio.ai/api/v1` |
| Production (EU (London)) | `https://eu.lovelio.ai/api/v1` |
| Production (ANZ (Sydney)) | `https://anz.lovelio.ai/api/v1` |

A workspace's exact host is shown in Settings > API keys.

## Authentication

```http
Authorization: Bearer sk_live_...
```

API key, sent as Authorization: Bearer <key>. Three key types: sk_live_ (production), sk_test_ (development - same workspace, same data, marked as a test key; use a separate workspace if you need isolated test data), and sk_trial_ (issued at signup, expires 7 days later - swap to a live key from Settings > API keys). Keys are server-generated, shown once at creation, and scoped per permission (or admin for everything). Lovelio Connect apps authenticate with the OAuth access token from the connect flow instead (Authorization: Bearer lc_at_...) - it carries exactly the scopes the agency approved, enforced on every request. Money is gated at FIELD level, not route level: the three scopes placements:financials:read, clients:financials:read and marketplace:financials:read unlock salary, fee, contract rates, expected GP, commission percents, the client fee schedule and split-fee deal amounts. Without them those fields return null and everything else on the record still comes through - a read never 403s for want of a money scope. admin satisfies all three. Requesting any of them puts a Connect app in the elevated review tier. See /docs/agents/build-an-integration.

## Pagination and shared parameters

Every list endpoint takes these. Cursor-based: read `meta.next_cursor` from a response and pass it back as `after`.

| Name | In | Type | Description |
| --- | --- | --- | --- |
| `limit` | query | integer, 1-100, default 25 | Rows per page. Clamped to the 1-100 range rather than rejected, so asking for 500 returns 100 - read meta.has_more and page with the cursor. Unparseable values fall back to 25. |
| `after` | query | string | Cursor for forward pagination |
| `before` | query | string | Cursor for backward pagination |
| `created_after` | query | string (date-time) | Only rows created at or after this ISO 8601 date or datetime (inclusive). Malformed values are a 422, never silently ignored. |
| `created_before` | query | string (date-time) | Only rows created at or before this ISO 8601 date or datetime (inclusive). Malformed values are a 422, never silently ignored. |

## Rate limit headers

| Header | Type | Description |
| --- | --- | --- |
| `X-RateLimit-Limit` | integer | Requests allowed per minute |
| `X-RateLimit-Remaining` | integer | Requests remaining in window |
| `X-RateLimit-Reset` | integer | Unix timestamp when window resets |

## Guides

- https://lovelio.ai/docs/agents - what an agent can drive end to end
- https://lovelio.ai/docs/agents/top-10-tasks - runnable examples for the ten most common calls
- https://lovelio.ai/docs/agents/build-an-integration - sandbox agency, test API key, live webhook testing
- https://lovelio.ai/docs/agents/error-handling - error envelope, request IDs, retries, idempotency keys
- https://lovelio.ai/docs/agents/webhooks - subscribing and verifying HMAC signatures
- https://lovelio.ai/docs/agents/sdks - single-file TypeScript and Python clients
- https://lovelio.ai/docs/api/changelog - every version, including breaking changes
- https://lovelio.ai/llms-full.txt - all of the above inlined in one fetch

## Endpoint index

Filtered to: Calendar.

### Calendar

Shared calendar events for interviews, phone screens, reminders, deadlines, and meetings

- `GET /calendar-events` - List calendar events
- `POST /calendar-events` - Create calendar event
- `GET /calendar-events/{id}` - Get calendar event
- `PATCH /calendar-events/{id}` - Update calendar event
- `DELETE /calendar-events/{id}` - Delete calendar event

---

## Calendar

Shared calendar events for interviews, phone screens, reminders, deadlines, and meetings

### GET /calendar-events

**List calendar events**

Returns calendar events for the company (shared interviews, phone screens, reminders, deadlines, meetings). Filter by time window with start and end, by event_type, or by linked record IDs. Calendar events are automatically created when an interview is scheduled via POST /v1/interviews.

Operation ID: `listCalendarEvents`

**Query parameters**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `start` | string (date-time) | no | Only return events starting at or after this ISO-8601 timestamp. |
| `end` | string (date-time) | no | Only return events starting strictly before this ISO-8601 timestamp. |
| `event_type` | string (`interview`, `phone_screen`, `reminder`, `deadline`, `meeting`) | no |  |
| `application_id` | string | no |  |
| `candidate_id` | string | no |  |
| `job_id` | string | no |  |
| `limit` | integer, max 100, default 25 | no |  |
| `cursor` | string | no | starts_at cursor for forward pagination. |

**Responses**

| Code | Description | Body |
| --- | --- | --- |
| `200` | List of calendar events | { success, data: array of CalendarEvent, meta } |

### POST /calendar-events

**Create calendar event**

Create a calendar event. For interview events you normally use POST /v1/interviews, which creates both an interview record and a matching calendar event; use this endpoint for standalone entries like reminders, deadlines, and meetings.

Operation ID: `createCalendarEvent`

**Request body** (`application/json`)

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `title` | string | yes |  |
| `event_type` | string (`interview`, `phone_screen`, `reminder`, `deadline`, `meeting`) | yes |  |
| `starts_at` | string (date-time) | yes |  |
| `ends_at` | string (date-time) \| null | no |  |
| `all_day` | boolean | no |  |
| `notes` | string | no |  |
| `application_id` | string | no |  |
| `job_id` | string | no |  |
| `candidate_id` | string | no |  |
| `assigned_to` | string | no | User ID the event is assigned to. |

**Responses**

| Code | Description | Body |
| --- | --- | --- |
| `201` | Calendar event created | { success, data: CalendarEvent } |
| `422` | Validation error |  |

### GET /calendar-events/{id}

**Get calendar event**

Operation ID: `getCalendarEvent`

**Path parameters**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | string | yes | Calendar event external ID (cal_ prefix) |

**Responses**

| Code | Description | Body |
| --- | --- | --- |
| `200` | Calendar event | { success, data: CalendarEvent } |
| `404` | Not found |  |

### PATCH /calendar-events/{id}

**Update calendar event**

Operation ID: `updateCalendarEvent`

**Path parameters**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | string | yes |  |

**Request body** (`application/json`)

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `title` | string | no |  |
| `event_type` | string (`interview`, `phone_screen`, `reminder`, `deadline`, `meeting`) | no |  |
| `starts_at` | string (date-time) | no |  |
| `ends_at` | string (date-time) \| null | no |  |
| `all_day` | boolean | no |  |
| `notes` | string \| null | no |  |
| `assigned_to` | string \| null | no |  |

**Responses**

| Code | Description | Body |
| --- | --- | --- |
| `200` | Updated calendar event | { success, data: CalendarEvent } |
| `404` | Not found |  |

### DELETE /calendar-events/{id}

**Delete calendar event**

Operation ID: `deleteCalendarEvent`

**Path parameters**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | string | yes |  |

**Responses**

| Code | Description | Body |
| --- | --- | --- |
| `200` | Deleted |  |
| `404` | Not found |  |

## Schemas

Objects referenced by the operations above.

### CalendarEvent

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | string | no |  |
| `title` | string | no |  |
| `notes` | string \| null | no |  |
| `event_type` | string (`interview`, `phone_screen`, `reminder`, `deadline`, `meeting`) | no |  |
| `starts_at` | string (date-time) | no |  |
| `ends_at` | string (date-time) \| null | no |  |
| `all_day` | boolean | no |  |
| `application_id` | string \| null | no |  |
| `job_id` | string \| null | no |  |
| `candidate_id` | string \| null | no |  |
| `assigned_to` | string \| null | no | User ID the event is assigned to. |
| `created_by` | string \| null | no |  |
| `created_at` | string (date-time) | no |  |
| `updated_at` | string (date-time) | no |  |