Skip to main content
POST
Delete application

Restrictions

Usage

  • Deletion is a soft delete: the application disappears from list, info and infos, and later calls with its ID fail (InvalidParameter, or ResourceNotFound for remote-config operations). There is no restore operation.
  • The application’s client_token stops being accepted by the data intake within about 5 minutes; data already collected is not removed.
  • The caller must be able to edit the application: the account owner, an account admin, the application’s creator, or a member of its owning team; anyone else gets AccessDenied.
  • Every call is recorded in the account audit log. Don’t put secrets in request fields.

Authorizations

app_key
string
query
required

APP Key created in the Flashduty console under My → APP Key. Send it as the app_key query parameter or in the Fd-App-Key request header. Its effective access is the intersection of the key's permission scope and the creator's current role permissions. Keep it secret.

Body

application/json

Request with a single application ID.

application_id
string
required

RUM application ID. Get application IDs via POST /rum/application/list.

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

No payload. Depending on the operation, data is {} or omitted from the envelope; rely only on the HTTP 200 status and the absence of error.