Overview
The Folkyn API (/api/v1) is for server-side integrations. Each request uses a team API key; all data is scoped to that team.
Rate limit: 60 requests/minute per key by default — see Rate limits. Individual keys may have a higher limit; check X-RateLimit-Limit on responses.
What your API key represents
An API key is a team-level service account with access equivalent to a team administrator for every operation documented under/api/v1.
- One key, one team — all requests are scoped to that team’s data.
- Not a personal login — the key does not impersonate the user who created it; it is a machine identity for integrations.
- Contract of record — the authoritative list of routes, fields, and behavior is the OpenAPI specification: https://api.folkyn.com/api/v1/openapi.yaml (JSON: openapi.json).
Accessible via the API
Not accessible via the API
Use the API Reference tab and the OpenAPI file above for the exact request and response shapes.
Prerequisites
- A team API key from Settings → Developer in the Folkyn app (see Authentication).
Base URL
Production:https://api.folkyn.com
For local testing, use the base URL of the environment you control (for example http://localhost:3000).
OpenAPI specification
Download the contract without an API key:
The API Reference tab on this site is generated from the same OpenAPI documents. Import either URL into Postman (Import → Link), Insomnia (Import Data → From URL), or your codegen tool; prefer JSON if YAML import fails.
First request
List project codes with the Authorization header:X-Api-Key instead of Bearer.
Success response
JSON responses wrap payloads indata:
Errors
On failure, the body includes anerror object; error.code is always the same integer as the HTTP status. See Errors for the full shape and common cases.
Next steps
- Authentication — headers, key handling
- Errors — error shape and codes
- Rate limits — default 60 requests/minute per key; see
X-RateLimit-Limitfor your key’s limit
