Skip to main content
POST
Preview remote config

Restrictions

Usage

  • Runs the same matcher as the engine, so the result matches what production clients receive.
  • Omit config to preview the currently live configuration.

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

Preview request. Omit config to preview the currently live configuration.

application_id
string
required

RUM application ID.

app_version
string

App version the simulated client reports.

config
object

The whole per-application remote configuration. A change reaches an SDK asynchronously and is applied when that SDK creates its next session, so a running session never flips a decision mid-flight.

env
string

Environment the simulated client reports.

sdk
string

SDK name and version the simulated client reports, e.g. web@2.4.1.

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

Values the simulated client would receive.

request_id
string
required

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

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"