diff --git a/README.md b/README.md index e587e4b..78323fd 100644 --- a/README.md +++ b/README.md @@ -224,6 +224,10 @@ required. The candidate will be emailed after they apply to the job, unless the | `silent` | Disables confirmation email sent to candidates upon application. Accepts values of `true`, `false`, `"true"` or `"false"`. | `source` | Adds a source tag to candidate (e.g. 'LinkedIn') | `ip` | IP application was submitted from, used for detecting country for compliance reasons (e.g. `"184.23.195.146"`) +| `timezone` | IANA timezone identifier for the applicant (e.g. `"America/New_York"`). Invalid timezone strings are silently ignored. +| `userAgent` | User-Agent string for the applicant's client. If omitted, captured from the `User-Agent` request header. Useful for backend/proxy integrations forwarding a browser's value. Truncated to 512 characters. +| `acceptLanguage` | Accept-Language string for the applicant's client. If omitted, captured from the `Accept-Language` request header. Truncated to 256 characters. +| `referer` | Referring URL for the application. If omitted, captured from the `Referer` request header. Truncated to 2048 characters. | `consent.marketing` | Indicate whether candidate is open to being contacted about future opportunities (e.g. `"consent":{"marketing":true}` for `JSON`, or `consent[marketing]=true` for `multipart/form-data`)

A `compliancePolicyId` can be added to indicate the policy that applies to this posting (e.g. `consent":{"marketing": {"provided": true, "compliancePolicyId": ""}}` for `JSON`, or `consent[marketing][provided]=true` and `consent[marketing][compliancePolicyId]=""` for `multipart/form-data`)
Note: to be released in waved rollouts starting mid-September, 2024 | `consent.store` | Indicate whether the candidate has provided consent for the purpose of storing and processing their data (e.g. `"consent":{"store":true}` for `JSON`, or `consent[store]=true` for `multipart/form-data`)
Note: to be released in waved rollouts starting mid-September, 2024

A `compliancePolicyId` can be added to indicate the policy that applies to this posting (e.g. `consent":{"store": {"provided": true, "compliancePolicyId": ""}}` for `JSON`, or `consent[store][provided]=true` and `consent[store][compliancePolicyId]=""` for `multipart/form-data`)
Note: to be released in waved rollouts starting mid-September, 2024 | `opportunityLocation` | The posting location associated with the opportunity. If no posting is provided, opportunityLocation is not set. If not specified and a multi-location posting is provided, opportunityLocation defaults to “unspecified”. Defaults to the posting location for single-location postings.