Create a meeting
Changed onLogs, imports or schedules a general meeting, through the same service the Atlas app uses. Returns the created meeting in the same shape as GET /api/v1/meetings/{meetingId}.
Logging or importing a past meeting: send skipCalendarEvent: true with past startAt / endAt. There is no separate backdating flag: a meeting whose endAt is already in the past is stored as completed; one that ends in the future is scheduled.
Scheduling: send skipCalendarEvent: false and senderEmail; the calendar event is created from that user’s connected calendar. If that calendar cannot be reached the meeting is still created, without a calendar event — except when its authorisation has expired, which returns 401 and creates nothing.
The user that owns the API key (or senderEmail, when given) is the organizer and is always added as an attendee; that user needs a connected mailbox in Atlas. Only general meetings can be created here — candidate interviews are not supported.
Request
- Base URLhttps://api.recruitwithatlas.com
- AuthHTTP bearer
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Request body
Example request
{
"name": "Intro call with Jane Doe",
"startAt": "2026-06-01T09:00:00Z",
"endAt": "2026-06-01T09:30:00Z",
"timeZone": "Europe/London",
"communicationMethod": "video_call",
"attendees": [
{
"email": "jane.doe@client.com",
"isUser": false
}
],
"skipCalendarEvent": true,
"description": "Imported from our call recorder",
"peopleNotes": "Discussed the senior engineer role; follow up next week."
}Response
Meeting created
Changes
- warning
added the new
undefinedenum value to the///response property for the response status - warning
added the new
undefinedenum value to the/response property for the response status - warning
added the new
undefinedenum value to the/response property for the response status
- warning
- info
endpoint added
- info