Frequently asked questions

Pingo is a compact macOS menu bar app for quick HTTP requests. Choose a method, enter a URL, add headers or a body when needed, then inspect the response without opening a full API client.

Pingo supports GET, POST, PUT, PATCH, and DELETE requests.

No. Pingo uses an ephemeral network session and does not maintain an automatic cookie jar, response cache, or HTTP credential store. The current request and response live in the app while you work with them, but Pingo does not provide saved histories, accounts, or cloud sync.

Yes. Add Cookie, Authorization, or other required values explicitly in the header editor. Pingo sends the headers you provide but does not automatically store or reuse them for later requests.

Pingo shows the HTTP status, request duration, content type, response headers, and a text preview of the response body. Large response previews are limited to keep the app responsive.

Yes. You can stop an in-flight request. Pingo also applies request and resource timeouts so an unresponsive endpoint does not keep the scratchpad busy indefinitely.

Requests go directly from your Mac to the URL you enter. Pingo does not proxy request URLs, headers, bodies, or responses through a Pingo service.

Pingo requires macOS 14 or later.

Pingo uses Sparkle to check for signed updates. You can start an update check from the app, and available releases are provided through the project's GitHub release infrastructure.

Yes. The source code is available on GitHub under the MIT License.