---
title: "Introduction to the Crono API"
description: "A high-level overview of the Crono API, how it works, and what you can achieve by integrating it with external tools."
url: https://help.crono.one/it/articles/56-introduction-to-the-crono-api
collection: "Connections"
updated: 2026-09-14
language: it
alternates: [en]
---

# Introduction to the Crono API

A high-level overview of the Crono API, how it works, and what you can achieve by integrating it with external tools.

The Crono External API lets you connect Crono to external tools, automation platforms, internal systems, and custom workflows. It provides programmatic access to the same core resources you use inside Crono, making it possible to automate data flows, enrich records, and build custom integrations.

This article provides a high-level overview of how the API works and what you can do with it.

## What you can do with the Crono API

The API enables you to:

-   Create and update **Accounts**
    
-   Create and update **Contacts**
    
-   Add items to **Lists**
    
-   Trigger **Enrichment** workflows
    
-   Sync information between Crono and external tools
    
-   Automate lead flows and database updates
    
-   Build custom dashboards or backend services
    

Any system capable of sending HTTP requests can integrate with Crono.

## Where to find the full API documentation

The complete API reference, including all endpoints, request schemas, examples, and response formats, is available at: [**https://ext.crono.one/docs/**](https://ext.crono.one/docs/)

This documentation is continuously updated as new endpoints are added.

## Base URL

All Crono API requests use the following base URL:

```javascript
https://ext.crono.one/api/v1
```

Each resource (Accounts, Contacts, Lists…) extends this base path.

## Authentication model

Crono uses header-based authentication with two keys:

-   **X-Api-Key** (Public API Key)
    
-   **X-Api-Secret** (Private API Key)
    

Both keys must be included in every request.  
  
The Crono External API is available on **Ultra and Enterprise**. If you are on another plan and need API access, **get in touch** — it can be enabled for an individual workspace on request. Until API access is enabled, the Connections section does not appear and no keys can be generated. The API settings page is visible only to **Managers**.

To learn how to generate keys, see the article: [**How to generate API Keys**](https://help.crono.one/en/articles/55-how-to-generate-api-keys.md).

## Supported tools and integrations

You can use the Crono API with virtually any platform that supports HTTP requests. Popular options include:

-   n8n
    
-   Zapier
    
-   Make
    
-   Unify
    
-   Freckle
    
-   Clay
    
-   Attio
    
-   Folk
    
-   Monday
    
-   Custom backend servers and scripts
    
-   Internal tools
    

The API is flexible and designed to support many workflows. Creativity is the only limit.

## Who should use the Crono API

The API is designed for:

-   Operations and automation teams
    
-   Developers building custom integrations
    
-   Teams using no-code tools (n8n, Make, Zapier, Clay, Attio, etc.)
    
-   Agencies and consultants integrating Crono into client workflows
    

If you want to automate processes or move data between systems, the API is the recommended method.

## API rate limits

The following rate limits apply to Crono API requests:

-   **API key limit** (`X-API-Key`, pre-auth): 50 requests / 10 seconds and 2,000 requests / 10 minutes
    
-   **Subscription limit** post-auth: 250,000 requests / day
    

The subscription daily limit resets at midnight UTC.