> ## Documentation Index
> Fetch the complete documentation index at: https://docs.praxa.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Admit a minimal durable task

> Admit a durable Praxa task with a personal workspace API key, then verify the returned run through readback or reconnectable events.

Admit a durable Praxa task with a personal workspace API key, then verify the returned run through readback or reconnectable events.

<Info>
  **Availability:** Production partner preview. **Required scope:** `execute:write`.
</Info>

## Authenticate safely

Create a disposable **personal workspace** API key with exactly `execute:write`. Send it as `Authorization: Bearer $PRAXA_API_KEY`. A Gateway OAuth token, Supabase JWT, provider credential, or organization memory key is not interchangeable with this key.

The hosted playground sends the credential from your browser session to the documented API through the configured playground proxy. Use test data, never share the key, and revoke it when the check ends.

## Request fields

<ParamField header="Idempotency-Key" type="string">
  Must equal the body idempotencyKey when both are present. The effective key is header, body, then requestId.
</ParamField>

<ParamField header="X-AI-Platform-Version" type="v1">
  X-AI-Platform-Version header parameter.
</ParamField>

<ParamField body="apiVersion" type="v1" required>
  apiVersion request field.
</ParamField>

<ParamField body="requestId" type="string" required>
  requestId request field.
</ParamField>

<ParamField body="mode" type="task" required>
  mode request field.
</ParamField>

<ParamField body="task.input" type="string" required>
  task.input request field.
</ParamField>

<ParamField body="idempotencyKey" type="string">
  idempotencyKey request field.
</ParamField>

## Runnable request examples

<CodeGroup>
  ```bash cURL theme={null}
  curl --fail-with-body -X POST 'https://api.praxa.io/v1/execute' \
    -H "Authorization: Bearer $PRAXA_API_KEY" \
    -H "Idempotency-Key: tutorial-task-2026-08-13" \
    -H "X-AI-Platform-Version: v1" \
    -H "Content-Type: application/json" \
    --data '{
    "apiVersion": "v1",
    "requestId": "tutorial-task-2026-08-13",
    "mode": "task",
    "task": {
      "input": "Summarize the incident and propose the next safe action."
    },
    "idempotencyKey": "tutorial-task-2026-08-13"
  }'
  ```

  ```javascript Node.js theme={null}
  const response = await fetch("https://api.praxa.io/v1/execute", {
    "method": "POST",
    "headers": {
      "Authorization": `Bearer ${process.env.PRAXA_API_KEY}`,
      "Idempotency-Key": "tutorial-task-2026-08-13",
      "X-AI-Platform-Version": "v1",
      "Content-Type": "application/json"
    },
    "body": JSON.stringify({
      "apiVersion": "v1",
      "requestId": "tutorial-task-2026-08-13",
      "mode": "task",
      "task": {
        "input": "Summarize the incident and propose the next safe action."
      },
      "idempotencyKey": "tutorial-task-2026-08-13"
    })
  });
  const text = await response.text();
  if (!response.ok) throw new Error(`${response.status}: ${text}`);
  console.log(text ? JSON.parse(text) : { status: response.status });
  ```

  ```python Python theme={null}
  import json
  import os
  from urllib import error, request

  payload = json.dumps({
    "apiVersion": "v1",
    "requestId": "tutorial-task-2026-08-13",
    "mode": "task",
    "task": {
      "input": "Summarize the incident and propose the next safe action."
    },
    "idempotencyKey": "tutorial-task-2026-08-13"
  }).encode()

  req = request.Request(
      "https://api.praxa.io/v1/execute",
      method="POST",
      headers={
        "Authorization": f"Bearer {os.environ['PRAXA_API_KEY']}",
        "Idempotency-Key": "tutorial-task-2026-08-13",
        "X-AI-Platform-Version": "v1",
        "Content-Type": "application/json"
      },
      data=payload,
  )
  try:
      with request.urlopen(req, timeout=30) as response:
          text = response.read().decode()
          print(json.loads(text) if text else {"status": response.status})
  except error.HTTPError as exc:
      raise RuntimeError(f"{exc.code}: {exc.read().decode()}") from exc
  ```
</CodeGroup>

## What success means

A `202` response proves durable admission or an exact idempotent replay. It does not prove that the task completed.

## Successful response

**202** — Durable task admitted or exact idempotent replay returned.

<ResponseField name="apiVersion" type="v1" required>
  apiVersion response field.
</ResponseField>

<ResponseField name="run_id" type="string" required>
  run\_id response field.
</ResponseField>

<ResponseField name="requestId" type="string" required>
  requestId response field.
</ResponseField>

<ResponseField name="mode" type="task" required>
  mode response field.
</ResponseField>

<ResponseField name="status" type="queued | running | awaiting_approval | completed | failed | cancelled" required>
  Public lifecycle status. Internal cancelling and reconcile\_required states project as running; reconciliation is not terminal.
</ResponseField>

<ResponseField name="createdAt" type="string" required>
  createdAt response field.
</ResponseField>

<ResponseField name="updatedAt" type="string" required>
  updatedAt response field.
</ResponseField>

<ResponseField name="completedAt" type="string">
  completedAt response field.
</ResponseField>

<ResponseField name="pendingApproval" type="object">
  Present only when Praxa can derive the exact recorded browser action and bind it to the stored action digest. The summary contains the exact recorded instruction or steps followed by the target host.
</ResponseField>

<ResponseField name="result" type="object">
  Present only for schema-valid, digest-matched verified text.
</ResponseField>

<ResponseField name="failure" type="object">
  failure response field.
</ResponseField>

<ResponseField name="links" type="object" required>
  links response field.
</ResponseField>

<ResponseExample>
  ```json 202 theme={null}
  {
    "apiVersion": "v1",
    "run_id": "018f0000-0000-7000-8000-000000000001",
    "requestId": "request-id-demo-0001",
    "mode": "task",
    "status": "queued",
    "createdAt": "2026-08-13T12:00:00.000Z",
    "updatedAt": "2026-08-13T12:00:00.000Z",
    "links": {
      "self": "/v1/runs/018f0000-0000-7000-8000-000000000001",
      "events": "/v1/runs/018f0000-0000-7000-8000-000000000001/events"
    }
  }
  ```
</ResponseExample>

## Handle failures

| Response                    | Meaning                                                                    | Safe action                                                                         |
| --------------------------- | -------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- |
| `400 invalid_request`       | The method, path, headers, query, or body failed strict validation.        | Correct the request; do not retry unchanged input.                                  |
| `401 authentication_failed` | The bearer key is missing, malformed, expired, or revoked.                 | Stop and replace the key through the authenticated console.                         |
| `403 authorization_failed`  | The authenticated key lacks scope or tenant authority.                     | Request only the missing least-privilege scope; never substitute another tenant ID. |
| `409 conflict`              | The same idempotency key was paired with different logical input or state. | Restore the original body or create a key for a genuinely new operation.            |
| `429 rate_limited`          | The principal exceeded a bounded rate.                                     | Honor `retryAfterMs` or `Retry-After`, add jitter, and cap attempts.                |
| retryable `5xx`             | The server could not confirm a final response.                             | Reconcile reads or replay the exact keyed mutation before creating new work.        |

```json Example problem theme={null}
{
  "type": "https://docs.praxa.io/problems/authorization-failed",
  "title": "Authorization failed",
  "status": 403,
  "code": "authorization_failed",
  "detail": "The API key does not grant the required scope.",
  "retryable": false
}
```

## Verify the result

1. Save `run_id` and `Location`.
2. Read the run or consume events until a terminal state.
3. Replay the exact request with the same key and require the same logical run.

## Retry, cleanup, and production use

* Treat `401`, `403`, and `409` as authority or state signals, not generic retry prompts.
* Reuse the idempotency key only for an exact retry of the same logical mutation.
* For `429` or retryable 5xx responses, follow server retry guidance and keep a bounded attempt budget.
* Move the request into a trusted application backend before production; never ship the Praxa key in browser or mobile code.
* Revoke the disposable key, disable test webhooks, and erase disposable candidate data after validation.

Continue with [API authentication](/api-playground/authentication), the [failure and retry guide](/api-playground/errors), and the [end-to-end coverage matrix](/api-playground/coverage-and-testing).