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.