Every workspace has an API. Send a task with your key and a person confirms receipt within one business day.
openapi.json
OpenAPI 3.1 — the same document the contract pipeline
audits and the SDKs are generated from.
Authentication
Your key was issued in the email titled Your harness access is ready. It looks
like ach_0000000000000000000000000000000000000000 and is stored only as a hash, so
it cannot be re-sent — keep it somewhere safe.
Present it in either header:
Authorization: Bearer ach_…
X-API-Key: ach_…
Treat the key as the workspace: anyone with it can submit tasks and read them. If it leaks, reply to your access email and we rotate it.
Base URL
https://www.5kingsmarketing.com/wp-json/harness/v1
Endpoints
| Method | Path | What it does |
|---|---|---|
GET | /me | Workspace, SKU, status and task counts |
POST | /tasks | Submit a task |
GET | /tasks | List your tasks (latest first) |
GET | /tasks/{id} | One task and its status |
Submit a task
curl -X POST https://www.5kingsmarketing.com/wp-json/harness/v1/tasks \
-H "Authorization: Bearer $HARNESS_KEY" \
-H "Content-Type: application/json" \
-d '{
"task": "Our Shopify collection pages duplicate the product title in the H1. Diagnose and fix.",
"store_url": "https://example-store.com",
"platform": "shopify"
}'
Response:
{
"id": 41,
"status": "received",
"workspace": "ws_3aa621170bf5",
"message": "Received. A person confirms it within one business day."
}
From JavaScript:
await fetch("https://www.5kingsmarketing.com/wp-json/harness/v1/tasks", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.HARNESS_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({ task, store_url, platform })
});
Task statuses
| Status | Meaning |
|---|---|
received | Recorded. Nobody has looked at it yet. |
acknowledged | Confirmed by a person, within one business day. |
in_progress | Being worked on. |
done | Delivered, with the evidence in the delivery record. |
Errors
| Code | HTTP | Cause |
|---|---|---|
ach_missing_key | 401 | No key in the request |
ach_invalid_key | 401 | Key not recognised |
ach_key_not_active | 403 | Request exists but is not provisioned |
ach_task_too_short | 422 | Under 10 characters |
ach_task_too_long | 422 | Over 8,000 characters |
ach_rate_limited | 429 | Over 30 submissions or 600 reads per hour |
ach_task_not_found | 404 | No such task in this workspace |
Limits and what happens next
- 30 task submissions per hour per key, 600 reads per hour.
- A task is not executed automatically. A person reads it, confirms within one business day, and the work follows the Integrity Standard — scope in writing, smallest correct change, verified after.
- Turnaround for the work itself is in the SLA.
- Need something urgent? Reply to your access email and say so; the API has no priority flag on purpose, because priority is a conversation, not a parameter.
Using the browser UI instead
If you bought Workspace UI access, you can work in the browser instead of the API — same workspace, same tasks. The UI link was in your access email.