Skip to contentDevelopersPrezly website
Press contacts

Delete Newsroom Contact

Delete a press contact after reviewing any story references.

Personal token scopes: sites:write. Your account must also have access to the requested data. Authentication

Successful deletion returns 204 with no JSON body. A used contact returns 409; the force parameter is enabled by its presence, even when supplied as force=false.

Read the guide

DELETE
/newsrooms/{newsroom_id}/contacts/{newsroom_contact_id}

Attempt to delete a Newsroom Contact.

Note:: The operation will fail with 409 Conflict response code if the contact is used in at leasy one story. However, you can pass ?force query parameter to override it and force the deletion. The contact will be removed from all stories it's used in.

Deleting a public newsroom press contact is separate from deleting a CRM contact. References in stories protect this entry from deletion. The presence of ?force bypasses the protection regardless of its value, including ?force=false.

Personal access tokens: sites:write. Every listed scope is required; the token owner's permissions, feature availability and newsroom access still apply.

Authorization

API_key
headerAuthorizationBearer <token>

Bearer authentication using an integration API key, or a personal access token only where the operation explicitly supports it. Every listed personal-token scope is required; owner permissions and newsroom access still apply.

Path Parameters

newsroom_contact_id*string

Newsroom Contact UUID or ID

Length1 <= length
newsroom_id*string

Newsroom UUID or ID

Length1 <= length

Query Parameters

force?string

Presence forces deletion even when stories reference this contact.

Response Body

Press contact deleted; empty response.

Example Request
curl -X DELETE 'https://api.prezly.com/v2/newsrooms/string/contacts/string'
Example Response
Empty