Skip to main content
POST
List remote config history

Restrictions

Usage

  • Only the 50 most recent versions are kept; older versions are deleted when a new one is published and can no longer be listed or reverted to.
  • Newest first by default (orderby=updated_at, asc=false). An unrecognized orderby falls back to updated_at; ties are broken by version.
  • content_hash and equivalent_to identify versions with identical content, e.g. a revert that restored an earlier version.

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

Remote configuration history request. Newest first by default.

application_id
string
required

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

asc
boolean

Ascending order. Default: false (descending).

limit
integer
default:20

Page size. 0 or a negative value means 20; values above 100 are treated as 100.

orderby
enum<string>
default:updated_at

Sort field:

  • updated_at: publish time (default).
  • version: version number.

Any other value falls back to updated_at.

Available options:
updated_at,
version
p
integer
default:0

Zero-based page index; offset is p multiplied by limit.

Required range: 0 <= x <= 100000

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

Remote configuration history page.