Skip to main content
POST
List mapping data

Restrictions

Usage

  • If query is provided, all source labels must be specified — partial source label queries are rejected.
  • Pagination uses cursor-based (search_after_ctx) or page-based (p, limit) navigation. limit defaults to 20, max 100.
  • The search_after_ctx token from a response can be passed back to retrieve the next page.

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
schema_id
string
required

Mapping schema ID (MongoDB ObjectID hex).

query
object

Exact-match filter on source label values. All source labels must be provided if any are specified.

orderby
enum<string>

Sort field.

Available options:
created_at,
updated_at
asc
boolean

Sort ascending when true.

p
integer<int64>

Page number (1-based). Used for offset-based pagination.

limit
integer<int64>

Page size (1–100, default 20).

search_after_ctx
string

Opaque cursor token for cursor-based pagination.

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
required

Endpoint-specific payload. See each operation's 200 response schema.