Public API

Base URL

https://www.calendarpa.com/api/v1

All endpoints are served over HTTPS. HTTP requests are automatically upgraded.

Authentication

CalendarPA uses the OAuth 2.0 Authorization Code flow. After authorization, include the access token as a Bearer token in every request:

Authorization: Bearer cpa_at_...

OAuth 2.0 Flow

1. Authorize— Redirect the user to /oauth/authorize with your client_id, redirect_uri, response_type=code, and scope.
2. Exchange— POST the authorization code to /api/oauth/token with grant_type=authorization_code.
3. Refresh— When the access token expires, POST to /api/oauth/token with grant_type=refresh_token.
4. Revoke— POST to /api/oauth/revoke to revoke a token pair.

Scopes

Endpoints

Account

Bookings

Booking Types

Contacts

Webhooks

Common Parameters

Create Booking

POST /v1/bookings

Example Request

curl -X POST https://www.calendarpa.com/api/v1/bookings \
  -H "Authorization: Bearer cpa_at_..." \
  -H "Content-Type: application/json" \
  -d '{
    "event_type_id": "et_xyz789",
    "start_time": "2026-03-15T10:00:00Z",
    "invitee_name": "Jane Smith",
    "invitee_email": "jane@example.com",
    "invitee_timezone": "America/New_York"
  }'

Webhook Events

Subscribe to real-time notifications when events occur in your CalendarPA account. Create subscriptions via POST /v1/hooks.

Webhook Signing

Every webhook delivery includes an HMAC-SHA256 signature for verification:

Rate Limits

Rate-limited requests return 429 Too Many Requests. Maximum 25 active webhook subscriptions per account.

Error Responses

All errors return a JSON body with an error field:

{
  "error": "Unauthorized",
  "code": "INVALID_TOKEN"
}

Third-Party Integrations

CalendarPA integrates with popular automation platforms out of the box:

Need Help?

If you have questions about the API or need help with your integration, contact our support team at [email protected]