API Reference

daymesh API

Build integrations with daymesh using our REST API. All endpoints require authentication via API token.

Base URL

https://daymesh.com/api/v1

Authentication

All API requests require a Bearer token in the Authorization header:

$ curl -H "Authorization: Bearer dm_your_token_here" \
  https://daymesh.com/api/v1/me

Creating a token

Go to Settings → API Access → Create Token. Give your token a descriptive name and copy it immediately — the full token is only shown once.

Token format

Tokens use the prefix dm_ followed by 32 hexadecimal characters. Example: dm_a8f3k2m9b4c7d1e0f5a6b3c8d2e9f0a1

Rate limits by plan

Plan	Requests per minute
Free	30
Pro ($5/mo)	120
Business ($15/mo)	300

User

Calendars

Feeds

Analytics

Tokens

Rate Limiting

Every API response includes rate limit headers so you can track your usage:

Header	Description
X-RateLimit-Limit	Maximum requests allowed per minute
X-RateLimit-Remaining	Requests remaining in the current window
X-RateLimit-Reset	Unix timestamp when the window resets

When you exceed your rate limit, the API returns a 429 Too Many Requests response:

HTTP/1.1 429 Too Many Requests
X-RateLimit-Limit: 30
X-RateLimit-Remaining: 0
X-RateLimit-Reset: 1711353660
Retry-After: 42

{
  "error": "rate limit exceeded, try again in 42 seconds"
}

Use the Retry-After header value to wait before retrying. Implementing exponential backoff is recommended for robust integrations.

Errors

All errors return a JSON object with an error key:

{
  "error": "calendar not found"
}

Status	Meaning
400	Bad Request — invalid or missing parameters
401	Unauthorized — missing or invalid API token
403	Forbidden — valid token but insufficient permissions (e.g. wrong plan)
404	Not Found — resource does not exist or does not belong to you
429	Too Many Requests — rate limit exceeded
500	Internal Server Error — something went wrong on our end

Get started

Ready to build with daymesh?

Create an API token and start integrating in minutes.

Go to Settings