Length-preserving masking
Secrets are masked, not dropped. An API key is stored and shown as •••••1234 so you can still tell requests apart without ever holding the real value.
02SUPPORT
API Logs
Your API is now how your users use your product. Restless brings every request into one place, so you can see which endpoints get hit, which calls fail, and where people give up.
$ npx restless init
Your API is how agents and users reach your product. Restless gives you a window into all of it.
Filter by user, endpoint, status, or error to find the exact calls you care about.
Every request is captured in full, so you can trace any issue back to what really happened.
Your users can see their own logs too, through the Workbench and MCP.
FULL STACK
See who isusing your API
Every customer, the endpoints they hit, and where they’re running into errors.
The Restless log view: a filter rail for endpoint, status and method beside a table of customers, their API keys, request volume and when they last called.
INSIGHTS
…or you canjust ask
Your logs are on the MCP server, so you can ask about your users in plain language.
HOW IT WORKS
The SDKuploads your log
restless.setup adds a small middleware to your app. It captures each request and response and ships them to Restless, tagged by the customer who made the call.
Detects your framework, generates your OpenAPI spec, and wires the SDK into your server.
server.js, where restless.setup wraps the app: it masks the authorization header, tags each call with the workspace that made it, resolves that owner once and caches it, and installs restless.errorHandler after the routes.
- Off the request path
- Requests are batched and uploaded in the background, so the SDK adds no latency to your API.
- Redacted by default
- Authorization and Cookie headers, and fields like password and ssn, are stripped before anything leaves your server. The list extends itself from your OpenAPI spec.
- Owner enrichment
- Owner metadata resolves once per owner id, then caches. A hundred calls from the same workspace don’t hit your database a hundred times.
- Error triage built in
- 4xx and 5xx responses get an x-log-url header and a debug block, so a failed call links straight to its captured log.
Security
Audited PII access
Every time someone opens an end-user’s data it’s recorded as log.view or user.view, with the email stored only as a hash.
FULL STACK
One view ofevery request
Captured in full, attributed to a customer, and ready to filter, ask, or replay.
Full Requests and Responses
Who called, what they sent, and what came back, down to the headers and body. The complete record, not a sample or a summary, so you can trace any issue to the exact request.
Sensitive fields are redacted before they leave your server.
Filter by anything
User, endpoint, method, status code, or user agent. Narrow to the exact calls you care about.
Owner enrichment
Every request is tied to the customer who made it, enriched with their name, plan, and contact.
Problems rise to the top
Repeated failures and high-error endpoints surface on their own.
Read it your way
Browse it in the Workbench or ask about it over MCP.
Replay and debug
Open any request in the inspector and replay it as cURL, HAR, or Postman.
Shareable views
Filter down to a slice of traffic and share the exact view with a link. Everyone opens the same filtered logs, no screenshots.
Related features
MCP Server
Filter your logs and replay any request to see exactly what failed.
Human Support
Answer developer questions with the full request already in front of you.
Workbench
Give agents native access to your API, no docs required.
GET STARTED
Setup is a breeze
Restless is tightly integrated with your API, so we install a small SDK. Don't worry, we walk you through every step of the way.
Nothing is uploaded without your permission.
$ npx restless init
A terminal animation shows the Restless API setup from introduction through account login.