Manage Endpoints
/endpoints-manageAtomically merges endpoints and their references. Every operation names the source and target starting etags. All operations use the versions at the start of the batch; each affected endpoint advances once at commit. If any operation fails, all operations roll back. Responses are retained for 24 hours.
Required scope
endpoint:writeHeader parameters
- Idempotency-Key
stringRequired Client-chosen key that makes a non-idempotent request retry-safe, following draft-ietf-httpapi-idempotency-key-header. A committed response is stored for 24 hours and replayed for the same principal, operation, key and payload. Missing key returns 400 IDEMPOTENCY_KEY_REQUIRED, a key longer than 255 characters returns 400 IDEMPOTENCY_KEY_INVALID, the same key with a different payload returns 422, and the same key while the first request is still in flight returns 409. Requests rolled back before external provider attempts do not consume the key. Group mutations retain terminal failed responses after provider attempts together with received provider truth; their operation contract defines these replayable outcomes.
minLength: 1
maxLength: 255
Request body
Fields
EndpointsManageRequestReturns
200
Per-operation results and errors. Any error means no changes committed.
Fields
EndpointsManageResponseErrors
400 IDEMPOTENCY_KEY_REQUIREDInvalid request or missing Idempotency-Key.
Check the request fields and any validation details, then correct the payload.
409 IDEMPOTENCY_KEY_IN_FLIGHTIdempotency key in flight.
Check the device’s current mode or state. Retry only after the conflict is resolved.
422 IDEMPOTENCY_KEY_REUSEDIdempotency key payload conflict.
Correct the rejected value using the constraints in the error details or request schema.