Update A2A agent
Edit an A2A agent’s card URL, auth, streaming flag, or owning team.
Restrictions
| Aspect | Value |
|---|---|
| Rate limits | 1,000 requests/minute; 50 requests/second per account |
| Permissions | None — any valid app_key can call this operation |
Usage
- Omit a field to leave it unchanged; only fields present in the request are updated.
- Every call is recorded in the account’s audit log.
Authorizations
App key issued from the Flashduty console under Account → APP Keys. Required on every public API call.
Body
Editable fields of an A2A agent; omitted fields are left unchanged.
Identifier of the agent to update.
New display name.
128New description.
New agent card URL.
New authentication scheme.
New authentication parameters.
Toggle streaming-response support.
Reassign the agent to this team; omit to leave unchanged, 0 for account scope.
New credential model.
New per-user secret JSON schema.
New OAuth metadata JSON.
Response
Success
Standard response envelope used by every Flashduty public API. On success data contains the endpoint-specific payload and error is absent. On failure error is present and data is absent. request_id is always present and is also mirrored in the Flashcat-Request-Id response header.
Unique ID for this request. Mirrored in the Flashcat-Request-Id header. Include it when reporting issues.
"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"
Error payload inside the response envelope. Present only on non-2xx responses.
No payload; the operation returns an empty data field on success.