Skip to main content
POST
List remote config history

Restrictions

Usage

  • Newest first by default (orderby=updated_at, asc=false).
  • content_hash and equivalent_to identify versions whose content is identical, so the console can say “this is an earlier version’s content” instead of showing a false difference.

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

Remote configuration history request. Newest first by default.

application_id
string
required

RUM application ID.

asc
boolean

Ascending order. Default: false (descending).

limit
integer
default:20

Page size. Default 20, max 100.

Required range: x <= 100
orderby
enum<string>
default:updated_at

Sort field. Default: 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.

data
object
required

Remote configuration history page.

request_id
string
required

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

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"