Machine-readable spec
Download the contract without an API key:| Format | URL |
|---|---|
| YAML | GET https://api.folkyn.com/api/v1/openapi.yaml |
| JSON | GET https://api.folkyn.com/api/v1/openapi.json |
Navigation
Use the API Reference tab for endpoints; the Guides tab has quickstart, authentication, errors, and rate limits. In the sidebar, each section (Overview, Specification, Project codes, Team tags, Teams, Missions, Freelancers, Activity reports, Accounting) is a top-level group. Under each resource group, operation titles follow List → Create → Retrieve → Update when those verbs apply (for example List Project Codes, Create Project Code, Retrieve Project Code). Exceptions stay explicit (Download OpenAPI specification, Mark Accounting Entry as Paid, Update Mission Enterprise Fields).Try requests
Some endpoint pages include Mintlify’s interactive Try it / playground (OpenAPI). When you use it:- Base URL — Send requests to
https://api.folkyn.comunless you intentionally target another environment (for example a local Next.js dev server). - Team API key — Use one auth method only (not both on the same request):
Authorization: Bearer— Paste the full key including thefk_live_prefix. If the UI has a separate Bearer or token field, put the key there and let the tool add theBearerprefix; avoid ending up withBearer Bearer ….X-Api-Key— Set this header to the same full key value (noBearerprefix).
- Complete path parameters, query fields, and JSON body as the operation requires, then run the request.
Related
- Quickstart — first successful call
- Errors —
errorobject and HTTP alignment - Rate limits — 60 requests/minute per key
