Developer-Focused API Docs (Markdown)

I need clear, comprehensive API documentation written in Markdown so developers can plug straight into our service with minimal back-and-forth. The draft should read like a concise reference: endpoints first, followed by parameters, authentication flow, request-response samples, error codes, and any rate-limit or pagination notes. Please mirror standard REST naming conventions and keep the tone factual and example-driven.

Deliverables
• A fully structured Markdown file (or small set of files) ready to drop into our docs repository.
• Curl or language-specific snippets for each endpoint.
• A quick “Getting Started” section that walks a new developer from token creation to their first successful call.
• Internal links, tables of contents, and code blocks formatted for GitHub-style Markdown.

Acceptance criteria
• Every public endpoint documented, no 404s or placeholders.
• Consistent parameter tables and response schemas.
• All examples tested against the live or staging API and shown to work.
• Lint-clean Markdown (no broken anchors, code fenced correctly).

Feel free to highlight any missing info you need—schema files, Postman collection, or test credentials—so I can supply them upfront and keep the writing cycle tight.