MyWorkerAI API

Name: MyWorkerAI API
Brand: MyWorkerAI API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingMarketing Automationbearer, apiKey4 EndpointsREST

For Agents

List marketing campaigns, retrieve their leads, and filter inbound emails for sales follow-up using AI classification. Best for B2B sales teams running automated outbound campaigns.

Install Jentic One Beta

Connect the MyWorkerAI API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MyWorkerAI 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 | sh

Step 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 instance

Jentic 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 MyWorkerAI API.

List active outbound campaigns the authenticated user owns

Retrieve all leads associated with a specific campaign

Look up an individual lead record by ID for enrichment or follow-up

Classify and filter inbound email content using the AI filter endpoint

GET STARTED

Start building with MyWorkerAI API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use MyWorkerAI API for, with concrete tasks.

★ Outbound Campaign Lead Sync

Pull lead records from MyWorkerAI campaigns into a CRM, data warehouse, or downstream sequencing tool. Sales operations teams use the GET /api/campaign and /api/campaign/{id}/lead endpoints to mirror campaign progress nightly, so reps see fresh prospect data without logging into MyWorkerAI directly. Saves analytics teams from building screen-scrapers when MyWorkerAI is one input among many in a multi-vendor sales stack.

Fetch every lead from campaign ID 17 via GET /api/campaign/{id}/lead and post each as a contact in HubSpot CRM.

Inbound Email Filtering

Classify inbound email replies to outbound campaigns so reps only see genuine sales conversations rather than auto-responses, out-of-office bounces, and spam. POST /api/email/filter accepts the message body and returns a classification useful for routing replies into a CRM, archive, or human review queue. Cuts manual triage time on high-volume reply queues.

Send the body of an inbound email to POST /api/email/filter and route the reply to the SDR queue if it returns a positive sales-intent classification.

Lead Detail Enrichment

Look up individual lead records by ID to enrich contact data, draft personalised follow-ups, or check campaign attribution. GET /api/campaign/lead/{id} returns the full lead object so an AI agent or rep workflow can compose a tailored outreach without re-querying the campaign list. Common pattern when MyWorkerAI is feeding a personalisation layer or AI-generated reply tool.

Retrieve lead ID 482 with GET /api/campaign/lead/{id} and draft a personalised follow-up email referencing their campaign source.

AI Agent Sales Co-Pilot

Wire MyWorkerAI into an AI sales agent through Jentic so the agent can answer questions like 'how many leads are in my Q3 campaign?' or 'classify this reply' without the developer hand-coding requests. Through Jentic's intent search and execution layer, the four MyWorkerAI operations are reachable in under an hour, with credentials isolated server-side.

Search Jentic for 'list MyWorkerAI campaigns', execute the call, then chain into 'get leads for campaign' to summarise pipeline coverage.

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for myworkerai api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/api/campaign

List all campaigns owned by the authenticated user

GET

/api/campaign/{id}/lead

List all leads attached to a specific campaign

GET

/api/campaign/lead/{id}

Retrieve an individual lead record by ID

POST

/api/email/filter

Classify an inbound email body for sales triage

GET

/api/campaign

List all campaigns owned by the authenticated user

GET

/api/campaign/{id}/lead

List all leads attached to a specific campaign

GET

/api/campaign/lead/{id}

Retrieve an individual lead record by ID

POST

/api/email/filter

Classify an inbound email body for sales triage

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

MyWorkerAI bearer tokens and API keys are stored encrypted in the Jentic vault. Agents receive scoped execution access; the raw Authorization header value never enters the agent's prompt or model context.

Intent-based discovery

Agents search by intent (e.g., 'list outbound campaigns') and Jentic returns the matching MyWorkerAI operation with its parameter schema, so the agent can call the right endpoint without reading the spec.

Time to first call

Direct MyWorkerAI integration: 1-2 days for auth handling and lead pagination. Through Jentic: under 30 minutes for the first end-to-end call.

FAQs

Specific to using MyWorkerAI API through Jentic.

Why is there no official OpenAPI spec for MyWorkerAI API?

MyWorkerAI does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call MyWorkerAI 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 MyWorkerAI API use?

The MyWorkerAI API supports two schemes: a JWT bearer token and an API key passed in the Authorization header. Both are configured in components.securitySchemes as jwtAuth and apiKeyAuth. Through Jentic, the credential is held in the encrypted vault and injected at execution time, so the raw token never reaches the agent's context.

Can I retrieve all leads in a campaign with the MyWorkerAI API?

Yes. Call GET /api/campaign/{id}/lead with the campaign ID to get the lead list. Use GET /api/campaign first to discover the IDs of campaigns the authenticated user owns, then iterate over them if you need a full pull.

How does the MyWorkerAI email filter endpoint work?

POST /api/email/filter accepts an email body in the request payload and returns a classification used to triage inbound replies to outbound campaigns. The endpoint is most useful for routing replies into SDR queues versus auto-archive paths.

What rate limits apply to the MyWorkerAI API?

Rate limits are not declared in the OpenAPI spec. Treat the service as moderately rate-limited, implement exponential backoff on HTTP 429, and contact MyWorkerAI support for committed throughput on the email filter endpoint if you process high reply volumes.

How do I call the MyWorkerAI API from an AI agent through Jentic?

Install the Jentic SDK with pip install jentic. Use SearchRequest with a query like 'list MyWorkerAI campaigns' to discover the right operation, LoadRequest to load its schema, and ExecutionRequest to call it. Get an agent API key at https://app.jentic.com/sign-up.