Delete an endpoint | emnify Documentation

Deletes an endpoint and all its child entities. <Note> Execute this operation sequentially - wait for each request to complete before starting the next. For bulk deletions, use [`DELETE /api/v2/endpoint/multi`](/developers/api/endpoint/bulk-delete-endpoint) instead (supports up to 2,000 endpoints). </Note> <Info> Endpoints with an assigned SIM cannot be deleted (results in a `409` error). </Info>

Deletes an endpoint and all its child entities.

Execute this operation sequentially - wait for each request to complete before starting the next.

For bulk deletions, use DELETE /api/v2/endpoint/multi instead (supports up to 2,000 endpoints).

Endpoints with an assigned SIM cannot be deleted (results in a 409 error).

Authentication

AuthorizationBearer

An auth_token should be provided to authenticate a session.

To obtain an auth_token, see the /api/v1/authenticate POST request.

Path parameters

endpoint_idstringRequired

Response

Endpoints deleted successfully. The response payload body should be empty.

Errors

400

Bad Request Error

404

Not Found Error

409

Conflict Error

Deletes an endpoint and all its child entities.

Execute this operation sequentially - wait for each request to complete before starting the next.

For bulk deletions, use DELETE /api/v2/endpoint/multi instead (supports up to 2,000 endpoints).

Endpoints with an assigned SIM cannot be deleted (results in a 409 error).

An auth_token should be provided to authenticate a session.

To obtain an auth_token, see the /api/v1/authenticate POST request.

Endpoints deleted successfully. The response payload body should be empty.

$	curl -X DELETE https://cdn.emnify.net/api/v1/endpoint/endpoint_id \
>	-H "Authorization: Bearer <token>"