Skip to main content
GET
List employee-attributes
This API endpoint is in beta and may be subject to changes, including breaking changes (similarly to the legacy API endpoints), without prior notice. Read more about versioning.
OAuth 2.0 scopes
or

EstablishmentsThis API endpoint will filter out results based on accessible business-establishments.You may only access employee-attributes of employees whose applicable business-establishments are accessible to you.
ClaimsThis API endpoint will filter out results based on accessible claims.Each employee-attribute is associated with specific an employee directory “section”. You may only access employee-attributes attached to sections that are accessible to you.

Authorizations

Authorization
string
header
required

The Lucca API implements the oAuth 2 protocol with the client-credentials-flow. Refer to RFC8725.

FlowClient Credentials
Token URL
https://accounts.world.luccasoftware.com/connect/token
Scopes1
employee-attributes.readonly
Read [employee-attributes](/api-reference/latest/employee-attributes/employee-attribute).

Headers

Api-Version
enum<string>
required

Set the API version.

Available options:
2024-11-01
Allowed value: "2024-11-01"
Maximum string length: 10
Example:

"2024-11-01"

If-None-Match
string

Only execute the request if current cached version of the resource does not match the one given here.

Example:

"W/q5sd4w2x1c1gfdg"

If-Match
string

Only execute the request if current cached version of the resource matches the one given here. Useful to avoid concurrency conflicts.

Example:

"W/q5sd4w2x1c1gfdg"

Accept-Encoding
string

List of compression algorithms you support.

Query Parameters

id
string[]

Filter out employee-attributes on their IDs.

Maximum array length: 100
Minimum string length: 1
Example:
definition.id
string[]

Filter out employee-attributes on the id of their associated definition.

Maximum array length: 100
Minimum string length: 1
Example:
employee.id
string[]

Filter out employee-attributes on the id of the employee they belong to.

Maximum array length: 100
Minimum string length: 1
Example:
applicability.asOf
string<date>

Only return employee-attributes whose applicability period includes the given date. An attribute is considered applicable when its applicability.start is on or before the date and its applicability.end is on or after the date. Null bounds are treated as open-ended.

applicability.strictAsOf
string<date>

Only return employee-attributes whose strict applicability period includes the given date. Same semantics as applicability.asOf, but on applicability.strictStart / applicability.strictEnd, which do not fill the gaps between consecutive resources. A date falling in a period without any contract therefore returns nothing.

value
string

Filter out employee-attributes on their value.

When the value is a JSON object, then supports sub-property filtering using dot notation (e.g. value.foo=bar).

-value
string

Filter out employee-attributes on their value, by exclusion ("not").

When the value is a JSON object, then supports sub-property filtering using dot notation (e.g. -value.foo=bar meaning "where value.foo is not equal to bar").

sort
enum<string>[]

Order results by instruction. Read more about sorting. Default: id.

Available options:
id,
-id,
createdAt,
-createdAt,
value,
-value,
definition.id,
-definition.id
lastUpdatedAt
string

Filter out employee-attributes on their lastUpdatedAt timestamp (range). ISO 8601 formatted date-time-offset-range string. Designed as a right-half-open interval: end is excluded [start, end).

Each bound must be written as yyyy-MM-ddTHH:mm:ss, with optional fractional seconds, followed by an offset (Z or ±hh:mm). Seconds are required. A timestamp read from a response payload can be reused as a bound as is, within a precision of 100 ns.

Examples:

  • 2026-01-01T00:00:00Z--2027-01-01T00:00:00Z: from Jan. 1st 2026 until Dec. 31st 2026.
  • ..--2026-06-01T00:00:00Z: until May 31st 2026 (included).
  • 2026-05-26T00:00:00Z--..: from May 26th 2026.
  • 2026-05-26T07:23:29.7977299+00:00--..: from May 26th 2026, 07:23:29.7977299 UTC.
Pattern: ^(?:\d{4}-(?:0[1-9]|1[0-2])-(?:0[1-9]|[12]\d|3[01])T(?:[01]\d|2[0-3]):[0-5]\d:[0-5]\d(?:\.\d+)?(?:Z|[+-](?:[01]\d|2[0-3]):[0-5]\d)|\.\.)--(?:\d{4}-(?:0[1-9]|1[0-2])-(?:0[1-9]|[12]\d|3[01])T(?:[01]\d|2[0-3]):[0-5]\d:[0-5]\d(?:\.\d+)?(?:Z|[+-](?:[01]\d|2[0-3]):[0-5]\d)|\.\.)$
Examples:

"2026-01-01T00:00:00Z--2027-01-01T00:00:00Z"

"..--2026-06-01T00:00:00Z"

"2026-05-26T00:00:00Z--.."

"2026-05-26T07:23:29.7977299+00:00--.."

page
string

Cursor of the page to retrieve: the page value of links.next.href or links.prev.href in a previous response. Cursors are opaque: don't build or modify them. An invalid cursor gets a 400 Bad Request. Read more about pagination.

limit
integer
default:25

Number of items per page. Defaults to 25. Maximum is 1,000. Read more about pagination.

Required range: 0 <= x <= 1000
include
enum<string>[]

Include metadata:

  • embedded: the partial or complete representations of related resources (e.g. the employee the resource belongs to).
  • links: links to related resources or actions (e.g. approving a leave-request). May be null when you do not have access to the resource (or action).
  • totalCount: only applicable on collections (i.e. lists of resources), gives the total number of items across all pages.

Read more about expanding responses.

Available options:
embedded,
links,
totalCount

Response

OK

A collection of employee-attribute resources.

type
string
Allowed value: "employee-attributes"
url
string<uri>
totalCount
integer<int64> | null

Total number of items across all pages that satisfy query parameters.

Required range: x >= 0
items
employee-attribute · object[]

Items of this paginated list. May be partial and/or stale representations.

Maximum array length: 1000

Links to related resources

embedded
object | null

Embeds the representation of resources related to the employee-attribute(s).

Only returned if requested by the API client: ?include=embedded.