Update a guest

Updated:

PUT/property/{connection_id}/guest/{id}

Updates the PropertyGuest identified by id. Provide the unified PropertyGuest fields to change in the request body.

Parameters

fieldsstring array
Fields to return
rawstring
Raw parameters to include in the 3rd-party request. Encoded as a URL component. eg. raw parameters: foo=bar&zoo=bar -> raw=foo%3Dbar%26zoo%3Dbar
connection_idstring required
ID of the connection
idstring required
ID of the Guest

Payload

idstring
unique identifier for the guest
created_atdate-time
when the guest was created (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
updated_atdate-time
when the guest was last updated (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
namestring
the guest full name
first_namestring
the guest first name
last_namestring
the guest last name
emails array
email addresses of the guest
telephones array
telephone numbers of the guest
addressobject
postal address of the guest
languagestring
the guest preferred language (ISO 639-1)
nationalitystring
the guest nationality
company_namestring
the guest company name
image_urlstring
URL of the guest picture
notesstring
free-text notes about the guest
metadata array
custom field values

Returns

Response fieldTypeRequiredDescription
idstringNounique identifier for the guest
created_atstring (date-time)Nowhen the guest was created (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
updated_atstring (date-time)Nowhen the guest was last updated (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
namestringNothe guest full name
first_namestringNothe guest first name
last_namestringNothe guest last name
emailsPropertyEmail[]Noemail addresses of the guest
emails[].emailstringYesthe email address
emails[].typeenumNothe kind of email address Values: WORK, HOME, OTHER
telephonesPropertyTelephone[]Notelephone numbers of the guest
telephones[].telephonestringYesthe telephone number
telephones[].typeenumNothe kind of telephone number Values: WORK, HOME, MOBILE, FAX, OTHER
addressobjectNopostal address of the guest
address.address1stringNofirst line of the street address
address.address2stringNosecond line of the street address
address.citystringNocity or locality
address.regionstringNostate, province or regional area
address.region_codestringNostate, province or regional area code
address.postal_codestringNopostal or ZIP code
address.countrystringNocountry name
address.country_codestringNoISO 3166-1 alpha-2 country code
languagestringNothe guest preferred language (ISO 639-1)
nationalitystringNothe guest nationality
company_namestringNothe guest company name
image_urlstringNoURL of the guest picture
notesstringNofree-text notes about the guest
metadataPropertyMetadata[]Nocustom field values
metadata[].idstringNothe custom field identifier
metadata[].slugstringNothe custom field key
metadata[].valueobjectNothe custom field value
metadata[].namespacestringNothe scope or origin of the custom field
metadata[].formatenumNothe data type of the value Values: TEXT, NUMBER, DATE, BOOLEAN, FILE, TEXTAREA, SINGLE_SELECT, MULTIPLE_SELECT, MEASUREMENT, PRICE, YES_NO, CURRENCY, URL
metadata[].extra_dataobjectNoadditional data about the custom field

Errors

Errors return the HTTP status code and a JSON body with statusCode, error (the short label) and message (a human-readable detail).

{
  "statusCode": 429,
  "error": "Too Many Requests",
  "message": "Too many requests to unified.to API; max requests per minute: N"
}
StatusErrorMeaning
400Bad RequestThe request was malformed or failed validation.
401UnauthorizedThe connection is likely broken; re-authorize it.
403ForbiddenThe connection is missing permissions or scopes.
404Not FoundThe requested resource does not exist.
429Too Many RequestsRate limit exceeded (see the two sources below).
500Internal Server ErrorAn unexpected error occurred.
501Not ImplementedNot supported by this integration.

Errors from the underlying integration pass through: the integration's status comes back as ours (429, 401, 403, 404 or 5xx), usually with its message. When the integration's error body is unclear, Unified extracts what it can and returns a clearer message.

429 Too Many Requests

A 429 has two possible sources:

  • The integration's own rate limit, passed through.
  • Unified's workspace limit: a rolling 60 seconds, set by plan, with the message Too many requests to unified.to API; max requests per minute: N.
const options = {
  method: 'PUT',
  url: 'https://api.unified.to/property/5de520f96e439b002043d8dc/guest/5de520f96e439b002043d8d8',
  headers: {
    authorization: 'bearer .....'
  },
  data: undefined,
  params: {
    fields: '',
    raw: '',
  }
};

const results = await axios.request(options);
Are we missing anything? Let us know
Was this page helpful?