Workee API
✓ Official Vendor SpecDeveloper ToolsSource ControlapiKey4 EndpointsREST
For Agents
Programmatically test zapier connection, subscribe trigger. Covers 4 operations with apiKey authentication.
Use for: I need to test zapier connection, I want to subscribe trigger, Search for unsubscribe trigger, Find all sample data
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Workee API for managing Zapier webhook connections and triggers. The API exposes 4 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the Workee API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Workee 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.
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%2Fworkee.ai%2Fworkee" | 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%2Fworkee.ai%2Fworkee" | 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 Workee API.
Test Zapier connection
Subscribe trigger
Unsubscribe trigger
Get sample data
Monitor Workee API operational status and events
Use Cases
Patterns agents use Workee API for, with concrete tasks.
★ Developer Tools Operations
Use the Workee API to perform developer tools operations programmatically. The API provides 4 endpoints covering core functionality including test zapier connection, subscribe trigger, unsubscribe trigger.
Call GET /zapier/connections/test to test zapier connection
Automated Connections Management
Automate connections operations by combining multiple Workee API endpoints. Agents can subscribe trigger and then unsubscribe trigger in a single workflow.
Call POST /zapier/connections/subscribe to subscribe trigger, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Workee API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'test zapier connection', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
4 endpoints — workee api for managing zapier webhook connections and triggers.
METHOD
PATH
DESCRIPTION
GET
/zapier/connections/test
Test Zapier connection
POST
/zapier/connections/subscribe
Subscribe trigger
POST
/zapier/connections/unsubscribe
Unsubscribe trigger
GET
/zapier/connections/sample-data
Get sample data
GET
/zapier/connections/test
Test Zapier connection
POST
/zapier/connections/subscribe
Subscribe trigger
POST
/zapier/connections/unsubscribe
Unsubscribe trigger
GET
/zapier/connections/sample-data
Get sample data
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Workee API by hand means setting up its header API key and managing the Zapier connection lifecycle yourself. Through Jentic you install once, import the Workee API from the API Directory, store the API key once, and your agent calls it.
Permission scoping
The Workee API carries its target in the request body rather than the URL path, so scope by operation: limit the agent to the operations it needs, such as testing a connection or fetching sample data. You choose that set, so subscribe and unsubscribe calls are not included unless you add them.
Credential isolation
Your Workee API key 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.
Intent-based discovery
Agents search Jentic by intent such as 'test a Zapier connection' or 'get sample data', and Jentic returns the matching Workee API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
FAQs
Specific to using Workee API through Jentic.
What authentication does the Workee API use?
The Workee API uses an API key passed in the `X-API-KEY` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I test zapier connection with the Workee API?
Yes. Use the GET /zapier/connections/test endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Workee API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I test zapier connection through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'test zapier connection'. Jentic returns the matching Workee API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Workee API have?
The Workee API exposes 4 endpoints covering connections operations.
GET STARTED