Manage stream API keys
You will learn how to create, copy, and revoke stream ingest API keys.
Stream API keys (lax_…) authenticate ingest only. They cannot query or
manage the app. Session JWTs and personal access tokens cannot ingest.
Create a key
- Select the target stream in the sidebar.
- Open Streams.
- Under API keys, click New API key.
- Enter a Name (for example
do-app-platformorlocal-curl). - Click Create key.
- Copy the secret from Save this API key — it is shown only once.
Also copy the ready-made curl sample when present; it already includes your API host, stream id, and key.
Use the key
| Path | How to send the key |
|---|---|
| Native HTTP JSON | Header X-API-Key: lax_… |
| Native HTTP plain text | Header X-API-Key: lax_… on /ingest/text |
OpenSearch-compatible _bulk |
HTTP Basic — username ignored; password = API key |
| OTLP Logs | X-API-Key or Authorization: Bearer lax_… |
Native first-run example:
curl -sS -X POST "$CORDO_API/v1/streams/$STREAM_ID/ingest" \
-H "Content-Type: application/json" \
-H "X-API-Key: $KEY" \
-d '{"level":"info","msg":"hello from curl"}'
Full method guides: Ingest your logs.
List and revoke
The API keys table shows Name, Prefix, Created, Last used, and Status (Active / Revoked).
To revoke:
- Click Revoke on an active key.
- Confirm. Ingest with that secret stops immediately.
You cannot recover a revoked secret — create a new key and update shippers.
Next
- Retention: Configure retention
- Ship logs: Ingest your logs
- Return to Workflows