Skip to main content
POST
Update remote config

Restrictions

Usage

  • The client sends the complete object, not a patch: rule order is the priority, so a partial update has no unambiguous interpretation.
  • Each call allocates a new version and records a history row in the same transaction as the write.
  • Call POST /rum/application/remote-config/preview first to check what clients would receive.

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

Publish a whole new remote configuration version. The client sends the complete object, not a patch: rule order carries meaning.

application_id
string
required

RUM application ID.

config
object
required

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.

reason
string

Operator's note on why this version was published. Stored verbatim.

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 allocated to the published configuration.

request_id
string
required

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

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"