https://api.produktly.com/api/v1

All endpoints (except GET /openapi.json) require an API key passed as a Bearer token.

1. Sign in to Produktly and open Settings → API keys.
2. Generate a new key and copy it. The same key works for both REST and MCP.
3. Send it on every request:

GET /api/v1/changelogs HTTP/1.1
Host: api.produktly.com
Authorization: Bearer <your-api-key>

Missing or invalid keys return 401 unauthorized. Treat the key like a password — anyone with it can read and write your Produktly data.

List endpoints return an envelope with a data array and pagination metadata:

{
  "data": [ { "id": 1, "name": "..." } ],
  "pagination": { "total": 42, "limit": 50, "offset": 0 }
}

Single-resource endpoints (e.g. GET /roadmaps/{id}) return the resource directly, no envelope.

List endpoints accept limit (default 50, max 100) and offset (default 0) query parameters. Date filters (startDate, endDate) compose with pagination where supported.

Errors come back in a consistent shape:

{
  "error": {
    "code": "invalid_tag_names",
    "message": "Unknown tag names: foo. Use GET /v1/tags to see available tags.",
    "details": { "missing": ["foo"] }
  }
}

Common codes:

• unauthorized (401) — missing or invalid API key
• not_found (404) — resource doesn't exist or doesn't belong to your company
• validation_error (400) — invalid request parameters
• rate_limit_exceeded (429) — see Rate limits below
• internal_error (500) — server-side problem; safe to retry

Every API key is limited to 60 requests per minute. The /users endpoints have a separate bucket of 300 requests per minute to support backend syncs. Every response includes:

• X-RateLimit-Limit: total allowed in the window
• X-RateLimit-Remaining: remaining quota
• X-RateLimit-Reset: Unix seconds when the bucket refills

When you exceed the limit you'll get 429 rate_limit_exceeded with a Retry-After header. Back off and retry.