canonical: https://jentic.com/apis/fiksu.cc/fiksu

# Fiksu Cc Fiksu

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.

## For AI agents

Manage leads, individuals, and businesses for SMB CRM workflows via 13 endpoints with API-key auth, plus Zapier subscription support.

## Scope

Does not handle email marketing, deal pipelines, or call recording - use for managing Fiksu leads, individuals, businesses, and Zapier triggers only.

## Capabilities

- 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
- Subscribe and unsubscribe Zapier triggers programmatically
- Delete a lead by its ID when it is disqualified

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'list leads', call GET `/api/lead/{businessId}` for each owned business, return the top 5 oldest unanswered leads

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/lead/new_lead` | Add a new lead |
| GET | `/api/lead/{businessId}` | Get leads for a business |
| DELETE | `/api/lead/{leadId}` | Delete a lead |
| POST | `/api/individual` | Create an individual |
| POST | `/api/business` | Create a business |
| POST | `/api/user/zapier_subscribe` | Subscribe Zapier trigger |

## Key resources

- **Leads** — Capture, list, and delete leads attached to businesses
- **Individuals** — Manage individual contact records
- **Businesses** — Manage business records that own leads
- **User** — Zapier subscription endpoints scoped per user

## Why Jentic

- **Setup:** Wiring Fiksu by hand means sending the token in the Authorization header, pointing at api.fiksu.cc, and mapping leads, individuals, businesses, and Zapier triggers across the endpoints yourself. Through Jentic you install once, import Fiksu from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Fiksu puts the lead and business id in the URL path (`/api/lead/{leadId}`, `/api/lead/{businessId}`), so a rule can pin your agent to the leads you allow. You choose the operations it may call, so a destructive action like deleting a lead is not included unless you add it.
- **Credential handling:** Your Fiksu API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. The raw Authorization header value never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'add a new lead' or 'subscribe a zapier trigger', and Jentic returns the matching Fiksu operation with its input schema, so the agent calls it without reading the api-docs page.

## Related APIs

- **Salesforce API** — Enterprise CRM alternative for teams that have outgrown SMB tools
- **Fergus API** — Trades job management to take Fiksu leads through quote-to-invoice workflows
- **Asana API** — Task management for sales follow-ups triggered by new Fiksu leads

## FAQ

### What authentication does the Fiksu API use?

Fiksu uses an API key sent in the Authorization header. Through Jentic the key is encrypted in your Jentic One instance 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.

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

Yes. Because you self-host Jentic One, your own rules decide which Fiksu operations the agent may call and which credentials it may use. Fiksu carries the lead and business id in the URL path, such as `/api/lead/{leadId}` and `/api/lead/{businessId}`, so a rule can pin the agent to only the leads and businesses you allow. You choose the operations it can reach, so a destructive call like DELETE `/api/lead/{leadId}` stays off limits unless you explicitly grant it.