Getting startedAuthentication

Authentication

How to authenticate requests to the Imploy REST API with an access token.

Send the token

Add the token to every request in the Authorization header, using the Bearer scheme. The base URL is https://app.imploy.com.au/api/integrations/v1.

curl "https://app.imploy.com.au/api/integrations/v1/me" \
  -H "Authorization: Bearer imp_at_XXXX"

Check what the token can do

GET /me returns the connected organisation and the level for each area. Each area is read-write, read or none.

{
  "organisation": "example-organisation",
  "connection": "Example Client",
  "access": {
    "clients": "read-write",
    "staff": "read",
    "roster": "read",
    "sites": "read",
    "finance": "none",
    "forms": "none",
    "reports": "none",
    "prospects": "none"
  },
  "expires_at": "2026-01-01T00:00:00+00:00"
}

Requests

Filters go in the query string.

  • Lists can be comma separated (?refs=a:1,a:2) or repeated (?refs[]=a:1&refs[]=a:2).
  • Booleans are true or false.
  • Object values are sent as JSON text.

Responses

Responses are JSON, are sent with Cache-Control: no-store, and never include the token. Errors always include a message.

StatusMeaning
200OK. Also returned for deletes, and for dry runs.
201Created by a create endpoint.
400The body is not a JSON object
401The token is missing, invalid, disabled or expired
403The token does not have the permission this endpoint needs
404Unknown endpoint, or the record was not found
413Request body over 64 KB
422Validation failed, or the change is not allowed
429Rate limit reached
503Organisation integrations are turned off

See Limits and errors for the error format.