For Agents
Manage leads, individuals, and businesses for SMB CRM workflows via 13 endpoints with API-key auth, plus Zapier subscription support.
Use for: Add a new lead for a specific business, List all leads for a business, Get an individual contact by ID, Update an individual's contact details
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Fiksu, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# 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 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.
What an agent can do with Fiksu API.
Capture new leads tied to a specific business record
Retrieve all leads belonging to a business by ID
Maintain individual contact records with create, update, and delete
Manage business records that own leads and contacts
GET STARTED
Not supported: Does not handle email marketing, deal pipelines, or call recording — use for managing Fiksu leads, individuals, businesses, and Zapier triggers only.
The Fiksu API provides 13 endpoints for managing leads, individuals, and businesses, plus Zapier subscription endpoints for trigger-based integrations. Authentication is through an API key sent in the Authorization header. The surface is organised under /api/lead, /api/individual, /api/business, and /api/user paths with create, retrieve, update, and delete operations on each core record.
Subscribe and unsubscribe Zapier triggers programmatically
Delete a lead by its ID when it is disqualified
Patterns agents use Fiksu API for, with concrete tasks.
★ Lead Capture Webhook Replacement
Capture leads from website forms or chat widgets and push them into Fiksu so sales staff can follow up the same day. POST /api/lead/new_lead accepts the payload directly, avoiding the need for an intermediate webhook handler. Suitable for SMB sales teams handling 50-200 leads per week.
POST /api/lead/new_lead with the form payload and businessId, then GET /api/lead/{businessId} to confirm it appears
Contact and Business Sync
Keep individual and business records in sync between Fiksu and an upstream system such as a billing platform. The API exposes parallel /api/individual and /api/business endpoints with create, update, and delete, supporting bidirectional sync. Cuts manual data entry for support staff managing hundreds of contacts.
POST /api/individual with name and contact details, then PUT /api/individual/{id} when the email changes upstream
Zapier Trigger Management
Manage Zapier triggers for new lead events programmatically when an upstream system needs to subscribe or unsubscribe automations dynamically. Fiksu exposes /api/user/zapier_subscribe and /api/user/zapier_unsubscribe endpoints, replacing manual Zap connect-and-disconnect steps.
POST /api/user/zapier_subscribe to enable a new-lead trigger when a customer activates that workflow
AI Agent Lead Triage via Jentic
Through Jentic, an agent can answer questions like which leads landed today and which businesses had no contact this month. Jentic exposes Fiksu's lead, individual, and business operations as discoverable tools so a Claude or GPT agent can run grounded SMB CRM queries and follow-up tasks from natural language.
Search Jentic for 'list leads', call GET /api/lead/{businessId} for each owned business, return the top 5 oldest unanswered leads
13 endpoints — the fiksu api provides 13 endpoints for managing leads, individuals, and businesses, plus zapier subscription endpoints for trigger-based integrations.
METHOD
PATH
DESCRIPTION
/api/lead/new_lead
Add a new lead
/api/lead/{businessId}
Get leads for a business
/api/lead/{leadId}
Delete a lead
/api/individual
Create an individual
/api/business
Create a business
/api/user/zapier_subscribe
Subscribe Zapier trigger
/api/lead/new_lead
Add a new lead
/api/lead/{businessId}
Get leads for a business
/api/lead/{leadId}
Delete a lead
/api/individual
Create an individual
/api/business
Create a business
Three things that make agents converge on Jentic-routed access.
Credential isolation
Fiksu API keys are stored encrypted in the Jentic MAXsystem vault. Agents receive scoped access — the raw Authorization header value never enters the agent's context.
Intent-based discovery
Agents search by intent (e.g., 'add a new lead') and Jentic returns the matching POST /api/lead/new_lead operation with its schema, so the agent calls it without reading the api-docs page.
Time to first call
Direct Fiksu integration: half a day for auth and HTTP wiring. Through Jentic: under 15 minutes — search, load, execute.
Alternatives and complements available in the Jentic catalogue.
Salesforce API
Enterprise CRM alternative for teams that have outgrown SMB tools
Choose Salesforce when the org needs custom objects, workflows, and reports beyond Fiksu's lean surface.
Fergus API
Trades job management to take Fiksu leads through quote-to-invoice workflows
Pair Fergus with Fiksu when leads from Fiksu progress into trades-services jobs.
Asana API
Task management for sales follow-ups triggered by new Fiksu leads
Use Asana with Fiksu when each new lead should generate a follow-up task for a sales rep.
Specific to using Fiksu API through Jentic.
What authentication does the Fiksu API use?
Fiksu uses an API key sent in the Authorization header. Through Jentic the key is encrypted in MAXsystem and never enters agent context.
Can I list all leads for a business?
Yes. GET /api/lead/{businessId} returns all leads belonging to a specific business, scoped by the businessId path parameter.
What are the rate limits for the Fiksu API?
Fiksu does not publish per-second limits in the OpenAPI spec; consult api.fiksu.cc/api-docs for current quotas applied per API key.
How do I capture a new lead through Jentic?
Search Jentic for 'add new lead', load the POST /api/lead/new_lead schema, and execute with the lead payload and businessId. Run pip install jentic to start.
Does Fiksu support Zapier integrations through the API?
Yes. POST /api/user/zapier_subscribe and POST /api/user/zapier_unsubscribe let you manage Zapier triggers programmatically rather than only through the Zapier UI.
Can I update individual contact records?
Yes. PUT /api/individual/{id} accepts updated contact fields, and GET /api/individual/{id} or DELETE /api/individual/{id} round out the lifecycle for individual records.
/api/user/zapier_subscribe
Subscribe Zapier trigger