> ## Documentation Index
> Fetch the complete documentation index at: https://docs.parse.bot/llms.txt
> Use this file to discover all available pages before exploring further.

# Dashboard guide

> Build, test, and revise APIs in the Parse dashboard — then call them from your code

The fastest way to build an API is in the [dashboard](https://parse.bot). You paste a URL, Parse builds the API, and you test and revise it visually before wiring it into your app. This guide walks the full UI flow.

## 1. Create a new API

Click **+ New** in the top-left of the nav. Paste the URL you want data from, describe what you need, and Parse either matches an existing API or builds a new one.

![New API submission modal](https://mintcdn.com/parse/bS5HzXFQPEeID5Ct/images/dashboard/new-api-modal.png?fit=max\&auto=format\&n=bS5HzXFQPEeID5Ct\&q=85\&s=c06418c79dde7b46b842896a48ff4b2c)

The New API dialog — paste a URL, describe the data, and build.

The **Contribute to marketplace** toggle controls whether your API stays linked to the shared canonical for its domain:

* **On** (default) — the build is **free**, and your API stays in sync with the canonical so you can [pull upstream improvements](https://docs.parse.bot/updates.md).
* **Off** — a fully private, desynced API. This build is charged, and the choice is permanent.

Builds typically take \~60 seconds. You'll watch progress live, and the API lands in **My APIs**. On a new build, endpoints are saved as they're verified, so a build that fails partway still keeps the endpoints that already worked. (Revisions to an existing API still apply their changes at completion — see [step 4](#4-revise-in-plain-english).)

If the site requires a login, the build is interactive: it will pause to ask for credentials, a 2FA code, or a clarifying question. Answer promptly — prompts expire (roughly 5 minutes for credentials and 2FA codes, 15 for questions) and an unanswered build parks. We recommend a test account for initial builds where the site offers one: see the [security overview](https://docs.parse.bot/authenticated-apis.md#security-overview) for how credentials are handled and [interactive prompts](https://docs.parse.bot/authenticated-apis.md#during-the-build-interactive-prompts) for the full list.

## 2. Or start from an existing one

Thousands of sites are already built. Open **Discover** to search the [marketplace](https://docs.parse.bot/marketplace.md) and fork or subscribe to an existing API instead of building from scratch.

![Marketplace discover page](https://mintcdn.com/parse/bS5HzXFQPEeID5Ct/images/dashboard/marketplace-discover.png?fit=max\&auto=format\&n=bS5HzXFQPEeID5Ct\&q=85\&s=6d7e3a1978855c73a5d3687fdbc2c5a1)

Discover — search, filter by category, and pick a pre-built API.

## 3. Test endpoints in the browser

Open any API to see its endpoints. Pick one, fill in the parameters, and hit **Send request** to run it live and see the real response — no code required. This is the quickest way to confirm an endpoint returns what you expect.

![API detail with endpoint tester and revision bar](https://mintcdn.com/parse/bS5HzXFQPEeID5Ct/images/dashboard/api-detail-endpoints.png?fit=max\&auto=format\&n=bS5HzXFQPEeID5Ct\&q=85\&s=a6c63fa5871c7cbcb7d7c2e263b402d3)

An API's detail view — choose an endpoint, fill parameters, and run it live.

## 4. Revise in plain English

Not quite right? Use the **revision bar** at the bottom of any API page. Describe the change — "add a search-by-category endpoint", "include the publish date in get\_paper" — and Parse revises the API for you. Mention a specific endpoint with `@`. Revisions run the same way a build does; the `scraper_id` stays the same.

## 5. Grab a code snippet

Once it works, scroll to **Now plug it in**. Copy a ready-to-run snippet — cURL, Python, TypeScript, an MCP config, or the OpenAPI spec — with your API's real URL and IDs already filled in.

![Code snippets: cURL, Python, TypeScript, MCP, OpenAPI](https://mintcdn.com/parse/bS5HzXFQPEeID5Ct/images/dashboard/api-code-snippets.png?fit=max\&auto=format\&n=bS5HzXFQPEeID5Ct\&q=85\&s=a9e7c2e725d69811d11f52a54aaea441)

Copy a ready-to-run snippet, or wire the API through MCP.

The snippet calls the same execution endpoint documented throughout these docs:

```
POST https://api.parse.bot/scraper/{scraper_id}/{endpoint_name}
```

## Next steps

> [card] [Quickstart](https://docs.parse.bot/quickstart.md)
>
> Call your endpoints from code, end to end

> [card] [Code examples](https://docs.parse.bot/examples.md)
>
> Full Python & JavaScript clients

> [card] [Updates](https://docs.parse.bot/updates.md)
>
> Pull upstream improvements into your API

> [card] [MCP Server](https://docs.parse.bot/mcp.md)
>
> Connect an AI agent to all your APIs


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.