getAgentIntegration
GET/agents/:agentId/integrations/:integrationId
Requires agents:read. Deterministic stored configuration only; no worker/network/provider reachability evidence. New mutations require API_CONFIGURATION_ENABLED, Idempotency-Key and (except schedule creation) an exact If-Match ETag. Current authority precedes retained replay; matching replay returns the original outcome before testing its historical conditional revision. Disable/delete do not cancel an admitted occurrence. Setup controls require a member-issued key; service credentials may only use explicitly granted named schedules.
Request
Responses
- 200
- 400
- 403
- 404
- 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.
Exact resource/configuration revision for If-Match. Replayed ETags describe the original outcome.
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.
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.