Package Reroute Config API

The Package Reroute Config API provides REST endpoints for programmatic management of Package Traffic Controller (PTC) configuration in JFrog Artifactory—for example, reading settings and configuring which Artifactory remote repository handles each package type.

Important: The repo_key for each registry type must reference a remote repository. Virtual repositories are not supported—PTC requires the upstream-facing remote to track consumption accurately and apply Curation configuration automatically. The PUT /artifactory/api/package-reroute/config/{type} endpoint will reject non-remote repo_key values in a future release.

Whether Package Reroute is available for your instance is determined by your JFrog license and subscription (and related entitlement); it is not something you turn on via a documented customer enable API. Coordinate with your JFrog account team for licensing.

Defaults and naming: The Router path for package reroute is /package-reroute—product-defined and not customer-configurable. Point Zscaler ZIA at that literal path. The REST endpoints in this API always live under the fixed prefix /artifactory/api/package-reroute/ (also not a renameable path). GET /package-reroute/config returns configuration such as enabled and per-type repo_key; it does not expose a separate Router redirect path setting. PUT /package-reroute/config/{type} sets the repo_key (remote repository name) that receives rerouted traffic for each package type.

All endpoints require admin privileges. Authenticate using Bearer token (JWT) or Basic auth.

For deployment and operator guidance, see Package Traffic Controller in JFrog Security documentation.

Related Topics