Shripi Guide

1. Installation

Shripi is a Chrome extension available from the Chrome Web Store.

1. Open the Chrome Web Store and search for Shripi, or use the direct link on the homepage.
2. Click Add to Chrome, then confirm by clicking Add extension in the dialog.
3. The Shripi icon () will appear in your Chrome toolbar. Pin it for easy access.
4. No account required to start capturing. Sign in only if you want to sync your Pro license.

2. Quick Start

Start capturing in three steps:

1. Click the Shripi icon in your toolbar to open the popup.
2. Click "Start Capture" (or the toggle in the top bar). A green "Capturing" indicator confirms it's running.
3. Browse your app and watch requests appear in real time. Click any row to inspect its full details — headers, body, response, timing.

When you've captured what you need, click any request row and use the Copy as dropdown to export it as cURL, Python, Fetch, or Postman.

3. Filtering Requests

The toolbar above the request list gives you several ways to narrow down what you see:

• Search box — Type to filter by URL, path, domain, or header values. Use the scope selector to limit search to URL only, domain only, or URL + headers.
• Method filter — Filter to GET, POST, PUT, PATCH, DELETE, or any combination.
• Status filter — Filter to 2xx (success), 3xx (redirect), 4xx (client error), or 5xx (server error).
• Grouped / flat view — Toggle between grouping requests by domain/endpoint or showing them in a flat chronological list.

To exclude URLs from capture entirely (e.g. analytics or ad tracking calls), go to Settings → Exclude URL patterns and enter a substring or regex pattern.

4. Exporting

Shripi supports multiple export formats. Access them via the Export button in the toolbar.

Clean mode

Enable Clean mode before exporting to strip browser-injected noise headers (sec-fetch-*, user-agent, accept-encoding) that are irrelevant to your API calls.

Env var placeholders (Pro)

With Env var placeholders enabled, redacted values are replaced by ${VARIABLE_NAME} in cURL and Python exports. Python exports also auto-emit os.getenv() declarations so the code runs as-is once you export your env vars.

5. Redaction

Redaction is on by default. It strips sensitive values before they appear in the UI or any export, so you never accidentally share credentials.

What gets redacted

• Authorization headers — Any header matching the auth header name patterns (default: ^authorization$).
• Sensitive cookies — Cookies with names matching known session patterns (sessionid, token, auth, etc.).
• Sensitive query params — URL parameters like token, api_key, secret, access_token.
• JSON body keys — Keys like password, secret, private_key in request bodies.

Customizing redaction (Pro)

In Settings → Redaction you can:

• Add custom auth header name patterns (regex, e.g. ^x-api-key$)
• Add custom auth header value patterns
• Add custom sensitive cookie name patterns
• Add custom sensitive query param patterns

6. Session Management

Shripi keeps captured requests in memory by default. When you close the extension or navigate away, the session resets.

Persistent storage (Pro)

Enable Persistent storage in Settings to save your captured session to IndexedDB. Your requests survive browser restarts and tab refreshes.

Request limit

Set a Request limit (default: 500) to cap how many requests are stored. When the limit is reached, the oldest requests are pruned automatically. Set to 0 for unlimited (Pro).

Clearing history

Click the Clear button in the toolbar to delete all captured requests for the current session. You'll be prompted to confirm. This action is irreversible.

7. Settings Reference