Skip to main content

Setting up OpenAPI (Beta)

Use the Klipy API to integrate with other tools

Jung Hong Kim avatar
Written by Jung Hong Kim
Updated over a month ago

Klipy CRM provides a RESTful API that allows you to programmatically interact with your CRM data. This documentation will guide you through authentication and basic usage of the API.

Important Notice

⚠️ Beta Release: The Klipy API is currently in open beta. Please note:

  • No Service Level Agreement (SLA) is provided during the beta period

  • API operations are not reversible - please use with caution

  • Test thoroughly in a non-production environment first

  • API specifications may change without prior notice

Authentication

All API requests require authentication using an API key in the header.

API Key Management

Obtaining an API Key

  1. Log in to your Klipy CRM account

  2. Navigate to Settings → API (Link)

  3. Click "Generate Key"

  4. Enter the name of the key (e.g. Zapier Test)

Using Your API Key

Include your API key in all API requests using the following header:

X-KLIPY-API-KEY: klipy_pk_<your_api_key_here>

Revoking an API Key

  1. Log in to your Klipy CRM account

  2. Navigate to Settings → API (Link)

  3. Find the API key you want to revoke

  4. Click "Remove"

Verifying Your API Key

Test your API key by making a GET request to the authentication endpoint:

curl --request GET \ --url https://api.klipycrm.com/api/v1/authenticate \ --header 'X-KLIPY-API-KEY: your_api_key_here'

Successful response:

{ "team_name": "Your_Team_Name" }

API Documentation

Complete API documentation is available at:
https://developer.klipycrm.com/api-reference


Rate Limits

  • Standard rate limits apply

  • Status code 429 indicates you've exceeded the rate limit

  • Implement appropriate retry logic in your applications

Best Practices

  1. Store API keys securely

  2. Rotate API keys periodically

  3. Use separate API keys for different environments

  4. Monitor API usage and response patterns

  5. Implement proper error handling

  6. Test thoroughly before production use

Did this answer your question?