Update mapping schema

Update the name, description, or owning team of a mapping schema. Source and result labels cannot be changed after creation.

POST /enrichment/mapping/schema/update

Update mapping schema

cURL

curl --request POST \
  --url 'https://api.flashcat.cloud/enrichment/mapping/schema/update?app_key=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "schema_id": "665f1a2b3c4d5e6f7a8b9c01",
  "schema_name": "CMDB Lookup v2",
  "description": "Updated description"
}
'

200

{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {}
}

Restrictions

Aspect	Value
Rate limits	1,000 requests/minute; 50 requests/second per account
Permissions	Mappings Manage (on-call)

Usage

• Only the schema creator, account admin, or team member can update the schema.
• Every call is recorded in the account audit log. Don’t put secrets in request fields.

Authorizations

app_key · string · query · required

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

application/json

schema_id · string · required

Schema ID (MongoDB ObjectID hex).

schema_name · string | null

New schema name (max 39 chars).

Maximum string length: 39

description · string | null

New description (max 500 chars).

Maximum string length: 500

team_id · integer<int64> | null

New owning team ID. 0 removes the team association.

Response

200

application/json

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.

request_id · string · required

Unique ID for this request. Mirrored in the Flashcat-Request-Id response header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

data · object · required

Empty response body. The server returns data: null on success.