POST /products/refresh requests a fresh update for specific products. Use it when you need Octogen to refresh a known set of product pages sooner than the standard catalog update cadence. The endpoint returns as soon as the request is accepted; it does not wait for downstream processing or indexing to finish.
Request
Body parameters
object[]
required
Product identifiers to refresh. Maximum 500 targets per request.
string
Product page URL to refresh. Provide either
url or uuid, not both.string
Octogen product UUID to refresh. Provide either
uuid or url, not both.string
Optional active crawled catalog key. Include this when the URL is not already indexed, or when the same URL could belong to more than one active crawled catalog.
Example
Response
The endpoint returns202 Accepted when at least one target was accepted for refresh. It returns 400 Bad Request with the same response shape when no target could be accepted.
string
required
Request identifier for this refresh request.
integer
required
Number of targets received in the request.
string | null
Provider-neutral workflow identifier for the asynchronous refresh, when a workflow was started.
string | null
Non-fatal workflow launch error. If this is present, accepted targets were still accepted, but Octogen could not start the downstream refresh workflow automatically.
object[]
required
Targets accepted for refresh after authorization and validation.
object[]
required
Targets that were not accepted. Each rejection includes the original
target, a machine-readable code, and a human-readable message.Example response
Resolution rules
Errors
Product refresh is asynchronous, and the accepted request starts a
multi-stage chain: recrawl, extraction, and re-indexing. Expect search and
lookup results (including a product’s active status) to update within a few
hours of acceptance, not minutes. The 202 response confirms scheduling
only.