# Quickstart

Four steps from zero to your first compromised records. You need an API token with Data Breaches permission.

## 1. Get your token

Find your API `token` in your Webz.io dashboard. Your account must have Data Breaches access and be authorized for the domain you search - without it, requests return `401` or `403`.

## 2. Run a query

`GET`

```bash
https://api.webz.io/breaches?token=YOUR_TOKEN&email_domain=example.com
```

Every request needs a `token` and at least one of `email`, `email_domain`, `login_domain`, or `domain`.

## 3. Read the response

The JSON response contains a `records` array plus paging fields:

```json
{
  "records": [ ... ],
  "totalResults": 1230,
  "moreResultsAvailable": 1130,
  "next": "/breaches?token=YOUR_TOKEN&email_domain=example.com&next=CURSOR",
  "requestsLeft": 989,
  "totalResultsVerified": true
}
```

## 4. Get the next page

Append the `next` value to `https://api.webz.io` and call it again. Repeat until `moreResultsAvailable` reaches `0`. See [Pagination](data-breach-pagination).

That's it - you are up and running. Next, learn the [Search Scope](data-breach-scope) and [Filters](data-breach-filters).

> [!NOTE]
> Responses return up to **100** records each. By default a search covers the last 365 days - see [Time Range](data-breach-time-range).