Follow the HTTP redirect chain for a QR code URL captured from product packaging and return the final canonical URL plus the intermediate hops.
Used by the dual-scan flow: after the operator scans a QR code, the client posts the URL here, displays the resolved value, and (if accepted) calls /captures/{id}/save-redirect to persist it as a redirect rule on the trade item.
Behavior:
error_message rather than failing the request when the URL is unreachable.https://) are followed transparently.Documentation Index
Fetch the complete documentation index at: https://docs.closient.com/llms.txt
Use this file to discover all available pages before exploring further.
Request body for following the redirect chain of a captured QR URL.
QR code URL to resolve. Must be http:// or https://; non-HTTP schemes are rejected with error_message populated in the response (the request itself does not 4xx — failure modes are surfaced uniformly so the UI can render a single error path).
1 - 2048OK
Result of following the redirect chain for a QR code URL.
The URL submitted by the caller.
Final URL after following all redirects. Equal to initial_url when no redirects were followed and when an error short-circuited the chain (so the UI always has a URL to show alongside error_message).
Number of HTTP 3xx redirects followed before reaching the final URL. Capped at 10 — chains longer than that surface as an error_message rather than a partial result.
x >= 0Empty on success. On failure, a human-readable description of the error (timeout, connection refused, too many redirects, malformed URL). The UI surfaces this string directly to the operator.
True when error_message is empty.
Ordered list of URLs visited, starting with initial_url and ending with final_url. Empty when an error short-circuited resolution before any response was received.