Get client invoice type details
const url = 'https://api2.recruso.co.uk/v1/reference/client-invoice-types/1';const options = {method: 'GET', 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 GET \ --url https://api2.recruso.co.uk/v1/reference/client-invoice-types/1 \ --header 'Authorization: <Authorization>'Returns one client invoice type by id. The client endpoints take this vocabulary by name rather than by id: clientInvoiceType on create and update a client is matched against these names, and an unrecognised name returns 400 listing the accepted values.
Client invoice types are platform-wide, so an id means the same client invoice type for every agency.
An id that does not match a client invoice type returns 404.
Access. Requires an authenticated token. No further policy is applied.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”The id path parameter
Responses
Section titled “Responses”OK
One client invoice type.
object
The client invoice type’s identifier. Stable and platform-wide — the same id means the same thing for every agency.
The client invoice type name, as it appears in Recruso. Up to 50 characters. Unique across all client invoice types.
Examplegenerated
{ "id": 1, "name": "example"}Unauthorized
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"}