Endpoint
latest version of the product, reading from a redirects.jsonc file in the product’s versioned content directory.
Unlike other content endpoints, this route does not accept a
version parameter. It always resolves to the latest version’s redirect rules.Path parameters
The slug identifying the product.Examples:
terraform-plugin-framework, terraform-enterpriseExample requests
Response
Returns a JSON array of redirect rule objects. Each object maps a source path to a destination path.200
Response fields
The response is a top-level JSON array. Each element is a redirect rule object:The original URL path that should redirect. May include path segments but does not include the hostname.
The target URL path to redirect to.
When
true, the redirect is treated as a permanent (301) redirect. When false or absent, it is a temporary (302) redirect.Response headers
| Header | Description |
|---|---|
content-type | Always application/json |
served-from | Indicates whether content was served from current build or production |
How redirects files are structured
Redirect rules are stored as JSONC (JSON with comments) files atcontent/<productSlug>/<version>/redirects.jsonc. JSONC allows inline comments to document the reason for each redirect.
redirects.jsonc:
Error responses
| Status | Body | Cause |
|---|---|---|
404 | Not found | The productSlug is not in the product configuration, the latest version metadata could not be resolved, or no redirects.jsonc file exists for the product. |
500 | Server error | The redirects.jsonc file exists but could not be parsed. |