For Agents
Programmatically create contact, list contacts. Covers 75 operations with apiKey authentication.
Use for: I need to contact, I want to contacts, Search for contact, Find all contact
Not supported: Does not handle payments, communications, or developer tools - use for crm only.
Taskip public API for managing contacts, companies, team members, invoices, quotations, support tickets, documents, projects, sales pipelines, meetings, and inbox conversations. The API exposes 75 endpoints secured with apiKey authentication.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Taskip 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftaskip.net%2Ftaskip" | shStep 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%2Ftaskip.net%2Ftaskip" | 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 Taskip API.
Create contact
List contacts
Get contact
Update contact
Delete contact
Bulk delete contacts
Invite client
Patterns agents use Taskip API for, with concrete tasks.
★ CRM Operations
Use the Taskip API to perform crm operations programmatically. The API provides 75 endpoints covering core functionality including create contact, list contacts, get contact.
Call POST /contact to create contact
Automated Companies Management
Automate companies operations by combining multiple Taskip API endpoints. Agents can list contacts and then get contact in a single workflow.
Call GET /contact to list contacts, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Taskip 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 'create contact', load the operation schema, and execute with Jentic-managed credentials
75 endpoints — taskip public api for managing contacts, companies, team members, invoices, quotations, support tickets, documents, projects, sales pipelines, meetings, and inbox conversations.
METHOD
PATH
DESCRIPTION
/contact
Create contact
/contact
List contacts
/contact/{id}
Get contact
/contact/{id}
Update contact
/contact/{id}
Delete contact
/contact/bulk-delete
Bulk delete contacts
/contact/invite-client
Invite client
/company
Create company
/contact
Create contact
/contact
List contacts
/contact/{id}
Get contact
/contact/{id}
Update contact
/contact/{id}
Delete contact
/contact/bulk-delete
Bulk delete contacts
/contact/invite-client
Invite client
/company
Create company
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Taskip API by hand means sending its X-Secret-Key header on every request, targeting the public-api.taskip.net host, and building your own retry handling across its many CRM endpoints. Through Jentic you install once, import the Taskip API from the API Directory, store the secret key once, and your agent calls it.
Permission scoping
The Taskip API puts the contact id in the URL path (/contact/{id}), so a rule can pin your agent to one contact: it can read and update that record. You choose the operations it may call, so destructive ones like deleting a contact or bulk-delete are not included unless you add them.
Credential isolation
Your Taskip secret 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 'create a contact' or 'invite a client', and Jentic returns the matching Taskip API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Taskip API through Jentic.
What authentication does the Taskip API use?
The Taskip API uses an API key passed in the `X-Secret-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 create contact with the Taskip API?
Yes. Use the POST /contact endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Taskip 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 create contact through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create contact'. Jentic returns the matching Taskip API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Taskip API have?
The Taskip API exposes 75 endpoints covering companies, contacts, deals operations.
GET STARTED