Jupiter Developers

Request logs show the individual requests made with a team’s API keys, newest first. Use them to debug an integration: see the status the gateway returned, how long a request took, how many credits it cost, and which firewall rule, if any, applied.

View and filter

Logs are scoped to a team and listed newest first, with cursor-based pagination. Filter the list by:

Status Code
Method
API Group
Path

Request logs list in Portal with status, method, API group, and path filters applied

Request detail

Select a request to open its detail panel. The panel shows the full record for that request, including the firewall decision and the rules that matched.

Request log detail panel showing the full record including the firewall decision

Field reference

Each log entry records:

Field	Description
Timestamp	When the gateway received the request.
Request ID	Unique ID for the request.
Client IP	The caller’s IP address.
ASN	The caller’s autonomous system number.
Country	The country the request came from.
Host	The host the request was sent to.
Referrer	The referrer header, if sent.
User agent	The user-agent header.
Method	The HTTP method.
Path	The URI path and query string.
Status	The HTTP status code returned.
Bytes sent / received	Response and request sizes.
Credits consumed	Credits the request cost.
Latency	Total time, broken into auth, time to first byte, and time to last byte.
Firewall	The outcome and the rules that matched.

Retention

Request logs are kept for 6 months.

Analytics

Aggregate traffic, performance, and cost across requests.

Firewall

See the rules behind the firewall decisions in your logs.

Response Codes

What each HTTP status in the logs means.

Plans and Pricing

How credits are counted per endpoint.

Firewall Analytics

⌘I

​View and filter

​Request detail

​Field reference

​Retention

​Related