Archive a contact
ProRead & write keyAvailable on the Pro and Enterprise plans (beta).
DELETEhttps://app.reshta.ir/api/v1/public…/public/contacts/{id}
Archives the contact; it can be restored in the app. The response is its ID and archived.
Request
curl https://app.reshta.ir/api/v1/public/contacts/0192c4e8-7b1a-7c3e-9f20-5d6a1b2c3d4e \ -X DELETE \ -H "Authorization: Bearer $RESHTA_API_KEY" \ -H "Idempotency-Key: 7f3c2b1e-4a5d-4c6f-9e1a-2b3c4d5e6f70"Headers
AuthorizationstringrequiredBearer followed by the business API key (rk_live_…).
Idempotency-KeystringrequiredA unique ID for this operation, such as a fresh UUID; retrying with the same key does nothing twice.
Path parameters
iduuidrequiredThe record ID (UUID).
Responses and errors
200—Done; the body is the record.
400validation_errorInvalid body, or no Idempotency-Key; details names the field.
401unauthorizedThe key is missing, wrong or revoked, or its creator is no longer active.
403forbiddenThe key has no write access.
404not_foundNo such record in this business.
409conflictThis Idempotency-Key came with another body, or is still in progress.
429rate_limitedOver 120 requests per minute; Retry-After says how many seconds to wait.
Response
400
{ "error": { "code": "validation_error", "message": "Idempotency-Key header is required", "details": [ { "field": "idempotency_key", "message": "idempotency_key_required" } ] }}