Upsert mapping data rows
Mapping data
Upsert mapping data rows
Insert or update up to 1000 data rows in a mapping schema. Each row must contain all source and result labels.
POST
Upsert mapping data rows
Restrictions
| Aspect | Value |
|---|---|
| Rate limits | 1,000 requests/minute; 50 requests/second per account |
| Permissions | Mappings Manage (on-call) |
Usage
- Each doc must contain values for all labels defined in
source_labelsandresult_labels. - Values for unknown labels are silently dropped.
- Each value must be at most 2048 characters.
- Upsert is keyed on the combination of source label values — existing rows with the same source key are updated.
- A schema can hold at most 10,000 rows by default.
- The operation is locked per schema; concurrent upserts to the same schema may fail with
ErrRequestTooFrequently.
Authorizations
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
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.