You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 20, 2026. It is now read-only.
No, it is not. Burp Rest API exposes functionalities that are best suited for the Professional
8
+
version of Burp Suite. Even if it was possible to start _burp-rest-api_ using the Free version of Burp, this is no longer possible and the support won't be included in future releases.
9
+
10
+
Whenever I run the gradle command I receive an error. What can be the the cause?
There are two binding ports in a standard burp-rest-api setup:
35
+
-**burp-rest-api RPC mechanism**. Both IP address and port can be customized at runtime using command line arguments (namely _--server.address_ and _--server.port_)
36
+
-**Burp Proxy Listener**. This is a Burp Suite configuration, and can be customized using a custom project option file.
Next generation Burp Suite v2 is a beta release at the time of writing this FAQ. While we will *try* to mantain support for both Burp Suite stable and beta, we cannot ensure full compability. For production, please stay on Burp Suite Professional stable branch.
By default, Burp is launched in headless mode with the Proxy running on port 8080/tcp (localhost only) and the REST endpoint running on 8090/tcp (localhost only).
15
+
By default, Burp is launched in headless mode with the Proxy running on port 8080/tcp (**localhost only**) and the REST endpoint running on 8090/tcp (**localhost only**).
46
16
47
17
To __run Burp in UI mode__ from the command line, use one of the following commands:
48
18
49
-
With the `bootRun` command:
50
-
```
51
-
gradlew bootRun -Djava.awt.headless=false
52
19
```
53
-
or
54
-
```
55
-
gradlew bootRun -Dheadless.mode=false
56
-
```
57
-
or with the `bootRun` command using the `-PappArgs` to pass args directly to burp suite :
The following command line arguments are used only by the extension to configure the run mode and port number.
105
51
52
+
`--burp.jar=<filaname.jar>` : Loads the Burp jar dinamically, and expose it through REST APIs. This flag is required.
53
+
54
+
`--burp.ext=<filename.{jar,rb,py}` : Loads the given Burp extensions during application startup. This flag can be repeated.
55
+
106
56
`--server.port=<port_number>` : The REST API endpoint is available at the given port number. `--port=<port_number>`
107
57
works as short hand argument.
108
58
@@ -122,7 +72,7 @@ Command line arguments passed to the executable burp-rest-api JAR are forwarded
122
72
`--config-file=<filename>` : Opens the project using the options contained in the selected project configuration file. To
123
73
load multiple project configurations, this argument can be passed more than once with different values.
124
74
125
-
`--user-config-file=<filename>` : Opens the project using the options contained in the selected user configuration file. To
75
+
`--user-config-file=<filename>` : Opens the project using the options contained in the selected user configuration file. To
126
76
load multiple user configurations, this argument can be passed more than once with different values.
127
77
128
78
For more information on Projects, refer to the Burp Suite documentation
@@ -155,18 +105,55 @@ This project also comes with a client (_BurpClient.java_) written in Java for us
155
105
## Credits
156
106
157
107
This project is originally inspired from [Resty-Burp](https://github.com/continuumsecurity/resty-burp
158
-
"continuumsecurity/resty-burp: REST/JSON interface to Burp Suite") and is developed in partnership with [Doyensec](https://www.doyensec.com).
108
+
"continuumsecurity/resty-burp: REST/JSON interface to Burp Suite"), and is developed in partnership with [Doyensec LLC](https://doyensec.com/). <imgsrc="https://www.doyensec.com/images/logo.png"width="300">
159
109
160
110
## Contributing
161
111
162
112
The burp-rest-api project team welcomes contributions from the community. If you wish to contribute code and you have
163
113
not signed our contributor license agreement (CLA), our bot will update the issue when you open a Pull Request. For
164
-
any questions about the CLA process, please refer to our [FAQ](https://cla.vmware.com/faq). For more detailed
165
-
information, refer to [CONTRIBUTING.md](CONTRIBUTING.md).
114
+
any questions about the CLA process, please refer to our [CLA FAQ](https://cla.vmware.com/faq). For more detailed
115
+
information, refer to [CONTRIBUTING.md](CONTRIBUTING.md) and [FAQ.md](FAQ.md).
116
+
117
+
### Develop
118
+
119
+
Upon successfully building the project, an executable JAR file is created.
120
+
The Burp suite JAR can be loaded dinamically through the `--burp.jar=` argument.
121
+
When the JAR is launched, it provides a REST/JSON endpoint to access the Scanner, Spider, Proxy and other
122
+
features of the Burp Suite Professional security tool.
123
+
124
+
#### Prerequisites
125
+
126
+
* Java 8
127
+
* Gradle
128
+
* Licensed Burp Suite Professional version 1.7.x or later from: <http://portswigger.net/burp/>
129
+
130
+
131
+
#### Build & Run
132
+
133
+
1.[Download](https://portswigger.net/burp/download.html) the Professional edition of Burp Suite.
134
+
2. The project can be run either by running the Gradle Spring `bootRun` command or by directly launching the JAR
135
+
created from building the project:
136
+
3. OPTIONAL: Create a `lib` folder under the project directory and place the Burp Suite JAR file into it and rename it to "burpsuite_pro.jar" in order to run the integration tests.
0 commit comments