Linkedape Aimfox API

Name: Aimfox API
Brand: Aimfox API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingMarketing AutomationapiKey9 EndpointsREST

For Agents

Run LinkedIn outreach campaigns, manage leads, and send messages on Aimfox via 9 API-key-authenticated endpoints.

Install Jentic One Beta

Connect the Aimfox API to your agent

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

Create, update, and delete LinkedIn outreach campaigns scoped to an Aimfox workspace

List leads enrolled in active campaigns and pull individual lead profiles

Send LinkedIn messages to specific leads through an automated outreach sequence

GET STARTED

Start building with Aimfox API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Aimfox API for, with concrete tasks.

★ LinkedIn Outreach Automation

Programmatically create and update LinkedIn outreach campaigns in Aimfox to scale prospecting beyond manual messaging. POST /campaigns and PATCH /campaigns/{id} support full campaign lifecycle, while POST /messages sends targeted follow-ups. Replaces manual campaign cloning with API-driven workflows.

Create a campaign named 'Q3 fintech CTOs' with target audience filters and a 3-step message sequence

Lead Pipeline Sync

Sync Aimfox leads and connections into a CRM each night to keep the sales pipeline current. The /leads and /connections endpoints expose lead and connection records that can be diffed against CRM state. Replaces CSV exports from the Aimfox UI with continuous sync.

Pull all leads added to Aimfox in the last 24 hours and upsert them into the CRM as new records

Personalized Message Sending

Send personalized LinkedIn messages to selected Aimfox leads as part of a research-then-outreach workflow. POST /messages accepts a lead ID and message body, enabling context-aware outreach. Useful when the agent has enriched lead data outside Aimfox.

Send a personalized message to lead ID 'lead-9912' referencing their recent funding announcement

AI Agent SDR Assistant

An AI agent uses Jentic to discover Aimfox operations by intent and runs a daily SDR routine - surface new leads, draft personalized openers, and send messages. The agent composes campaign, lead, and message endpoints in sequence. Credentials stay isolated through Jentic.

Search Jentic for 'send a LinkedIn message via Aimfox', load POST /messages, and send a personalized opener to today's hottest leads

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/campaigns

Create a LinkedIn outreach campaign

GET

/campaigns

List all campaigns

GET

/campaigns/{id}

Get a campaign by ID

GET

/leads

List leads enrolled in campaigns

POST

/messages

Send a LinkedIn message to a lead

GET

/connections

List LinkedIn connections

POST

/campaigns

Create a LinkedIn outreach campaign

GET

/campaigns

List all campaigns

GET

/campaigns/{id}

Get a campaign by ID

GET

/leads

List leads enrolled in campaigns

POST

/messages

Send a LinkedIn message to a lead

GET

Why Jentic?

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

Credential isolation

Your Aimfox 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 'send a LinkedIn message' or 'list campaign leads', and Jentic returns the matching Aimfox operation with its request schema and required header so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Aimfox API through Jentic.

Why is there no official OpenAPI spec for Aimfox API?

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

Aimfox uses an API key supplied in the X-API-Key header. Generate the key from the Aimfox dashboard. Through Jentic, the API key is stored encrypted in your Jentic One instance and injected per request.

Can I send LinkedIn messages programmatically with Aimfox?

Yes. POST /messages sends a LinkedIn message to a target lead within an active campaign. The lead must already exist in the Aimfox workspace; first call GET /leads to resolve the lead ID.

What are the rate limits for the Aimfox API?

Aimfox enforces LinkedIn-aware throttling - message sending is constrained to LinkedIn safety limits per connected account. Exceeding limits returns HTTP 429; back off and retry with longer delays.

How do I create a LinkedIn outreach campaign through Jentic?

Run pip install jentic, then search Jentic with 'create a LinkedIn outreach campaign' to retrieve POST /campaigns. Execute it with the campaign payload; Jentic handles the X-API-Key header automatically.

Is the Aimfox API free?

API access requires a paid Aimfox plan. Pricing depends on the number of connected LinkedIn accounts and concurrent campaigns; check linkedape.com for current tiers.

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

Yes. Because you run Jentic One yourself, your own rules decide which Aimfox operations and credentials the agent may use. Since Aimfox puts the campaign ID in the URL path (/campaigns/{id}), a rule can pin the agent to a single campaign so it can read that campaign and list its leads through GET /campaigns/{id} and GET /leads. You choose which operations are allowed, so write actions like POST /messages or POST /campaigns stay off limits unless you explicitly add them.

Linkedape Aimfox API

Connect the Aimfox API to your agent

Capabilities

Start building with Aimfox API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs