Skip to main content
POST
Resolve effective employee field sources

Authorizations

Authorization
string
header
required

Use an API key or OAuth access token. Enter only the token in the authorization dialog; requests send it as Authorization: Bearer <TOKEN>.

Create an API key in your workspace's Settings → API keys. Keys start with wm_api_ and only work in the workspace where they were created. Read-only keys can read data; creating, updating, or deleting data requires a read-write key.

OAuth access tokens are issued for connected Windmill applications.

Both token types use the authenticated user's workspace permissions. Each endpoint's permission requirements and the sharing settings of the requested items still apply.

Path Parameters

companyId
string
required

Company ID. A URL slug is also accepted. The caller must have access to this company.

Required string length: 1 - 128
Example:

"company-acme"

Body

application/json
employeeIds
string[]
required

Up to 1000 employee IDs, each 1–256 characters. Every ID must belong to the company. Repeated IDs are resolved once in first-seen order. An empty array returns no resolutions.

Maximum array length: 1000
Required string length: 1 - 256
Example:
fieldKeys
enum<string>[]

Up to 100 field keys. Repeated keys are resolved once in first-seen order. Omit to inspect all supported field keys; an empty array resolves no fields.

Maximum array length: 100

Employee profile field whose owning source is configured or resolved.

Available options:
avatarUrl,
dateOfBirth,
departments,
displayFullName,
employmentStatus,
employmentType,
ethnicity,
firstName,
preferredName,
gender,
jobLevel,
jobTitle,
lastName,
managerId,
maritalStatus,
phoneNumber,
primaryEmail,
pronouns,
startDate,
terminationDate,
workLocation,
country
Example:

Response

Effective employee field owners and source-confirmation status; unowned pairs omitted.

resolutions
object[]
required