POST /api/v2/organizations/:org_id/usage_export_job is a CircleCI Cloud API. CircleCI Server does not produce usage-export data from that route. There is no service in the cluster that should answer it with a report.
Cloud articles that show this curl against circleci.com do not apply to a Server hostname.
What Server returns
Before Server 4.8 the route was not served, so the call typically came back as not found.
Starting in 4.8, public-api-service still exposes this Cloud path and points the missing backend at localhost. The call then fails immediately with HTTP 500 and an error like:
dial tcp [::1]:80: connect: connection refused
The loopback target is intentional. It fails fast instead of hanging on a host that does not exist. The 500 is not a crashed usage service you can scale, and it is not fixed by retrying the Cloud request body.
Related Cloud-only how-tos, for Cloud orgs only:
