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, which is returned.
  • version must still be in the retained history (the 50 most recent versions); otherwise the call returns InvalidParameter (version not found).
  • The restored content is validated against the current rules again and is rejected with InvalidParameter if it no longer passes.
  • The server does not generate a reason; an omitted reason is stored as an empty string.
  • 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

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

application_id
string
required

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

version
integer
required

Version to restore. Must be one of the retained versions listed by POST /rum/application/remote-config/history/list.

Required range: x >= 1
reason
string

Optional free-text note (not an enum), at most 255 characters, stored verbatim and returned as reason by POST /rum/application/remote-config/history/list. The server does not fill it in when omitted.

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.

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

Version created by the revert.