Skip to main content
POST
Revert remote config

Restrictions

Usage

  • History is never rewritten: the revert publishes the earlier version’s content under a NEW version number.
  • An empty reason is filled in by the console as rolled back to vN.

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

Republish an earlier version's content under a new version number.

application_id
string
required

RUM application ID.

version
integer
required

History version to republish.

Required range: x >= 1
reason
string

Operator's note. The console fills in rolled back to vN when left empty.

Maximum string length: 255

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.

data
object
required

Version created by the revert.

request_id
string
required

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

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"