Skip to content
Recruso API

List receiving hours entries

GET
/v1/receiving-hours
curl --request GET \
  --url https://api2.recruso.co.uk/v1/receiving-hours \
  --header 'Authorization: <Authorization>'

Returns your agency’s receiving hours entries, ordered by receivingHoursName. A receiving hours entry is how a client prefers to receive its workers’ hours — a block timesheet, email, the portal, post, a text message, or from the workers themselves.

The response is not paged.

You only ever see and change your own agency’s records; there is no owner id on the request, and an id belonging to another agency returns 404 rather than 403 so that its existence is never disclosed.

Access. Requires a client-credentials access token. Tokens issued through the interactive user login are rejected.

Authorizations

Section titled “Authorizations”

Responses

Section titled “Responses”

200

Section titled “200”

OK

Media typeapplication/json
object
receivingHours
required
Array<object>
object
receivingHourId
required
integer format: int16
receivingHourName
required
string
Examplegenerated
{
  "receivingHours": [
    {
      "receivingHourId": 1,
      "receivingHourName": "example"
    }
  ]
}

401

Section titled “401”

Unauthorized

Media typeapplication/problem+json
object
type
string
nullable
title
string
nullable
status
integer format: int32
nullable
detail
string
nullable
instance
string
nullable
Examplegenerated
{
  "type": "example",
  "title": "example",
  "status": 1,
  "detail": "example",
  "instance": "example"
}

403

Section titled “403”

Forbidden

Media typeapplication/problem+json
object
type
string
nullable
title
string
nullable
status
integer format: int32
nullable
detail
string
nullable
instance
string
nullable
Examplegenerated
{
  "type": "example",
  "title": "example",
  "status": 1,
  "detail": "example",
  "instance": "example"
}