Keplars

API Reference

Complete reference for all Keplars REST API endpoints.

Base URL: https://api.keplars.com/api/v1

All endpoints require a Bearer token:

Authorization: Bearer $KEPLARS_API_KEY

API Key Types

Keplars has two types of API keys with different purposes and formats.

Regular API Keys

Used for sending emails programmatically. Created under Settings → API Keys in the dashboard.

Format:  kms_<workspaceId>.live_<secret>
Example: kms_019abc.live_a1b2c3d4e5f6...

These keys are tied to a specific email account in your workspace and can only call the email sending endpoints.

Admin API Keys

Used for the Marketing API - managing audiences, contacts, and reading campaign data. Created under Settings → Admin API Keys in the dashboard.

Format:  kms_<workspaceId>.adm_<secret>
Example: kms_019abc.adm_x9y8z7w6v5u4...

Admin keys are scoped - you choose which permissions to grant when creating the key.

ScopeAccess
contacts:readList and get contacts
contacts:writeAdd, update, and delete contacts
audiences:manageCreate, list, get, and delete audiences

Which key do I need?

For sending emails → use a Regular API key. For audiences and contacts → use an Admin API key with the required scope. Marketing endpoints reject Regular keys with 403 FORBIDDEN.

Admin key limit

You can have a maximum of 5 Admin API keys per workspace. Regular keys have no limit.


Endpoints


Error Format

All errors return a consistent JSON shape:

{
  "success": false,
  "error": "VALIDATION_ERROR",
  "message": "Field 'to' is required"
}
StatusCodeMeaning
401UNAUTHORIZEDMissing or invalid API key
403FORBIDDENKey type not allowed for this endpoint
403INSUFFICIENT_SCOPEAdmin key missing required scope
400VALIDATION_ERRORMissing required field or invalid value
400INVALID_TEMPLATEtemplate_id not found
429RATE_LIMITEDPlan email quota reached
403PLAN_REQUIREDFeature requires LAUNCH plan or higher
500INTERNAL_ERRORRetry with exponential backoff

On this page