> ## Documentation Index > Fetch the complete documentation index at: https://developer.jobmojito.com/llms.txt > Use this file to discover all available pages before exploring further. # Create, change or delete a meeting slot > One bookable slot of a meeting step, as the admin calendar writes it. create needs step_id and start_at; update and delete need slot_id; fields left out keep their value. A slot is offered in both meeting modes: in availability mode candidates see it next to the times taken from the interviewers' calendars. E-mails: delete cancels every booking on the slot and e-mails each booked candidate a cancellation (and the interviewers); an update of start_at, duration_minutes, location or meeting_url e-mails each booked candidate the booking again with the new details and moves the calendar events; other changes and create send nothing. Run dry_run first: it lists exactly the candidates who would be e-mailed (affected_bookings). Owners and recruiters on the position's access list; hiring managers read only. ## OpenAPI ````yaml https://cool.jobmojito.com/functions/v1/openapi post /merchant-meeting-slot-manage openapi: 3.1.0 info: title: JobMojito API version: 1.0.0 description: >- Public API for JobMojito, served by Supabase Edge Functions. Authenticate with a Supabase JWT access token via the Authorization header. servers: - url: https://cool.jobmojito.com/functions/v1 description: Production security: [] tags: - name: Interviews description: >- Create, configure and manage interview / coaching / assessment definitions. - name: Positions description: >- A position's hiring process: its steps and their settings, meeting slots, and copies of positions and interviews. - name: Coaching catalogue description: >- Directories (pages) of the coaching portal catalogue that group coaching sessions and carry custom content pages. - name: Results description: >- Interview results, transcripts, reports, re-attempt requests and analytics. - name: Reports description: >- Custom reports: read the catalogue of datasets, build a report definition, check it, save it and run it. - name: Candidates description: List and manage candidates. - name: Tasks description: >- Follow-up tasks for the hiring team, about a candidate, an application or a position. - name: Document requests description: >- Ask candidates for documents (certificates, IDs, references), follow them up and mark them reviewed. - name: Knowledge base description: Upload documents used to generate knowledge-base interviews. - name: Resume & Form verification description: Pre-screen candidates from resumes and forms. - name: Admin description: >- Account administration — invite team/coaching users, manage sub-merchants and avatar templates. - name: Feedback description: >- Send feature requests to the product team and report technical issues to support. - name: Integrations description: >- Ready-made connectors and how their fields map to JobMojito. A company sees the same tables under Integrations > Catalogue > Field mapping. ### ATS connector (Kombo) The applicant tracking system is connected through Kombo's unified ATS API. JobMojito keeps a copy of the ATS jobs, applications and candidates, links each position to one ATS job, invites applicants who reach the trigger stage, and writes the outcome back. Links, notes and attachments are written only when the company switched them on (merchant.kombo_selected_result_actions); job fields are not copied into the position. | JobMojito field | Direction | External field | Notes | | --- | --- | --- | --- | | `merchant.kombo_integration_id, merchant.kombo_integration_tool` | Into JobMojito | `integration-created / integration-deleted webhook: data.id, data.tool` | Set when the ATS connection is created and cleared when it is deleted. | | `kombo_jobs.id, kombo_jobs.name` | Into JobMojito | `GET /ats/jobs: id, name (fallback title)` | Copied on every full or incremental sync of the jobs. | | `kombo_jobs.status` | Into JobMojito | `jobs.status, jobs.remote_deleted_at` | DRAFT becomes draft, CLOSED or ARCHIVED becomes archived, deleted in the ATS becomes deleted. | | `kombo_jobs.data` | Into JobMojito | `jobs.* (whole job object)` | Kept as received; the position's own fields are not overwritten from it. | | `position_def_set.kombo_parameters.kombo_job_id, interview_def_set.kombo_parameters.kombo_job_id` | Into JobMojito | `jobs.id` | Links a position or interview to one ATS job, chosen by the recruiter. | | `position_def_set.status, interview_def_set.status` | Into JobMojito | `jobs.status (closed, archived, deleted, reopened)` | Closing the job in the ATS archives the linked positions and interviews; reopening it restores their previous status. | | `kombo_parameters.kombo_stage_id` | Into JobMojito | `jobs.stages[].id matched against applications.current_stage_id` | An application entering this stage triggers the invitation or the pre-screening; applicants already in it are invited when the position is published. | | `ATS pipeline report (stage names and order)` | Into JobMojito | `jobs.stages[].id, name, index` | Read for the ATS pipeline report only. | | `kombo_applications.id, kombo_job_id, kombo_candidate_id, data` | Into JobMojito | `GET /ats/applications: id, job_id, candidate_id` | Copied on application sync; applications of closed or archived jobs are not imported. | | `kombo_applications.kombo_stage_id` | Into JobMojito | `applications.current_stage_id` | A stage change re-runs the invitation check for that application. | | `kombo_applications.status` | Into JobMojito | `applications.outcome (HIRED, DECLINED), remote_deleted_at` | Hired, declined or deleted applications are archived and receive no further invitations. | | `position_result.outcome, interview_result.outcome` | Into JobMojito | `applications.outcome` | Set to hired or declined when the ATS marks the linked application, while the outcome is still pending. | | `position_result.status, interview_result.status` | Into JobMojito | `applications.remote_deleted_at` | An application deleted in the ATS archives the linked application in JobMojito if nobody has decided yet. | | `kombo_candidates.id, data, status` | Into JobMojito | `GET /ats/candidates: candidates.*, remote_deleted_at` | Copied on candidate sync; a candidate deleted in the ATS is archived. | | `profile_interview.email, profile_interview.email_auth` | Into JobMojito | `candidates.email_addresses[0].email_address` | Finds or creates the candidate when the application reaches the trigger stage. | | `profile_interview.name` | Into JobMojito | `candidates.first_name + last_name` | Set when the candidate is created from the ATS. | | `profile_interview.phone_number` | Into JobMojito | `candidates.phone_numbers[0].phone_number` | Set when the candidate is created from the ATS. | | `kombo_candidates.profile_interview_id` | Into JobMojito | `candidates.id (matched by e-mail)` | Links the ATS candidate to the JobMojito candidate on invitation or pre-screening. | | `interview_file (type resume)` | Into JobMojito | `GET /ats/applications/{id}/attachments, then /ats/candidates/{id}/attachments: type CV (fallback OTHER)` | The CV from the ATS is imported when the candidate is invited or pre-screened. | | `interview_result_pre_screening (AI pre-screening input)` | Into JobMojito | `applications.screening_question_answers[] (question.title, answer)` | The candidate's answers to the ATS screening questions are part of the AI pre-screening. | | `interview_result_pre_screening.nationality, residency` | Into JobMojito | `candidates.location.country (fallback address.country)` | Taken from the ATS candidate during pre-screening. | | `kombo_applications.interview_result_id, interview_result_pre_screening_id` | Into JobMojito | `applications.id` | Set when the candidate's result is linked back to the ATS application. | | `kombo_tags, kombo_rejection_reasons, kombo_users, kombo_offers, kombo_interviews` | Into JobMojito | `GET /ats/tags, /ats/rejection-reasons, /ats/users, /ats/offers, /ats/interviews` | Kept in sync so recruiters can pick tags and rejection reasons; the others are stored only. | | `kombo_parameters.kombo_selected_stage_id (step: config.kombo.accept_stage_id)` | From JobMojito | `PUT /ats/applications/{id}/stage` | Moves the application when the recruiter selects the candidate; the position's stage is used on the last step. | | `kombo_parameters.kombo_sync_all_results_stage_id` | From JobMojito | `PUT /ats/applications/{id}/stage` | Every processed result is moved to this stage, only when sync all results is on. | | `kombo_parameters.kombo_rejected_reason_human_id, kombo_rejected_reason_ai_id (step: config.kombo.reject_reason_id)` | From JobMojito | `POST /ats/applications/{id}/reject { rejection_reason_id, note }` | Rejects the application when the recruiter rejects; nothing is sent when no reason is configured. | | `Rejection note (result link, score, AI feedback)` | From JobMojito | `reject.note` | The note sent with the rejection. | | `interview_result result link + interview_result.score` | From JobMojito | `POST /ats/applications/{id}/result-links { label, url, details.attributes }` | Sent when result links are switched on: a signed link to the result with its score. | | `interview_result note (result link + score)` | From JobMojito | `POST /ats/applications/{id}/notes` | Sent when notes are switched on and the recruiter has decided, or sync all results is on. | | `interview_result.pdf_export_url (interview PDF report)` | From JobMojito | `POST /ats/applications/{id}/attachments (type OTHER)` | Sent when attachments are switched on; the PDF is generated first if missing. | | `interview_result_pre_screening score, recommendation and analysis` | From JobMojito | `POST /ats/applications/{id}/notes` | Sent after every AI pre-screening and again when the recruiter decides on it. | | `Pre-screening PDF report` | From JobMojito | `POST /ats/applications/{id}/attachments (type OTHER)` | Uploaded when attachments are switched on. | | `interview_result.coach_status (progress note)` | From JobMojito | `POST /ats/applications/{id}/notes` | A note when the interview fails or the answers are collected, only when sync all results is on. | | `position_result_step decision and recruiter notes (meeting step)` | From JobMojito | `POST notes, PUT stage, POST reject` | Sends ': passed / failed' with the recruiter's notes, then moves or rejects. | | `human_interview_request reason and outcome` | From JobMojito | `POST notes, PUT stage, POST reject` | Notes the request, moves on pass and rejects on fail or decline. | | `merchant.kombo_tag_assignment.result_weak / result_moderate / result_strong / result_exceptional` | From JobMojito | `POST /ats/candidates/{id}/tags` | Score tags on result sync: under 4 weak, under 7 moderate, under 8.5 strong, up to 10 exceptional. | | `merchant.kombo_tag_assignment.interview_selected / interview_rejected` | From JobMojito | `POST /ats/candidates/{id}/tags` | Decision tags on a recruiter decision; the selected tag only on the last step. | | `merchant.kombo_sync (manual sync)` | From JobMojito | `POST /force-sync` | Asks Kombo to sync the ATS again when the recruiter presses sync. | ### Webhooks JobMojito POSTs the same JSON payload for the events interview_result (the result is final and scored, sent again when a watched field changes), interview_collected (the candidate finished, before scoring) and interview_failed (failed, abandoned or no speech). Configure the URL, events and authentication headers per environment under Integrations > Custom integration; failed deliveries are retried and kept in the delivery history. | JobMojito field | Direction | External field | Notes | | --- | --- | --- | --- | | `interview_result.id` | From JobMojito | `id` | The result the event is about. | | `interview_result.question_set_id (interview_def_set.id)` | From JobMojito | `interview_id` | The interview definition. | | `interview_result.question_set_id (interview_def_set.id)` | From JobMojito | `question_set_id` | Same value as interview_id. | | `interview_result.status` | From JobMojito | `status` | active for interview_result, draft for the other two events. | | `interview_result.coach_status` | From JobMojito | `interview_status` | completed, failed, abandoned and so on. | | `interview_result.processing_status` | From JobMojito | `processing_status` | AI processing state. | | `interview_result.profile_interview_id` | From JobMojito | `profile_interview_id` | The candidate. | | `interview_result.profile_id` | From JobMojito | `profile_id` | The candidate's portal account, when there is one. | | `profile_interview.external_id` | From JobMojito | `candidate_external_id` | Your id for the candidate; present when a candidate is linked. | | `profile_interview.name` | From JobMojito | `candidate_name` | Present when a candidate is linked. | | `profile_interview.email` | From JobMojito | `candidate_email` | Present when a candidate is linked. | | `profile_interview.phone_number` | From JobMojito | `candidate_phone_number` | Present when a candidate is linked. | | `interview_result.recruiter_go_next_round` | From JobMojito | `recruiter_go_next_round` | The recruiter's decision; usually empty in interview_collected and interview_failed. | | `interview_result.ai_analysis` | From JobMojito | `ai_analysis` | Candidate-facing analysis, filled in interview_result. | | `interview_result.ai_analysis_recruiter` | From JobMojito | `ai_analysis_recruiter` | Recruiter-facing analysis, filled in interview_result. | | `interview_result.ai_analysis_other` | From JobMojito | `ai_analysis_other` | Session analyses by name, for example strengths_concerns. | | `interview_result.ai_analysis_other.strengths_concerns.strengths` | From JobMojito | `ai_analysis_recruiter_why_hire` | Deprecated copy kept for existing integrations. | | `interview_result.ai_analysis_other.strengths_concerns.concerns` | From JobMojito | `ai_analysis_recruiter_why_not_hire` | Deprecated copy kept for existing integrations. | | `interview_result.score_interview_ai` | From JobMojito | `ai_analysis_recruiter_score` | Recruiter-facing AI score, filled in interview_result. | | `interview_result.score` | From JobMojito | `score` | Overall score, filled in interview_result. | | `interview_result.pdf_export_url` | From JobMojito | `pdf_export_url` | When a PDF report is configured, interview_result waits until the PDF exists. | | `Changed fields of the result` | From JobMojito | `reason` | Which watched fields changed; 'manual re-trigger of ...' on a resend from the delivery history. | paths: /merchant-meeting-slot-manage: post: tags: - Positions summary: Create, change or delete a meeting slot description: >- One bookable slot of a meeting step, as the admin calendar writes it. create needs step_id and start_at; update and delete need slot_id; fields left out keep their value. A slot is offered in both meeting modes: in availability mode candidates see it next to the times taken from the interviewers' calendars. E-mails: delete cancels every booking on the slot and e-mails each booked candidate a cancellation (and the interviewers); an update of start_at, duration_minutes, location or meeting_url e-mails each booked candidate the booking again with the new details and moves the calendar events; other changes and create send nothing. Run dry_run first: it lists exactly the candidates who would be e-mailed (affected_bookings). Owners and recruiters on the position's access list; hiring managers read only. requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/MeetingSlotManageRequest' responses: '200': description: >- The slot after the call (or as it would be, in a dry run) and the bookings it reaches. content: application/json: schema: $ref: '#/components/schemas/MeetingSlotManageResult' '401': description: Missing, expired or invalid access token. content: application/json: schema: $ref: '#/components/schemas/Error' '403': description: >- Not company staff, a hiring manager (read only), another company, or the company feature meeting_panels is off for a panel (the message names it). content: application/json: schema: $ref: '#/components/schemas/Error' '404': description: No such slot or step, or its position is not visible to you. content: application/json: schema: $ref: '#/components/schemas/Error' '422': description: >- Validation error naming the field: missing slot_id / step_id / start_at, a start in the past, a step that is not a meeting step, capacity below the bookings, an interviewer or panel member not of this company, a panel on a free-time slot or without a lead. content: application/json: schema: $ref: '#/components/schemas/Error' '500': description: Server error. content: application/json: schema: $ref: '#/components/schemas/Error' security: - bearerAuth: [] components: schemas: MeetingSlotManageRequest: type: object properties: action: type: string enum: - create - update - delete description: >- create a slot on a meeting step, update one, or delete one (its booked candidates are cancelled and e-mailed). slot_id: type: string format: uuid description: 'update / delete: the slot (position_meeting_slot.id).' step_id: type: string format: uuid description: 'create: the meeting step (position_def_step.id, type meeting).' start_at: type: string format: date-time description: >- create (required) / update: when the meeting starts. Not in the past. duration_minutes: type: integer minimum: 5 maximum: 1440 description: >- Length, 5 to 1440 minutes. Default on create: the step's meeting.duration_minutes, else 30. capacity: type: integer minimum: 1 maximum: 500 description: >- How many candidates can book it, 1 to 500 (default 1); not below the number already booked. location: type: string nullable: true maxLength: 500 description: Address or room; null = the step's location. meeting_url: type: string nullable: true maxLength: 2000 pattern: ^https?:\/\/\S+$ description: Video link; null = the step's link. interviewer_profile_id: type: string nullable: true format: uuid description: >- Who holds the meeting (profile.id of a user of the company); null = the position's recruiter. note: type: string nullable: true maxLength: 2000 description: Internal note, not shown to candidates. agenda: type: string nullable: true maxLength: 4000 description: Agenda for the panel (company feature meeting_panels). panel_profile_ids: type: array nullable: true items: type: string format: uuid maxItems: 8 description: >- Needs the meeting_panels feature; hand-made slots only: up to 8 users (profile.id) who attend besides the interviewer, who leads. Empty or null removes the panel; left out keeps it. dry_run: type: boolean default: false description: >- true: validate and answer the slot as it would be and the booked candidates who would be e-mailed, without writing anything. required: - action additionalProperties: false MeetingSlotManageResult: type: object properties: action: type: string enum: - create - update - delete description: The action done (or checked). dry_run: type: boolean description: true when nothing was written. slot: $ref: '#/components/schemas/MeetingSlot' affected_bookings: type: array items: type: object properties: booking_id: type: string format: uuid description: The booking (position_meeting_booking.id). candidate_id: type: string nullable: true format: uuid description: The candidate (profile_interview.id). candidate_name: type: string nullable: true description: The candidate's name. effect: type: string enum: - cancelled - updated description: >- cancelled: the booking is cancelled, the candidate gets a cancellation e-mail and can book again; updated: the candidate gets the booking e-mail again with the new time, length, place or link. required: - booking_id - candidate_id - candidate_name - effect description: >- Booked candidates this call e-mails (or would, in a dry run). Empty when nobody is told. warnings: type: array items: type: string description: >- Things the user should know (e.g. booked candidates are not told about a capacity change). required: - action - dry_run - slot - affected_bookings - warnings Error: type: object properties: error: type: string example: Field is required. name: type: string example: interview_result_id required: - error MeetingSlot: type: object properties: id: type: string nullable: true format: uuid description: The slot (position_meeting_slot.id); null for a create in a dry run. step_id: type: string format: uuid description: The meeting step (position_def_step.id). position_id: type: string format: uuid description: The position (position_def_set.id). start_at: type: string description: Start (ISO 8601). duration_minutes: type: integer description: Length in minutes. capacity: type: integer description: How many candidates can book it. location: type: string nullable: true description: Location; null = the step's. meeting_url: type: string nullable: true description: Video link; null = the step's. interviewer_profile_id: type: string nullable: true format: uuid description: Who holds it (profile.id); null = the position's recruiter. note: type: string nullable: true description: Internal note. agenda: type: string nullable: true description: Panel agenda. status: type: string enum: - active - deleted description: active, or deleted after a delete. booked_count: type: integer description: Candidates booked on it before this call. panel_profile_ids: type: array items: type: string format: uuid description: The panel members this call set (besides the lead). required: - id - step_id - position_id - start_at - duration_minutes - capacity - location - meeting_url - interviewer_profile_id - note - agenda - status - booked_count securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: 'Supabase JWT — `Authorization: Bearer `.' ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.