canonical: https://jentic.com/apis/arrangr.com/arrangr # Arrangr API Jentic publishes the only available OpenAPI specification for Arrangr API, keeping it validated and agent-ready. Arrangr is a meeting scheduling platform, and its public API is webhook-centric - two endpoints let you subscribe and unsubscribe from webhook events for meeting lifecycle activity, including scheduled meetings, sent and received invitations, event RSVPs, and poll responses. Use these subscriptions to feed Arrangr meeting events into downstream CRM, calendar, and workflow systems. ## For AI agents Subscribe and unsubscribe from Arrangr webhook events for scheduled meetings, invitations, RSVPs, and poll responses. ## Scope Does not create meetings, manage calendars, or handle invitee CRUD - use for managing Arrangr webhook subscriptions only. ## Capabilities - Subscribe to Arrangr webhook events for scheduled meetings - Subscribe to invitation sent and received events - Subscribe to event RSVP and poll response events - Unsubscribe a webhook URL from Arrangr events ## Use cases ### CRM Activity Logging Push every Arrangr meeting that gets scheduled into a CRM as a logged activity. Subscribe via `/webhooks/subscribe` to the meeting-scheduled event, then handle the resulting webhook payloads server-side and create the matching CRM activity. Saves sales reps from manually re-entering meetings into HubSpot or Salesforce. Example prompt: POST `/webhooks/subscribe` with event type 'meeting.scheduled' and a target URL pointing at the CRM ingestion endpoint, then verify the subscription is active ### Poll Response Aggregation Aggregate poll responses from Arrangr meeting polls in near real time by subscribing to the poll response webhook event. Each response triggers a webhook call which can be written to a database for downstream reporting on attendee preferences and time-slot demand. Example prompt: Subscribe to the 'poll.response' event with a webhook handler that writes each response to a Postgres table ### Calendar Bridge Bridge Arrangr meeting confirmations into a separate calendar or notification system. Once a meeting is scheduled, the webhook fires and the receiver can create a Google Calendar entry, send a Slack heads-up, or record the appointment in a field service tool. Example prompt: Subscribe to 'meeting.scheduled' and on each webhook call create a corresponding Google Calendar event ### Agent-Driven Event Listening via Jentic Let an automation agent register and clean up Arrangr webhooks on demand without storing the bearer token in the agent's process. The agent searches Jentic for 'subscribe to Arrangr webhooks', loads the schema, and executes; clean-up runs the same way against `/webhooks/unsubscribe.` Example prompt: Search Jentic for 'subscribe to Arrangr webhooks', load the schema, and execute to register a webhook for 'meeting.scheduled' on a chosen URL ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/webhooks/subscribe` | Subscribe a webhook URL to Arrangr events | | POST | `/webhooks/unsubscribe` | Unsubscribe a webhook URL from Arrangr events | ## Key resources - **Webhook Subscriptions** — Subscribe and unsubscribe webhook URLs to Arrangr meeting lifecycle events ## Why Jentic - **Setup:** Wiring Arrangr by hand means learning its bearer auth and managing webhook subscribe and unsubscribe calls yourself. Through Jentic you install once, import the Arrangr API from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** Arrangr's webhook subscribe and unsubscribe take their target in the request body rather than a URL path, so limit the agent to the operations it needs, such as subscribing to a webhook. You choose the operations it may call, so unsubscribe is not included unless you add it. - **Credential handling:** Your Arrangr bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'subscribe to Arrangr webhooks', and Jentic returns the matching POST `/webhooks/subscribe` operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Calendly API** — Calendly is a broader meeting scheduling API with full CRUD on event types, invitees, and webhooks - **HubSpot CRM Contacts API** — HubSpot CRM is a natural target for logging Arrangr meeting events as activities - **Slack API** — Slack receives the human-facing notification that an Arrangr meeting has been scheduled ## FAQ ### Why is there no official OpenAPI spec for Arrangr API? Arrangr does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Arrangr API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Arrangr API use? Arrangr uses HTTP Bearer authentication. You pass an API token in the Authorization header. Through Jentic, the token is stored encrypted in the vault and injected at execution, so the agent never sees the raw bearer secret. ### Can I subscribe to scheduled meeting events with the Arrangr API? Yes. POST `/webhooks/subscribe` registers a webhook URL for Arrangr events including scheduled meetings, sent and received invitations, RSVPs, and poll responses. ### What are the rate limits for the Arrangr API? Arrangr does not publish a hard rate limit for the webhooks API. Subscriptions are control-plane operations rather than per-event calls, so usage is naturally light - register once and let Arrangr push events to your URL. ### How do I unsubscribe from Arrangr webhooks through Jentic? Run pip install jentic, then search Jentic with 'unsubscribe from Arrangr webhooks', load the schema for POST `/webhooks/unsubscribe`, and execute with the URL and event type you previously registered. ### Does the Arrangr API let me create or fetch meetings directly? Not in this public webhook-focused interface. The two endpoints exposed cover webhook subscription management; the actual meeting data arrives via the webhook payloads delivered to your subscribed URL. ### Can I limit what my agent is allowed to do with the Arrangr API? Yes. Because Jentic One is self-hosted, you set the rules that decide which Arrangr operations and credentials your agent can use. Arrangr exposes just two operations, POST `/webhooks/subscribe` and POST `/webhooks/unsubscribe`, and both take their target in the request body, so you can grant the agent only subscribe and leave unsubscribe out until you choose to add it. That way the agent registers the webhooks you allow and cannot remove subscriptions unless you explicitly permit it.