Meetings

Create a meeting

Changed on

Create a new meeting, optionally linked to households, contacts, and businesses in the same book. Only past meetings can be logged via the API.

post/v1/meetings

Request

  • Base URL
    https://api.slant.app
  • URL
    https://api.slant.app/v1/meetings
  • Auth
    HTTP bearer

Headers

Idempotency-Keystring

Unique key to ensure idempotent request handling. If a request with the same key was already processed, the original response will be returned.

Request body

book_idstring required

The book ID

titlestring required

Meeting title

start_timestring date-time required

Meeting start time (ISO8601). Must be in the past.

end_timestring date-time

Meeting end time (ISO8601)

notepadstring

Meeting notes (markdown)

contact_idsstring[]

Optional contact IDs in the meeting book to link on creation.

business_idsstring[]

Optional business IDs in the meeting book to link on creation.

household_idsstring[]

Array of household IDs to link to this meeting

Example request

{
  "book_id": "abc123xyz",
  "title": "Client Review",
  "start_time": "2024-01-15T10:00:00Z",
  "end_time": "2024-01-15T11:00:00Z",
  "notepad": "## Agenda\\n\\n- Review portfolio"
}

Response

meeting created

idstring required
titlestring required
start_timestring date-time nullable
end_timestring date-time nullable
duration_secondsinteger
meeting_linkstring nullable
meeting_source'instant' | 'calendar_event' | 'imported' | 'logged' nullable
meeting_typestring
book_idstring required
has_transcriptboolean required
has_recordingsboolean required
created_atstring date-time required
updated_atstring date-time required
quick_summarystring nullable
ai_summarystring nullable

AI-generated summary (markdown). When the firm requires an AI notice, it is appended as a final italic paragraph.

notepadstring nullable
transcriptobject[] nullable
event_participantsobject[] nullable

Changes

    • info

      added the new optional request property

    • info

      added the new optional request property

    • info

      added the media type application/json for the response with the status

    • info

      added the non-success response with the status

    • info

      removed the invalid_json enum value from the response property for the response status

    • info

      response property detail list-of-types was narrowed by removing types array from media type application/json of response 400

    • info

      added the required property to the response with the status

    • info

      added the required property to the response with the status