Delete a site contact
const url = 'https://api2.recruso.co.uk/v1/clients/1/sites/1/contact-persons/1';const options = {method: 'DELETE', headers: {Authorization: '<Authorization>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request DELETE \ --url https://api2.recruso.co.uk/v1/clients/1/sites/1/contact-persons/1 \ --header 'Authorization: <Authorization>'Deletes one contact person from one of your own agency’s sites. This is a soft delete: the row is retained with its activities and cost-centre links, and RestoreSiteContactPerson can bring it back.
A deleted contact disappears from ListSiteContactPersons and from GetSiteContactPersonById, which returns 404 for it. Restore is the only way to read it again, so record the contactPersonId before deleting.
Contact names are not reserved — another contact can immediately take the same name.
The site must belong to the client named in the route, and the contact to that site; otherwise 404. Deleting an already-deleted contact also returns 404.
Access. Requires a client-credentials access token. Tokens issued through the interactive user login are rejected.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”The clientId path parameter
The siteId path parameter
The id path parameter
Responses
Section titled “Responses”No Content
Unauthorized
object
Examplegenerated
{ "type": "example", "title": "example", "status": 1, "detail": "example", "instance": "example"}Forbidden
object
Examplegenerated
{ "type": "example", "title": "example", "status": 1, "detail": "example", "instance": "example"}Not Found
object
Examplegenerated
{ "type": "example", "title": "example", "status": 1, "detail": "example", "instance": "example"}