REST API Overview
The Hype Doc REST API lets you create, read, update, and delete wins, spaces, and tags programmatically.
Base URL
Section titled “Base URL”https://app.myhypedoc.com/api/v1Authentication
Section titled “Authentication”All requests require a Bearer token in the Authorization header:
GET /api/v1/wins HTTP/1.1Host: app.myhypedoc.comAuthorization: Bearer hdoc_xxxxxxxxxxxxxxxxxxxxContent-Type: application/jsonGenerate tokens in Settings → API Tokens. See Authentication for details.
Request format
Section titled “Request format”Send JSON with Content-Type: application/json. All request bodies use a root key matching the resource name:
{ "win": { "body": "Shipped the feature", "space_id": 1 }}Response format
Section titled “Response format”All responses return JSON. Successful responses return the resource directly (or an array for list endpoints). Error responses return an error key:
{ "error": "Not found"}Pagination
Section titled “Pagination”List endpoints support pagination via query parameters:
| Parameter | Default | Range | Description |
|---|---|---|---|
page | 1 | 1+ | Page number |
per_page | 25 | 1–100 | Items per page |
Pagination metadata is returned in response headers:
| Header | Description |
|---|---|
X-Total-Count | Total number of records |
X-Page | Current page number |
X-Per-Page | Items per page |
See Pagination for more details.
Rate limiting
Section titled “Rate limiting”Every response includes rate limit headers:
| Header | Description |
|---|---|
X-RateLimit-Limit | Max requests per window |
X-RateLimit-Remaining | Requests remaining |
X-RateLimit-Reset | Unix timestamp when the window resets |
See Rate Limits for limits per endpoint.
Caching
Section titled “Caching”All API responses include:
Cache-Control: private, no-storeVary: Authorization, AcceptAPI responses are never cached by intermediaries.