Releasesv0.1.0
Users

Hard-delete an end user

DELETE
/v1/users/{id}

The user's status becomes deleting at once: reads of their data return 404 and the user's tokens stop working, so uploads get 401 (410 only for an upload whose token was accepted just before). A background job then revokes provider connections (best effort), deletes the user's raw files and every row of the user, then the user. GET /v1/deletions/{job_id} tells when it is done.

Authorization

tenantKey
headerAuthorizationBearer <token>

Tenant API key, ohs_sk_ + 43 base62 characters.

Path Parameters

id*string
Formatuuid

Header Parameters

Authorization*string

The tenant API key, as a bearer secret.

Response Body

Deletion accepted.

application/json
  1. response
job_id*string
Formatuuid
curl -X DELETE 'http://localhost:8080/v1/users/497f6eca-6276-4993-bfeb-53cbbbba6f08' \  -H 'Authorization: Bearer ohs_sk_...'
{  "job_id": "453bd7d7-5355-4d6d-a38e-d9e7eb218c3f"}
Edit on GitHub