Delete a custom contact field
DELETE/api/v1/contact-fields/{id}
DELETE /contact-fields/{id}
curl -X DELETE 'https://www.unitpost.com/api/v1/contact-fields/cf_123' \
-H 'Authorization: Bearer YOUR_API_KEY' \
-H 'User-Agent: my-app/1.0'Response · 202
{
"object": "job",
"id": "id_123",
"kind": "string",
"status": "QUEUED",
"total": 1,
"processed": 0,
"failed": 0,
"error": "string",
"created_at": "2026-01-01T00:00:00.000Z",
"completed_at": "2026-01-01T00:00:00.000Z"
}Permanently delete a custom field definition and strip its stored value from every contact. Any template variable that referenced it will resolve to empty. On more than 5,000 contacts the strip runs as a background job and the response is 202 with the job's progress instead of 204. This can't be undone — recreate the field with Create a custom contact field if you need it back. Requires the contacts:write capability.
Parameters1 field
| Field | Type | Description |
|---|---|---|
idrequired | string · path | — |
Response · 202 fields10 fields
| Field | Type | Description |
|---|---|---|
objectrequired | string | — |
idrequired | string | — |
kindrequired | string | — |
statusrequired | enumQUEUED | RUNNING | COMPLETED | FAILED | CANCELED | — |
totalrequired | integer | null | — |
processedrequired | integer | — |
failedrequired | integer | — |
errorrequired | string | null | — |
created_atrequired | string | — |
completed_atrequired | string | null | — |
202204401404409