`bunny api GET /pullzone/v2/pullzones/{Id}/logs` is not working for me

[BryanWilhite]

I thought I would look at my pull-zone logs by translating the documented REST call into the CLI. This command returns a 404:

bunny api GET /pullzone/v2/pullzones/{Id}/logs

Is /pullzone/v2/ implemented?

[jedisct1]

Hi Bryan,

The bunny api command sends requests to https://api.bunny.net/, but the logging API is hosted at https://logging.bunnycdn.com/ .

That’s why you got a 404 .

The CLI could automatically use the logging API URL for /v2/pullzones/<id>/logs. But maybe a dedicated subcommand would be more convenient.

Maybe something like:

bunny pullzone logs 12345 \
  --from 2026-08-08T00:00:00Z \
  --to 2026-08-09T00:00:00Z \
  --status 4xx,5xx \
  --limit 100 \
  --offset 0 \
  --order desc

?

What do you think?

[jamie-at-bunny]

I like the idea of the logs subcommand using the logging URL as its base url. I'm hoping to get #86 merged soon, and we can add logs to it as a follow up.