Research Academy My account Customers About Blog Careers Legal Contact Resellers

DAST

Adding a single API

  • Last updated: November 20, 2026

  • Read time: 6 Minutes

This page explains how to create a site for a single API. You can add an API definition by uploading a file or providing a URL.

Adding API definitions by uploading a file

When you upload an API definition file, Burp Suite DAST uses that version for every scan until you upload a new one.

To add an API definition by uploading a file:

  1. Go to Sites and select Add a new site.

  2. Select API from the Site type panel.

  3. Enter a unique Site name.

  4. To add the site to an existing folder, select from the Site folder drop-down menu. Leave the field blank to create the site at the top level of the site tree.

  5. Click Select file and select the definition file to upload.

  6. If you upload a Postman Collection, you are given the option to upload a Postman environment file. Burp Suite DAST applies the environment variables to your Postman Collection on every scan. Click Add environment file and select your environment file.

  7. For an OpenAPI definition or SOAP WSDL without a full server URL, enter a Base URL and click Apply.

  8. If you upload a GraphQL schema, enter the GraphQL endpoint URL and click Apply.

Postman environments

A Postman environment sets the values of variables in your collection, such as hosts and credentials. Burp Suite DAST keeps the environment as a separate file and applies it on every scan.

Environment values take priority over all variables in the collection, including folder and request variables. This matches how Postman applies an environment. Burp Suite DAST also extracts credentials from the environment for detected authentication schemes.

To replace or remove the environment without adding the collection again:

  1. Go to Sites and select your API site.

  2. Select the Details tab and click Edit.

  3. Under API definition, click the trash icon next to Environment file.

  4. (Optional) Click Add environment file and select your new environment file.

  5. Click Save.

Note

Before Burp Suite DAST 2026.11.2, Burp Suite DAST merged the environment into the collection. Sites created this way keep their merged values and show the environment as read-only. To change a merged environment, remove the collection and upload it again.

Base URLs for OpenAPI and WSDL files

Some API definition files don't say where the API is hosted. For example:

  • An OpenAPI definition has relative server URLs, or no server URLs.

  • A SOAP WSDL has placeholder or relative service addresses.

To scan these endpoints, enter the URL where your API is hosted as the Base URL. This must be a full http:// or https:// URL.

Burp Suite DAST sends endpoints without a full server URL to the base URL. If the definition gives a full server URL, Burp Suite DAST uses it instead. The site overview shows the base URL.

If an OpenAPI definition has no full server URL, a message under Base URL asks you to enter one. You can't save the site until you click Apply. Without a base URL, Burp Suite DAST skips WSDL ports that don't have a full service address.

Note

Burp Suite DAST can't add a WSDL file if none of its service addresses are full URLs. Edit the file to give at least one full service address, then enter a base URL for the others.

Base URLs require Burp Suite DAST 2026.11.2 or later.

GraphQL schemas

You can upload a GraphQL schema to scan a GraphQL API that has introspection switched off. Upload the schema as an SDL file (.graphql), or as a saved introspection result in JSON format.

A schema doesn't include the URL of its endpoint, so you need to enter the GraphQL endpoint URL. Burp Suite DAST lists each query and mutation in the schema as an endpoint. It doesn't scan subscriptions.

Note

Uploading GraphQL schemas requires Burp Suite DAST 2026.11.2 or later.

Adding API definitions by providing a URL

When you provide a URL, Burp Suite DAST uses the latest version of the API definition for every scan. If the definition file is on a server that requires authentication, you can add host credentials. You can validate that the URL is reachable and the file can be parsed.

To add an API definition by providing a URL:

  1. Go to Sites and select Add a new site.

  2. Select API from the Site type panel.

  3. Enter a unique Site name.

  4. To add the site to an existing folder, select from the Site folder drop-down. Leave the field blank to create the site at the top level of the site tree.

  5. Click Host URL and enter the URL where your API definition file is hosted. To add an MCP server, enter the URL of its endpoint.
  6. (Optional) If your API definition file is on a server that requires authentication, click Add host credentials and enter the credentials.

  7. Click Validate to confirm that Burp Suite DAST can reach the URL and parse the API definition. If successful, the Endpoints tab lists the parsed endpoints.

Note

If you provide a URL for a Postman Collection, Burp Suite DAST also extracts the credentials for detected authentication schemes. They are shown in the Authentication tab.

If you manually edit the credentials for your site, they may be overwritten if you later click Validate.

Adding an MCP server

You can scan an MCP (Model Context Protocol) server to test the tools, prompts, and resources it provides. An MCP server doesn't have a definition file, so Burp Suite DAST gets this list from the server.

To add an MCP server, follow the steps in Adding API definitions by providing a URL. Enter the URL of the server's endpoint as the Host URL, for example https://mcp.example.com/mcp. If the server requires authentication, click Add host credentials and enter the credentials.

When you click Validate, Burp Suite DAST lists the server's tools, prompts, resources, and resource templates as endpoints. Each scan connects to the server again, so it tests what the server provides at the time of the scan.

Burp Suite DAST supports MCP servers that use the Streamable HTTP transport. Burp Suite DAST shows an error if the URL:

  • Uses the deprecated HTTP+SSE transport.

  • Isn't an MCP server.

Note

Scanning MCP servers requires Burp Suite DAST 2026.11.2 or later.

Adding captured traffic as an API definition

You can use captured traffic to create an API site without writing an API definition. Burp Suite DAST lists each distinct recorded request as an endpoint.

To add a Burp XML or HAR file, upload the file or provide its URL.

Burp XML files

You can use an XML file saved from Burp Suite Professional to scan captured HTTP requests in Burp Suite DAST.

To save the file:

  1. Select the requests you want to scan in Proxy > HTTP history or the site map.

  2. Right-click the selection and click Save items.

  3. Make sure Base64-encode requests and responses is selected.

  4. Enter a file name ending in .xml and click Save.

For more information about saving requests, see Save items.

Base64 encoding preserves the recorded request data. Without it, saved request bodies may differ from the originals. The parse report warns when this may happen.

Burp Suite DAST combines duplicate requests into one endpoint. It skips items without a usable URL or request and names them in the parse report.

Burp Suite DAST sends each request with its recorded credentials. Authentication that you configure for the site replaces any recorded header with the same name. Burp Suite DAST doesn't detect authentication schemes from recorded headers.

Note

Scanning Burp XML files requires Burp Suite DAST 2026.10.3 or later.

HAR files

Export a HAR file from your browser's developer tools or a proxy. After adding the file, review the requests on the Endpoints tab.

Requests for static assets start deselected. To include a request for an image, stylesheet, script, or font, select its checkbox.

Burp Suite DAST doesn't support:

  • WebSocket entries.

  • Replaying requests in their recorded order.

  • Editing recorded values before scanning.

Saving and scanning your site

Once you've finished creating your site, click Save.

Burp Suite DAST adds the new API to the site tree and prompts you to schedule a scan.

Related pages