Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Upcoming change to Greeting & Title on traveller profiles

Currently available fields:
 

...

Important: Depending on the agency settings for 'Title structure', either commonTitle / formalTitle OR compoundTitle are being used. Please consult our documentation for further details.

On top of that, two new greeting/gender values are implemented: Miss (MISS) & Undisclosed/Others (NON_BINARY, X)

Furthermore, a new field will be available: Name suffix / nameSuffix

Transition logic for deprecated fields

We will continue to support the deprecated fields until their scheduled removal. The following translation logic will be applied:

DirectionFieldLogic
From Faces (HTTP GET)gender
  • If a commonTitle is present, it is reported as-is
  • If a Otherwise, the one-letter code of the sex is set, it is reported (M / F / U / X)
  • Otherwise the field will be set to null
 titleWill be mapped one-to-one from greeting.formalTitle
To Faces (HTTP PATCH / POST)gender
  • If value is a known sex type one-letter code (M / F / U / X), apply it as "sex"
    • For F set greeting commonTitle = MS
    • for M set greeting commonTitle = MR
  • If value is a known common title, apply it as such and derive the default sex from it (e.g. MR = Sex "MMALE", MS = Sex "FFEMALE")
  • Otherwise set Sex = "UUNDEF" and remove commonTitle. The sent value will not be stored.
 titleWill be mapped one-to-one to greeting.formalTitle

New standard field 'state' on company

With our next release the new field 'state' will be available on all company profiles. If on a company profile the country field is filled with either 'United States', 'Canada', or 'Mexico', an additional standard field will be available to select the 'state'. The 'state' field includes all relevant states of the respective country in a drop-down list. The value of 'state' in the JSON is always a two-letter code.

Image Added Image Added

API rate limiting

If we monitor excessive API calls over a longer period, we reserve the right to set a rate limiting or to charge for these calls.