Appearance
Fetch the configured HOME latest update with Changelog fallback ​
The resolved widget deployment selects Changelog or the newest published Ghost post tagged product or #product. Ghost failures and empty results fall back to Changelog.
Request preparation ​
Send a GET request to /widget/latest-update on the appropriate server. Check the API overview for base URL guidance and the server information in the interactive reference. Replace path placeholders with identifiers from the intended account or site; a similarly named record in another workspace is not interchangeable.
No separate path or query parameters are declared for this operation in the current specification. Do not invent filtering or pagination options from another endpoint; use only the contract shown here.
No request body is declared in the current specification. Check the route and any documented parameters before sending the request rather than adding an arbitrary JSON payload.
Authentication and scope ​
The specification lists these security alternatives: BearerAuth, AccessToken. Read any operation-specific restrictions as well: browser-session, account-role, and signed-user requirements may impose additional conditions. See authentication before choosing a credential.
Keep credentials in the appropriate private configuration and remove secrets from shared logs. Confirm the target resource belongs to the intended workflow before issuing a request. Authentication alone should not be treated as confirmation that a supplied account, site, or customer identifier is correct.
Response handling ​
The documented responses for Fetch the configured HOME latest update with Changelog fallback are:
- 200: Latest update or null when neither source has a published item
- 401: Site key required or invalid
- 403: Widget origin not allowed
Begin with a known record or a narrow query and inspect the returned fields before displaying them to users. Where the operation defines pagination, follow those parameters to retrieve additional results. An empty successful response is different from a failed request; keep errors visible to the calling workflow instead of presenting them as an empty data set.
If a connection fails after submission, investigate the current server state before repeating an action whose outcome is uncertain. When requesting support, retain the method, route, response status, and sanitized error message. The interactive reference below provides the detailed schemas and examples for this specific operation.
Fetch the configured HOME latest update with Changelog fallback​
GET
/widget/latest-update
The resolved widget deployment selects Changelog or the newest published Ghost post tagged product or #product. Ghost failures and empty results fall back to Changelog.
Authorizations​
BearerAuth
JWT token from login
Type
HTTP (bearer)
or
AccessToken
Personal access token. Value: Token <your-token>
Type
API Key (header: Authorization)
Responses​
Latest update or null when neither source has a published item
application/json
JSON"requested_source": "string","resolved_source": "string","update": "string","card_html": "string"
{
 Â
 Â
 Â
 Â
}