Jicoo

Delete a webhook endpoint.

Fetch available schedules for an event type by event type ID/UID, or by an exact unique event type name. The input schema stays `eventTypeId`; when a name is supplied, the server resolves it through the authorized team event type list before calling the existing API. `periodStart` and `periodEnd` must be ISO 8601 date-time strings with a timezone offset, for example 2026-06-19T10:00:00.000Z.

Fetch a single booking.

Fetch booking contacts.

Fetch meeting recap fields for a booking.

Fetch meeting recording fields for a booking.

Fetch meeting transcript fields for a booking.

List bookings for the authorized team. By default this tool auto-paginates and returns ALL bookings in a single response (perPage=100 per backend request, up to 100 pages). If `page` or `perPage` is supplied explicitly the tool falls back to single-page behavior.

Fetch a user's busy times (blocked/occupied intervals) within a date range, complementing getAvailableSchedules (which returns open slots). `userId` is the target user's ID/UID. `start` and `end` must be ISO 8601 date-time strings with a timezone offset, for example 2026-06-19T10:00:00.000Z; `end` must be greater than or equal to `start` and the range is capped by the API (a 400 is returned when it is too large). Only time intervals are returned, not event details.

Fetch a single event type by event type ID/UID, or by an exact unique event type name. The input schema stays `eventTypeId`; when a name is supplied, the server resolves it through the authorized team event type list before calling the existing API.

List event types available to the authorized team. Use this tool when the user identifies a booking page / event type by name and you need to inspect possible exact matches before taking action. By default this tool auto-paginates and returns ALL event types in a single response (perPage=100 per backend request, up to 100 pages). If `page` or `perPage` is supplied explicitly the tool falls back to single-page behavior.

Fetch a single organization user.

Fetch one native routing form by uid. The response contains public, answerable workflow fields only.

Fetch a routing form route by routing form uid. This is a pure read. If no route exists the tool returns route=null and does not create one. Route destinations use destinationType string enum and eventTypeUid; numeric forwardable ids are never exposed.

Fetch visibility rules for a native routing form by uid. This is a pure read. If no visibility rule exists the API returns a default rule object with groups=[]. Use workflow uid values from getRoutingForm when building visibility rule sections and action.targetWorkflowIds. Visibility rule enums are public strings: conditionType and | or; ruleType is | isNot | include | exclude | regex; actionType show | hide.

Fetch a single webhook endpoint.

List webhook endpoints for the authorized team.

List { eventType, hosts } pairs for every event type in the authorized team. By default this tool auto-paginates and returns ALL items in a single response (perPage=100 per backend request, up to 100 pages). If `page` or `perPage` is supplied explicitly the tool falls back to single-page behavior. To get hosts for a specific event type, filter the returned `eventTypeHosts` array by `eventType.uid` client-side.

List host assign rules for an event type via GET /v1/event_types/{eventTypeId}/host_assign_rules. Host assign rules are only active when the parent eventType.hostAssignType is 3 (HostAssignRule). If the event type uses hostAssignType 1 (None) or 2 (RoundRobin), any rules returned here are inert. There is no dedicated getHostAssignRuleById tool: to fetch a single rule, call this tool and filter the returned hostAssignRules[] array by uid on the client side. Each returned rule has: uid, sort, priority, dailyLimitMinutes, weeklyLimitMinutes, monthlyLimitMinutes, conditions[] (each with entities[{ entityType: "User", entityId }]), createdAt, updatedAt. By default this tool auto-paginates and returns ALL rules in a single response (perPage=100 per backend request, up to 100 pages). If `page` or `perPage` is supplied explicitly the tool falls back to single-page behavior.

List organization users for the authorized team. By default this tool auto-paginates and returns ALL organization users in a single response (perPage=100 per backend request, up to 100 pages). If `page` or `perPage` is supplied explicitly the tool falls back to single-page behavior and returns only that page. The returned `pagination` object reflects the LAST fetched page when auto-paginating.

List native routing forms for the authorized team. By default this tool auto-paginates and returns ALL routing forms in a single response. If `page` or `perPage` is supplied explicitly the tool falls back to single-page behavior. Internal numeric form ids are never required; returned form uid values are used as routingFormId.

List schedules for the authorized team. By default this tool auto-paginates and returns ALL schedules in a single response (perPage=100 per backend request, up to 100 pages). If `page` or `perPage` is supplied explicitly the tool falls back to single-page behavior.

List user availability calendars. By default this tool auto-paginates and returns ALL calendars in a single response (perPage=100 per backend request, up to 100 pages). If `page` or `perPage` is supplied explicitly the tool falls back to single-page behavior.

Reschedule a booking.

Submit answers to a routing form by routing form uid. Payload matches POST /v1/routing_forms/{id}/responses and uses workflow uid values from getRoutingForm. This evaluates the route and returns bookingPage/availableSchedules only for event type destinations.

Update a booking using canonical booking payload.

Update an existing event type via public PATCH /v1/event_types/{eventTypeId}. This follows the same public contract style as createEventType: - flat top-level payload (there is no `eventType` wrapper) - string enums for availableUserType / hostAssignType / roundRobinAllocateType / rescheduleType - string enums for eventTypeUsers[].role / userType - string enum for location.phoneType (`none` | `callFromHost` | `callFromGuest`) - string enums inside form.workflows[] for workflowType / validateFormatType / customProps.furiganaFormatType / customProps.dateFormatType / customProps.addressCountryInputType - workflow.createType is not accepted (always set to User server-side); workflow.relations is not accepted (Salesforce-internal field) - internal-only fields such as eventTypeType / displayType / hostOperationType are not accepted - unknown top-level keys are rejected Top-level fields (all optional, but at least one is required): - name / description / slug / duration / intervalMinutes / maxCapacity / bufferBefore / bufferAfter / internalNote - availableUserType: `all` | `anyOne` - hostAssignType: `none` | `roundRobin` | `hostAssignRule` - roundRobinAllocateType: `allocateEqually` | `allocateWeighting` | `allocateRotation` - rescheduleType: `lockRescheduleUser` | `reassign` - location: partial location patch. Hidden internal fields are preserved server-side, so you can send only changed fields. - eventTypeUsers: full replacement list using string enums - form: `{ workflows }` — full replace of the booking form workflows - hostAssignRules: uid-based sync payload. Known `uid` updates, omitted existing rules delete, new items create. Common pitfalls: - eventTypeUsers is a full replace. - hostAssignRules is a SYNC (uid-based diff) — omitted uids trigger deletion. - location is partial, but the API preserves hidden internal fields instead of letting callers set them. On success the API returns the updated public read item directly.

Update an event type host.

Update an existing host assign rule via PATCH /v1/event_types/{eventTypeId}/host_assign_rules/{hostAssignRuleUid}. The hostAssignRuleUid must be obtained from listHostAssignRules first (no dedicated getById endpoint exists). Body schema (public update params — all top-level keys are optional, partial update): - sort: non-negative integer - priority: integer in [0, 3] - dailyLimitMinutes: integer >= 1 | null - weeklyLimitMinutes: integer >= 1 | null - monthlyLimitMinutes: integer >= 1 | null - conditions: array of { entities: [{ entityType: "User", entityId }] } IMPORTANT behaviors: - When conditions is omitted, existing conditions are preserved (no-op). - When conditions is sent, it FULLY REPLACES the existing conditions (not a merge). Fetch the current rule via listHostAssignRules and resend the full conditions list to add or remove entries safely. - Every entityId in conditions MUST already be registered as an EventTypeUser on the parent event type. Otherwise the API returns 400 "Invalid entityId(s): ...". - roundRobinAllocateType and per-entity priority/sort are NOT accepted by the public API; the server internally hardcodes sort=index+1, priority=0 for each entity on every update.

Update a native routing form by uid using public identifiers. Payload is a partial routing form update. Use projectUid or projectId only for a project in the authorized team. External forms and Salesforce forms are rejected.

Replace answers for an existing routing form response by uid. Payload matches PATCH /v1/routing_forms/{id}/responses/{rid}. It updates the response and re-evaluates routing; it does not create a booking or persist schedule selections.

Create or update the route for a native routing form by uid. If the route is missing, the API creates exactly one route and applies the payload. Use destinationType: eventType | redirect | message | noRouting. For eventType destinations, send eventTypeUid in the default destination and in every groups[] destination. Do not send numeric forwardableId; it is an internal database id and is not accepted.

Create or update visibility rules for a native routing form by uid. Payload matches PATCH /v1/routing_forms/{id}/visibility_rule and contains groups[]. Payload shape: { groups: [{ uid, conditionType, sections: [{ uid, conditionType, workflowId, ruleType, contents: [{ conditionType, content, contentId }], subFieldPath? }], action: { actionType, targetWorkflowIds } }] }. Use workflow uid values from getRoutingForm; numeric form ids and team ids are never required. Use public string enums: conditionType and | or; ruleType is | isNot | include | exclude | regex; actionType show | hide. Do not send numeric enum values.

Update a schedule.

Update a webhook endpoint via PATCH /v1/webhook_endpoints/{webhookEndpointId}. Team context is resolved from the access token. Common update fields (all optional, partial update): - url: string (https URL, localhost rejected) - description: string | null - status: string enum, `enable` | `disable` - scope: string enum, `team` (all event types) | `eventType` (restricted to selected event types) Not accepted on the public PATCH endpoint: - events / webhookType: managed internally; not settable via the public API.