Skip to main content
POST
/
enrichment
/
mapping
/
api
/
delete
Delete mapping API
curl --request POST \
  --url 'https://api.flashcat.cloud/enrichment/mapping/api/delete?app_key=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "api_id": "665f1a2b3c4d5e6f7a8b9c02"
}
'
{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {}
}

Documentation Index

Fetch the complete documentation index at: https://docs.flashcat.cloud/llms.txt

Use this file to discover all available pages before exploring further.

​
Restrictions

AspectValue
Rate limits1,000 requests/minute; 50 requests/second per account
PermissionsMappings Manage (on-call)

​
Usage

  • If the API is still referenced, the response returns HTTP 400 with a refs list.
  • Only the API creator, account admin, or team member can delete the API.
  • 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
​
api_id
string
required

Mapping API ID (MongoDB ObjectID hex).

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.

​
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.