Skip to Content
API ReferenceOverview

API Reference

Chirpier exposes two public HTTP surfaces:

  • logs APIs for event logging
  • control-plane APIs for reading and managing resources

Authentication

Send:

Authorization: Bearer <token>

The same bearer token works for both logs and control-plane APIs.

Base URLs

  • Logs: https://logs.chirpier.co
  • Resources: use your Chirpier app or API host for /v1.0/events, /v1.0/policies, /v1.0/alerts, and /v1.0/destinations

Error shape

Most validation failures return a JSON body like:

{
  "error": "invalid eventID"
}

Unauthorized requests return 401 when the bearer token is missing or invalid.

API families

Logs API
Write flat numeric events to Chirpier through `POST /v1.0/logs`.
Events API
Read and update event definitions, then inspect rollups for minute, hour, and day history.
Policies and Alerts API
Create alert rules, read runtime alert state, inspect deliveries, and trigger lifecycle transitions.
Destinations API
Configure Slack, Discord, Telegram, email, and webhook delivery targets, then test them.
Analytics API
Read window comparisons using `view=window` and explicit `previous` values.
Schemas
See the shared request and response object shapes used across the public API.
Last updated on
DestinationsLogs API