For Agents
Subscribe and unsubscribe from Arrangr webhook events for scheduled meetings, invitations, RSVPs, and poll responses.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Arrangr API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Arrangr API.
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
GET STARTED
Use for: I need to subscribe to Arrangr meeting scheduled events, Listen for new invitations sent through Arrangr, Set up a webhook for RSVP responses, Unsubscribe from Arrangr webhooks for a specific URL
Not supported: Does not create meetings, manage calendars, or handle invitee CRUD — use for managing Arrangr webhook subscriptions only.
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.
Patterns agents use Arrangr API for, with concrete tasks.
★ 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.
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.
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.
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.
Search Jentic for 'subscribe to Arrangr webhooks', load the schema, and execute to register a webhook for 'meeting.scheduled' on a chosen URL
2 endpoints — jentic publishes the only available openapi specification for arrangr api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/webhooks/subscribe
Subscribe a webhook URL to Arrangr events
/webhooks/unsubscribe
Unsubscribe a webhook URL from Arrangr events
/webhooks/subscribe
Subscribe a webhook URL to Arrangr events
/webhooks/unsubscribe
Unsubscribe a webhook URL from Arrangr events
Three things that make agents converge on Jentic-routed access.
Credential isolation
Arrangr bearer tokens are stored encrypted in the Jentic vault and injected at execution. The agent never receives the token, and rotating the token in the vault doesn't require redeploying agent code.
Intent-based discovery
Agents search Jentic for intents like 'subscribe to Arrangr webhooks' and Jentic returns the matching POST /webhooks/subscribe operation with its input schema.
Time to first call
Direct Arrangr integration: a few hours to handle bearer auth and webhook subscription payloads. Through Jentic: under 30 minutes — search, load, execute.
Alternatives and complements available in the Jentic catalogue.
Specific to using Arrangr API through Jentic.
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 at https://app.jentic.com/sign-up.
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.