CONCIERGE_ORIGIN_INVALID

Not an origin the widget can be pinned to

HTTP status 400 Bad Request, code CONCIERGE_ORIGIN_INVALID.

What it means#

An entry in a channel's Concierge allowedOrigins is not an exact origin. Origins are pinned the way the embed contract pins parent_origin, compared for equality with the page's window.location.origin, so each entry is a scheme and a host (and a port when it is not the default): https, or http on localhost, with no path, query, fragment, credentials or wildcard. At most 20.

What to do#

Send each origin as the browser reports it, e.g. https://tickets.example.com; list every subdomain that hosts the widget separately.

On the wire#

Every error response carrying this code names this page in error.moreInfo, with the request id in the query string. See Error codes for the response shape and the list of every code.