canonical: https://jentic.com/apis/taskip.net/taskip

# Taskip API

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.

## For AI agents

Programmatically create contact, list contacts. Covers 75 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or developer tools - use for crm only.

## Capabilities

- Create contact
- List contacts
- Get contact
- Update contact
- Delete contact
- Bulk delete contacts
- Invite client

## Use cases

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

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

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

Example prompt: Search Jentic for 'create contact', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/contact` | Create contact |
| GET | `/contact` | List contacts |
| GET | `/contact/{id}` | Get contact |
| PUT | `/contact/{id}` | Update contact |
| DELETE | `/contact/{id}` | Delete contact |
| POST | `/contact/bulk-delete` | Bulk delete contacts |
| POST | `/contact/invite-client` | Invite client |
| POST | `/company` | Create company |

## Key resources

- **Companies** — Operations related to Companies
- **Contacts** — Operations related to Contacts
- **Deals** — Operations related to Deals
- **Documents** — Operations related to Documents
- **Inbox** — Operations related to Inbox

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 61 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 89 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 46 / 100
  - Agent Usability: 90 / 100
  - Security: 50 / 100
  - AI Discoverability: 51 / 100
- **View full report:** https://jentic.com/apis/taskip.net/taskip/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

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

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

Yes. Because you run Jentic One yourself, your own rules decide which Taskip operations and credentials the agent may use. Since the contact id sits in the URL path (`/contact/{id}`), a rule can pin the agent to a single contact so it only reads and updates that record. You pick the operations it may call, so destructive ones like deleting a contact or bulk-deleting contacts stay off unless you explicitly add them.