# Efficax OpenClaw API

Version: 0.1.0
Base URL: https://openclaw-staging.telescopeinspection.cloud/api/v1

## Integration rule

OpenClaw should use this API as the only write surface. The browser UI is read-only.

## Authentication

Use an HTTP Bearer token. Mutating requests also require:

- Idempotency-Key
- X-OpenClaw-Actor
- X-Human-Approval, only when the environment requires approval

## Recommended sequence

1. Read `/docs/manifest` and compare hashes.
2. Read `/openapi.json` if the hash changed.
3. Create an empty schedule with `POST /schedules`.
4. Add POs, containers, document references and evidence references.
5. Call `POST /schedules/{id}/validate`.
6. Patch the schedule status to `ready` only when validation has no missing fields.

## Document types

Use these document type values when possible:

- booking
- packing_list
- loading_plan
- signature_sheet

## Safety

Do not invent completed data. If information is missing, leave the field empty and rely on validation.missing.

## Browser-only smoke test

If your OpenClaw environment can read public URLs but cannot send headers or secrets, the normal authenticated API cannot be tested from that tool.

For staging-only connectivity tests, an operator can provide a limited smoke-test URL:

```http
GET /browser-smoke/create-cy?token=<limited_smoke_token>&actor=nix-openclaw&key=<unique_key>
```

This endpoint only creates a fixed CY demo schedule and is not a substitute for the authenticated API.