Update mapping API
Update configuration of an existing mapping API.
Restrictions
| Aspect | Value |
|---|---|
| Rate limits | 1,000 requests/minute; 50 requests/second per account |
| Permissions | Mappings Manage (on-call) |
Usage
- Only the API creator, account admin, or team member can update the API.
- All updatable fields are optional — only provided fields are changed.
- Every call is recorded in the account audit log. Don’t put secrets in request fields.
Authorizations
App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.
Body
Mapping API ID (MongoDB ObjectID hex).
New API name (max 199 chars).
199New description.
New endpoint URL (max 500 chars).
500New TLS skip-verify setting.
New headers map (replaces existing).
New timeout in seconds.
New retry count.
New owning team ID.
Response
Success
Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.