Beetribe - Zapier API documentation
Agent-ready OpenAPI document · curated by JenticDeveloper ToolsProject ManagementapiKey3 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Authenticate Zapier-style integrations with Beetribe and read or write hive and queen records through a 3-endpoint Zapier-facing API.
Use for: Validate a Beetribe API token for a Zapier integration, Pull the latest queens from my Beetribe account, Send a record from a Zapier flow into Beetribe, I want to set up a Zapier trigger for new queens in Beetribe
Not supported: Does not handle hive sensor telemetry streams, payment processing, or end-user UI rendering - use for Zapier-driven authentication, queen records, and inbound record ingestion only.
Jentic publishes the only available OpenAPI specification for Beetribe - Zapier API documentation, keeping it validated and agent-ready. Beetribe is a beekeeping management platform, and this Zapier-facing API exposes the minimal surface needed to authenticate Zapier-hosted integrations and read or write data into the platform. The 3-endpoint API covers Zapier auth, a queens listing trigger, and a generic master endpoint used to receive Zapier-sourced records, secured by an X-TOKEN API key in the header.
Install Jentic One Beta
Connect the Beetribe - Zapier API documentation to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Beetribe - Zapier API documentation, 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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbeetribe.io%2Fbeetribe" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbeetribe.io%2Fbeetribe" | 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.
Capabilities
What an agent can do with Beetribe - Zapier API documentation API.
Authenticate a Zapier-style integration against Beetribe and validate the X-TOKEN API key
Trigger a Zapier flow when a new queen record is created in Beetribe
Receive arbitrary Zapier-sourced records into Beetribe via the master endpoint
Pull the current list of queens recorded in the user's Beetribe account
Use Cases
Patterns agents use Beetribe - Zapier API documentation API for, with concrete tasks.
★ Zapier integration auth and dropdowns
Beetribe's Zapier integration uses POST /zapier-auth to validate the user's X-TOKEN at install time and surface a friendly account label in the Zapier UI. GET /zapier-getqueens populates dropdowns inside Zap steps so users pick a queen by name rather than ID. This minimal surface is what Zapier needs to wire authentication and dynamic field lookups for downstream Zaps.
Call POST /zapier-auth with a candidate X-TOKEN and confirm the integration is recognised, then list queens via GET /zapier-getqueens to populate a Zap dropdown
Inbound record ingestion from no-code flows
Beekeepers using Zapier collect hive inspection notes, queen lineage records, or sensor readings from many sources - Google Sheets, mobile forms, IoT gateways - and pipe them into Beetribe. POST /master-endpoint accepts a generic structured payload from a Zap so the records land in Beetribe without a per-source endpoint. This keeps the integration surface tight while still supporting a wide range of inbound sources.
Post a hive inspection record with hive_id 12 and note Queen seen, no swarm cells to /master-endpoint via the configured Beetribe X-TOKEN
Queen records sync to other tools
Hobbyist and commercial beekeepers want a single source of truth for queen lineage. GET /zapier-getqueens returns the queens recorded in Beetribe so a Zap can mirror them into Airtable, a Google Sheet, or a CRM for breeding programmes and customer records. The Zapier-friendly response shape keeps each downstream Zap simple.
Pull all queens from /zapier-getqueens and push the new ones since last run into an Airtable base named Apiary Queens
AI agent integration for beekeeping records
Apiary managers use AI agents through Jentic to keep queen and hive records consistent across tools without writing Zaps for every flow. The agent reads queens from Beetribe, posts new inspection records, and reports back changes, with the X-TOKEN held in your Jentic One instance so it never enters agent context.
Through Jentic, find Beetribe's queens listing operation and produce a weekly snapshot of all recorded queens with their hive assignments
Key Endpoints
3 endpoints — jentic publishes the only available openapi specification for beetribe - zapier api documentation, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/zapier-auth
Validate a Zapier X-TOKEN credential
GET
/zapier-getqueens
List queens for Zapier dropdowns and triggers
POST
/master-endpoint
Receive generic Zapier-sourced records
POST
/zapier-auth
Validate a Zapier X-TOKEN credential
GET
/zapier-getqueens
List queens for Zapier dropdowns and triggers
POST
/master-endpoint
Receive generic Zapier-sourced records
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Beetribe API by hand means carrying the X-TOKEN header, running the Zapier auth exchange, and posting records to the master endpoint yourself. Through Jentic you install once, import the Beetribe API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Beetribe uses Zapier-style endpoints that take their targets in the request body rather than as a resource in the URL path, so scope the agent to the operations it needs, such as listing queens. You choose that operation set, so posting records to the master endpoint is not included unless you add it.
Credential isolation
Your Beetribe X-TOKEN API key is stored once, encrypted, by your own Jentic One instance and injected as the X-TOKEN header at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list Beetribe queens' or 'post a record to Beetribe', and Jentic returns the matching operation with its input schema so the agent calls /zapier-getqueens or /master-endpoint without browsing the SwaggerHub reference.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Beetribe - Zapier API documentation API through Jentic.
Why is there no official OpenAPI spec for Beetribe - Zapier API documentation?
Beetribe publishes a SwaggerHub-hosted reference but not a stable OpenAPI document at a discoverable URL on its own domain. Jentic generates and maintains this spec so that AI agents and developers can call Beetribe 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 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.
GET STARTED