Meetings
Base URL https://api.leadx.in/api/key/protected. Every request needs an apikey header — see Authentication.
3 endpoints.
GET /meeting
Get all meetings.
Auth apikey
:::note Used by the web app
components/ScheduleMeetingModal.jsx, pages/AddMeeting.jsx, pages/Meeting.jsx
:::
Query parameters — the standard list contract: p, n, sortBy, sortOrder, searchBy, searchValue, filters, advancedFilters, ids, nids. See Pagination and Filtering.
Response — data is an array of ScheduleMeeting objects, alongside the pagination fields described in Response format. updatedBy, createdBy, contact, host are populated, so they arrive as nested objects rather than ids.
POST /meeting
Create meeting.
Auth apikey · Success 200
:::note Used by the web app
components/ScheduleMeetingModal.jsx, pages/AddMeeting.jsx, pages/Meeting.jsx
:::
Request body
| Field | Default |
|---|---|
title | — |
description | — |
provider | offline |
app | — |
location | — |
mapLink | — |
meetingLink | — |
passcode | — |
timezone | — |
startTime | — |
endTime | — |
duration | — |
host | — |
contact | — |
lead | — |
attendees | — |
reminders | — |
recurrence | — |
Required: title, startTime.
Response — data is one ScheduleMeeting object.
GET /meeting/:id
Get meeting.
Auth apikey
:::note Used by the web app
pages/AddMeeting.jsx
:::
Path parameters
| Name | |
|---|---|
id | Required |
Response — data is one ScheduleMeeting object. lead, contact, host, app are populated, so they arrive as nested objects rather than ids.