Get required fields for tax calculation and statutory filing
Returns all fields required for tax calculation and/or statutory filing in this jurisdiction. This is a discovery endpoint — it tells you what data needs to be collected for both persons (workers) and businesses (employers).
Each field includes:
entity— Who the field belongs to:person(worker data) orbusiness(employer data)scope— Whether the field is needed forcalculation(tax engine input),filing(statutory return), or bothcondition— When present, the field only applies if another field matches a specific value (e.g. pension PIN only whenis_pensionableis true)
Use this to:
- Render onboarding forms with the right fields for each country
- Filter by
entityto build separate person vs. business forms - Validate that existing records have complete data
- Understand what
worker_datarequirements will surface if fields are missing
How to submit fields by scope:
scope: ["filing"]fields → Submit viaPUT /v1/statutory/persons/{id}/fields/{countryCode}(person entity) orPUT /v1/statutory/businesses/{id}/fields/{countryCode}(business entity)scope: ["calculation"]fields → Submit viaPUT /v1/persons/{id}/taxProfilescope: ["filing", "calculation"]fields → Submit to both endpoints
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Headers
Required when using a Platform API token. The tenant key identifying which business to operate on.
Path Parameters
ISO 3166-1 alpha-2 country code
^[A-Z]{2}$Query Parameters
Filter fields by worker type
employee, contractor Filter fields by scope — "calculation" for tax engine inputs, "filing" for statutory return fields. Omit to return all fields.
calculation, filing Response
Required fields with entity, scope, type, and validation rules
Flat list of fields required for tax calculation and/or statutory filing in a jurisdiction. Each field includes its entity (person or business), scope (calculation, filing, or both), and validation rules.
Fields with entity: "person" are worker-level data. Fields with
entity: "business" are employer-level data. Use the entity field
to build separate onboarding forms for workers and employers.
"MX"
Schema version number, per jurisdiction. Increments when fields are added, removed, or changed for this country. Use this to detect when your cached field list is stale.
3
employee, contractor "employee"