Message Agent
POST/agents/:id/messages
Ingest a message from an allowed sender using a supported channel and agent endpoint. Email is a supported input. Returns 201 with the stored timeline event, not an agent reply or proof of processing. Inactive agents return 409; disallowed senders return 403. REST does not accept file attachments here. Requires agents:operate.
Request
Responses
- 201
- 400
- 403
- 404
- 409
- 429
- 500
- 503
Response Headers
Smaller configured principal/owner request window limit when enforcement is enabled.
Smaller remaining principal/owner allowance at admission.
Seconds until the Redis-server-time fixed request window resets.
Present when Idempotency-Key is used: false for the original response, true for a replay.
Opaque retained receipt ID. Outcome lookup is available for covered G02 member and allowed G01 service operations.
Original protected response expiry.
Server-generated synchronous HTTP correlation; no worker lineage implied.
Invalid request body or query parameters. Field errors may be returned as arrays.
Response Headers
Server-generated synchronous HTTP correlation; no worker lineage implied.
Missing/invalid API key, insufficient scope, account eligibility, or communication policy denial.
Response Headers
Server-generated synchronous HTTP correlation; no worker lineage implied.
Resource not found or not accessible to this API key.
Response Headers
Server-generated synchronous HTTP correlation; no worker lineage implied.
Response Headers
Server-generated synchronous HTTP correlation; no worker lineage implied.
request_quota_exceeded or wait_capacity_exceeded. Honor Retry-After; no new input was accepted.
Response Headers
Seconds until the suggested retry, not a readiness guarantee.
Server-generated synchronous HTTP correlation; no worker lineage implied.
Unexpected failure; JSON includes detail and an error_id for support.
Response Headers
Server-generated synchronous HTTP correlation; no worker lineage implied.
admission_unavailable or work_capacity_exceeded. Honor Retry-After and preserve protected-write keys.
Response Headers
Seconds until the suggested retry, not a readiness guarantee.
Server-generated synchronous HTTP correlation; no worker lineage implied.