Skip to main content
DELETE
/
api
/
v1
/
users
/
{user_id}
curl -X DELETE "https://api.openwearables.com/api/v1/users/123e4567-e89b-12d3-a456-426614174000" \
  -H "Authorization: Bearer your_developer_token"
{
  "id": "123e4567-e89b-12d3-a456-426614174000",
  "created_at": "2024-01-15T10:30:00Z",
  "first_name": "John",
  "last_name": "Doe",
  "email": "[email protected]",
  "external_user_id": "ext_user_12345"
}

Authentication

This endpoint requires developer authentication. Developer credentials provide elevated privileges for deleting user data.
Deleting a user is a permanent action and cannot be undone. Ensure you have the correct user ID before proceeding.

Path Parameters

user_id
string
required
The unique UUID identifier of the user to delete

Response

Returns the deleted user object for confirmation.
id
string
UUID of the deleted user
created_at
string
ISO 8601 timestamp of when the user was originally created
first_name
string
User’s first name
last_name
string
User’s last name
email
string
User’s email address
external_user_id
string
External system identifier for the user
curl -X DELETE "https://api.openwearables.com/api/v1/users/123e4567-e89b-12d3-a456-426614174000" \
  -H "Authorization: Bearer your_developer_token"
{
  "id": "123e4567-e89b-12d3-a456-426614174000",
  "created_at": "2024-01-15T10:30:00Z",
  "first_name": "John",
  "last_name": "Doe",
  "email": "[email protected]",
  "external_user_id": "ext_user_12345"
}

Best Practices

1

Verify the User ID

Before deleting, retrieve the user with GET /api/v1/users/ to confirm you have the correct user.
2

Consider Data Dependencies

Check if the user has associated data (workouts, connections, etc.) that may also need to be handled.
3

Implement Confirmation

In your application, require user confirmation before calling this endpoint to prevent accidental deletions.
4

Log Deletion Events

Maintain audit logs of user deletions for compliance and troubleshooting purposes.

Build docs developers (and LLMs) love