leapTrigger
🚫

Access Denied

Your Scholar account doesn't have access to use leapTrigger.

Contact your admin to request access.

Complete your profile

We need your name and email to continue.

⚡ leapTrigger

Sign in to continue

Uses your Scholar account

↑↓ navigate ↵ open esc close
Edit Profile
#
Builder — Quick Reference
Sending a Request
1. Enter a URL and select a method (GET, POST, …)
2. Add query params, headers, body, or auth in the tabs below
3. Hit Send — response appears in the bottom panel
4. Paste a curl command into the URL bar to auto-fill all fields
Body Types
Raw / JSON — plain text or auto-formatted JSON
Form URL-encoded — key/value pairs sent as application/x-www-form-urlencoded
Multipart / File — mix text fields and file uploads (multipart/form-data)
Saving to a Collection
1. Enter a request name and collection name in the Save bar below the URL, then click Save
2. The request appears in the sidebar — click to reload it any time
3. Use the Variables tab to add per-request overrides (highest precedence)
Variables
Use anywhere in the URL, headers, params, or body. Manage variables in the Variables top-tab.
Runner — Quick Reference
Running a Collection
1. Select a Collection and optionally an Environment
2. Set Iterations to run all requests multiple times
3. Tick/untick requests in the checklist to control what runs — drag to reorder
4. Hit ▶ Run — results stream in live below
Data Files (Parameterised Runs)
Upload a .csv or .json file — each row becomes one iteration
Column headers become variable names, e.g. in the request URL
Click the green N rows ↗ badge to preview all rows
Options
Stop on failure — halts the run as soon as a request returns a non-success response
Keep variables — environment variables set by post-scripts persist across iterations
Delay — pause between requests (ms) to avoid rate-limiting
Reading Results
✓ pass — request completed and all assertions passed
✗ fail — request completed but an assertion failed
⚠ error — network error or timeout
Click ▾ Details on any row to see headers, body, and response. Export results via ↓ CSV or ↓ JSON.
How to use variables
Syntax
{{variable_name}}
Use double curly braces anywhere in the URL, headers, params, or body.
Examples
URL: https://{{base_url}}/api/{{version}}/users
Header: Authorization: Bearer {{token}}
Body: {"org": "{{org_id}}"}
Variable precedence (highest wins)
1. Local — per-request variables (Variables tab in Builder)
2. Environment — selected environment (e.g. "Production")
3. Global — always active, across all environments
Quick start
1. Click Global Variables → add base_url = https://api.example.com
2. Use it in any request: {{base_url}}/users
3. Or create an Environment to switch between staging / production values.
Secret Variables
Tick the Secret checkbox on any variable to mask its value in the UI.
Useful for tokens, passwords, and API keys — the value is stored but not displayed.
Sharing with Your Team
Open an environment → click ↑ Share to publish it org-wide.
Teammates see it under Org Environments and can copy it to their own envs.
Changes to a shared environment are live immediately — no re-publish needed.
Variables in Runner
Upload a CSV/JSON data file in the Runner to inject variables per iteration.
Each column header becomes a variable name — takes highest precedence during that iteration.
Builder
▶ Runner
Variables
+
Open tabs ()
Variables will be substituted from this environment.
✕
Params
Headers
Body
Auth
Variables
TypeKeyValue / File
Save the request first (via the Save tab), then add local variables here. Local variables override the selected environment for this request only.
Send a request to see the response
Sending…
⏱ ms
Body
Headers
No headers returned
HeaderValue
Closing tab auto-saves progress
⏸ Runner was interrupted
Requests to run
Select a collection and hit Run
⊘
No requests in this collection
✓
No failures so far — all requests passing No failed requests in this run
✓ All request(s) passed ✗ failed · passed
Total Avg Fastest Slowest Success
⚠ Run stopped after (iter #) —
Past Runs
⏸ Runner was interrupted
⏸ Paused
Closing tab auto-saves progress
Requests to run
Select a collection and hit Run
⊘
No requests in this collection
▶
Hit Run to start
✓
No failures so far No failed requests in this run
✓ All request(s) passed ✗ failed · passed
Total Avg Fastest Slowest Success
⚠ Run stopped after (iter #) —
⏱
No past runs yet — completed runs appear here
Past Runs ()
Global
🌐 Global Variables
Environments
No environments yet
Org Environments …
No shared environments
How to use variables
Syntax
{{variable_name}}
Use double curly braces anywhere in the URL, headers, params, or body.
Examples
URL: https://{{base_url}}/api/{{version}}/users
Header: Authorization: Bearer {{token}}
Body: {"org": "{{org_id}}"}
Variable precedence (highest wins)
1. Local — per-request variables (Variables tab in Builder)
2. Environment — selected environment (e.g. "Production")
3. Global — always active, across all environments
Quick start
1. Click Global Variables → add base_url = https://api.example.com
2. Use it in any request URL: {{base_url}}/users
3. Or create an Environment to switch between staging / production values.
Secret Variables
Tick the Secret checkbox on any variable to mask its value in the UI.
Useful for tokens, passwords, and API keys — the value is stored but not displayed.
Sharing with Your Team
Open an environment → click ↑ Share to publish it org-wide.
Teammates see it under Org Environments and can copy it to their own envs.
Changes to a shared environment are live immediately — no re-publish needed.
Variables in Runner
Upload a CSV/JSON data file in the Runner to inject variables per iteration.
Each column header becomes a variable name — takes highest precedence during that iteration.
🌐 Global Variables available across all environments
KeyValueSecret
✓ Active ● unsaved
KeyValueSecret
(yours)
KeyValueSecret
No variables
cURL