Monitors

Add trackers to monitor

Moves the account's trackers into this monitor by id ({ tracker_ids: ["trk_..."] }), out of the monitors they are in. A tracker always sits in one monitor and alerts through its delivery settings. It does not create trackers: POST /v1/monitors/{id}/entities does. Supply 1 to 90 IDs. Duplicate IDs count once. Every ID must belong to the account; a missing or foreign ID returns tracker_not_found and none move. attached_count reports the unique moved count.

post/v1/monitors/{id}/trackers

Request

Base URL: https://api.arcmira.com
URL: https://api.arcmira.com/v1/monitors/{id}/trackers
Auth: HTTP bearer

Path parameters

idstring required

Monitor id.

Headers

Idempotency-Keystring

One key per intent, 1 to 255 printable ASCII characters (0x21 to 0x7E); anything else is 400 invalid_idempotency_key. Keys are scoped to the account, credential and resource family. The same key and normalized method, path and body returns the committed response with Idempotency-Replayed: true. A changed intent within the same family returns 409 idempotency_conflict. Monitor and tracker families have independent namespaces. Secret recovery is limited as described by the operation.

Request body

tracker_idsstring[] required

Ids of the account's trackers ("trk_...") to move into this monitor from the monitors they are in. At most 90 IDs per request; duplicates count once. All IDs must belong to the account or none move.

Response

Success

attached_countinteger required

Number of unique requested trackers attached.

messagestring required

Human-readable confirmation, e.g. "Added 3 tracker(s) to monitor".

monitor_idstring required

The monitor id from the request path.

Changes

No recorded changes to this operation across all 1 revision of this API.