Bulk update endpoints
Updates details of a list of endpoints in bulk.
The request body must be an array of endpoint objects.
Each object requires an id field to identify the endpoint, and you only need to include the fields you want to update.
Unlike PATCH /api/v1/endpoint/{endpoint_id}, this bulk endpoint handles multiple endpoints safely in a single request without sequential execution constraints between individual endpoints.
Changing any of these fields resets the device’s connectivity: service_profile, tariff_profile, status, ip_address, ip_address_space, imei, imei_lock, or sim.
The network sends a Cancel Location, which ends the device’s active data session, and the device must reconnect.
Other fields, such as name, tags, and tag_assignments, don’t reset connectivity.
The reset happens only for endpoints whose values change. For example, an endpoint that already uses the target service policy doesn’t reset. Every changed endpoint in the request resets at the same time, so a bulk policy change can disconnect a whole fleet at once. If you assign a SIM that belongs to another device, that device’s connectivity resets too.
Execute bulk operations sequentially - wait for each bulk request to complete before starting the next.
emnify charges for activated SIMs, even if the endpoint status is set to Disabled.
To avoid accruing unexpected charges, update the SIM status to Suspended ("id": 2).
Authentication
An auth_token should be provided to authenticate a session.
To obtain an auth_token, see the /api/v1/authenticate POST request.
Request
IDs of existing tags replacing the tags currently assigned to the endpoint. An empty array removes all tags.
Mutually exclusive with tags. Provide at most one of the two.
Required when setting ip_address
Endpoint status: 0 (Enabled) or 1 (Disabled)