How does it find API endpoints?

It reads them from the definition rather than crawling the app. The endpoints mode prints every route and method the spec declares. Use brute mode or a crawler like katana to locate the file first.

Can it brute force endpoints from a wordlist?

No. brute mode probes common paths for the definition file, not arbitrary routes. For wordlist route discovery without a spec, use ffuf.

Which spec formats does it accept?

Set --format to json, yaml, yml, or js (default json). It reads Swagger 2.0 and OpenAPI 3. Use --base-path when the file omits the API root.

How do I keep it from hitting destructive endpoints?

It flags operations that match a dangerous-word list before firing them. Use --safe-word to exempt a false match, --rate to cap requests per second, and --quiet to skip prompts.

Can I route requests through a proxy?

Yes. Set --proxy to a host and port such as http://127.0.0.1:8080. Add --headers and --agent to control how each request looks.

Updated Jul 14, 2026

Discovery

Audit API routes from an exposed OpenAPI spec

Audit endpoints declared in exposed Swagger and OpenAPI specs.

Turn a leaked spec into a route list Replay documented requests to audit the live API Locate an undiscovered definition file

overview

What swagger-jacker does

Place swagger-jacker after you locate an exposed Swagger or OpenAPI definition and before fuzzers or template scanners that need concrete routes.

Operators use it when a leaked spec lists methods and paths that would otherwise need guessing. Point --url or --local-file at the definition, then pick a command mode.

Modes cover endpoints listing, automate replay, brute for the definition file, convert to URL lists, and prepare curl stubs. Pair with a crawler when the spec itself is still missing.

source github.com/BishopFox/sj

use cases

Where swagger-jacker fits

Turn a leaked spec into a route list

Run the endpoints command against a discovered Swagger or OpenAPI file to extract every documented path and method as structured data the workflow can act on.

Replay documented requests to audit the live API

Use automate mode to send a request to each endpoint the definition declares, with --rate limiting and a --proxy so the traffic stays controlled and observable.

Locate an undiscovered definition file

Point brute mode at a host to probe common paths where a Swagger or OpenAPI file tends to live, then audit the spec once it turns up.

Test against a separate host

Set --target to a host that differs from where the documentation lives, useful when a spec is served from a CDN but the API runs elsewhere.

Hand the routes to another tool

Use convert mode to write the spec out as a plain list of URLs, or prepare mode to emit curl commands, so a fuzzer or scanner downstream can consume the endpoints cleanly.

reference

swagger-jacker inputs and flags

15 inputs

Name	Type	Flag	Description
url	STRING	--url	Load the documentation file from a URL.
local-file	FILE	--local-file	Load the documentation from a local file.
command	STRING	·	Mode to run: automate, brute, convert, endpoints, or prepare.
target	STRING	--target	Set a request target if it differs from where the docs reside.
format	STRING	--format	Format of the definition file (json, yaml, yml, js).
rate	STRING	--rate	Limit the number of requests per second (default 15).
headers	STRING	--headers	Add custom headers in Name: Value form, repeatable.
proxy	STRING	--proxy	Proxy host and port, for example http://127.0.0.1:8080.

Showing key inputs. swagger-jacker exposes 15 inputs in total.

Full flag reference (15 inputs)

Name	Type	Flag	Description
url	STRING	--url	Load the documentation file from a URL.
local-file	FILE	--local-file	Load the documentation from a local file.
command	STRING	·	Mode to run: automate, brute, convert, endpoints, or prepare.
target	STRING	--target	Set a request target if it differs from the host the documentation resides on.
format	STRING	--format	Format of the definition file: json, yaml, yml, or js (default json).
base-path	STRING	--base-path	Set the API base path if the definition omits it, for example /V2/.
rate	STRING	--rate	Limit the number of requests per second (default 15).
timeout	STRING	--timeout	Request timeout period in seconds (default 30).
headers	STRING	--headers	Add a custom header in Name: Value form; repeatable.
agent	STRING	--agent	Set the User-Agent string sent with each request.
randomize-user-agent	BOOLEAN	--randomize-user-agent	Randomize the User-Agent string (default false).
proxy	STRING	--proxy	Proxy host and port, for example http://127.0.0.1:8080.
insecure	BOOLEAN	--insecure	Ignore server certificate validation.
safe-word	STRING	--safe-word	Exempt the given word from the dangerous-word check; repeatable.
quiet	BOOLEAN	--quiet	Do not prompt for input; use default values for all requests.

example

Run swagger-jacker

swagger-jacker · command

# list every route the exposed spec declaressj endpoints --url https://example.com/v2/swagger.json # replay each documented request through Burp, rate-limitedsj automate --url https://example.com/v2/swagger.json --proxy http://127.0.0.1:8080 --rate 10

sample output

GET     https://example.com/api/v2/usersPOST    https://example.com/api/v2/usersGET     https://example.com/api/v2/users/{id}PUT     https://example.com/api/v2/users/{id}DELETE  https://example.com/api/v2/users/{id}GET     https://example.com/api/v2/ordersPOST    https://example.com/api/v2/orders/{id}/refundGET     https://example.com/api/v2/admin/config

guidance

Choosing swagger-jacker

Reach for swagger-jacker once you have a Swagger or OpenAPI definition to audit. Spec-driven only. For routes without a definition, use ffuf. To find the definition first, crawl with katana or run brute mode.

katana

Crawls an app to find the spec and other endpoints. Locate the definition, then audit it here.

ffuf

Brute-forces routes without a spec. Use when no definition file exists.

nuclei

Template-based issue checks. Run after routes are enumerated from the spec.

faq

swagger-jacker questions

An API definition loaded with --url or --local-file, plus a command mode: endpoints, automate, brute, convert, or prepare.

Run swagger-jacker yourself

An exposed spec URL feeds Swagger Jacker, which enumerates and tests the documented routes and writes the audited endpoints as an output.

Open swagger-jacker in the library Build a workflow with it

Facts on this page come from the live Trickest tool library.

Audit API routes from an exposed OpenAPI spec

What swagger-jacker does

Where swagger-jacker fits

Turn a leaked spec into a route list

Replay documented requests to audit the live API

Locate an undiscovered definition file

Test against a separate host

Hand the routes to another tool

swagger-jacker inputs and flags

Run swagger-jacker

Choosing swagger-jacker

katana

ffuf

nuclei

swagger-jacker questions

More Discovery tools

apkurlgrep

cariddi

crawlergo

dirsearch

fallparams

feroxbuster

Run swagger-jacker yourself