Skip to main content
Sending a DELETE request to /nodes/{id} permanently terminates the specified compute node and halts per-second billing at that exact moment. The node transitions to a deleting status as it is torn down, and all data stored on it is wiped. Because this action is irreversible, make sure you have saved any work you need before calling this endpoint.

Endpoint

Path Parameters

string
required
The unique node ID you want to delete. This is the id value returned when you created the node. Example: node_abc123

Request Example

Response

A successful deletion returns HTTP 204 No Content with an empty response body. There is no JSON payload to parse — a 204 status code alone confirms the node has been scheduled for termination and billing has stopped.

Python SDK

The delete_node() method on the nodepick.ai client wraps this endpoint:
Deletion is permanent and immediate — all data stored on the node is lost the moment it is terminated. There is no recovery option. Billing stops at the exact moment of deletion, so always delete nodes as soon as you are finished with them.

Guaranteed Cleanup with try/finally

When you provision nodes programmatically, use a try/finally block to ensure every node you create is deleted even if your script raises an exception partway through:
This pattern guarantees that your cleanup logic runs regardless of whether the main body of your script succeeds or fails, preventing orphaned nodes from accruing unexpected charges.

Error Responses