What authentication does the Beetribe API use?

Beetribe uses an API key sent in the X-TOKEN header on every request. You generate the token from your Beetribe account's Zapier integration settings. Jentic stores the token in its vault and injects the header at execution time so it never enters agent context.

What does the master-endpoint accept?

POST /master-endpoint is the generic inbound ingest used by Zapier-driven Zaps. It accepts a structured payload with the record type and fields, so a single endpoint can receive hive inspections, queen records, or sensor data without a dedicated path per source. Validate against the response to confirm the record was accepted.

How do I trigger a Zap on new queens through Jentic?

Search Jentic for list Beetribe queens to find GET /zapier-getqueens. Schedule the agent to call it on a polling interval and diff the result against the last snapshot. Each new queen can then be forwarded to a downstream tool such as Airtable or a CRM.

Is the Beetribe API limited to Zapier use?

The published Zapier-facing surface is intentionally minimal - three endpoints designed to power Zapier triggers, dropdowns, and writes. Direct integrations can use the same X-TOKEN auth and call the endpoints from any HTTP client. Richer functionality lives inside the Beetribe app rather than this API surface.

What are the rate limits for the Beetribe API?

Beetribe does not publish explicit rate limits in the spec. Because the API is sized for Zapier polling intervals (commonly every 5-15 minutes), keep agent polling within that range and back off on HTTP 429 responses with exponential delay.

Can I limit what my agent is allowed to do with the Beetribe API?

Yes. Because you self-host Jentic One, your own rules decide which of Beetribe's three operations the agent can call and which credentials it may use, so you can allow only GET /zapier-getqueens to read your queen records while excluding writes. Beetribe's endpoints take their targets in the request body rather than in the URL path, so scoping is done at the operation level: POST /master-endpoint, which ingests arbitrary records, is not available to the agent unless you add it, and POST /zapier-auth stays limited to token validation. You pick that operation set, and the agent cannot reach any Beetribe operation you have not granted.