Skip to main content

Analytics API Overview

The Chippy Analytics API lets you collect events, identify users, and monitor app usage programmatically. Use it to send custom events from your backend, associate user traits for segmentation, and verify service health.

Base URL

All API requests are made to:

Authentication

Authenticate every request with a Bearer token in the Authorization header. API keys are managed in the Chippy dashboard under your organization settings.
API keys beginning with ak_live_ are production keys. Keep them secret and never expose them in client-side code.

Example authenticated request

Rate Limits

Each endpoint enforces its own rate limit per API key. Every response includes rate limit headers so you can track your usage:
If you hit a rate limit, back off and retry after the X-RateLimit-Reset timestamp. Batch endpoints are the most efficient way to send high volumes of events.

HTTP Status Codes

Error Response Format

All errors return a JSON object with an error field describing what went wrong.

Example error responses

400 Bad Request: missing a required field:
401 Unauthorized: invalid API key:
429 Too Many Requests: rate limit exceeded:

API Endpoints

Send Events

Track user actions and app behavior with single, batch, or SDK-friendly event endpoints.

Identify Users

Associate traits and properties with users for segmentation and analysis.

Health Check

Monitor analytics service status and component health.