# Bing Webmaster Crawl Stats (`bing-webmaster.crawl_stats`)

Daily Bingbot crawl figures for a site in the connected Bing Webmaster Tools account: pages crawled and indexed, status codes, robots.txt blocks and errors.

Docs: https://primaryapi.com/docs/api-reference/bing-webmaster/crawl_stats

- Endpoint: `POST https://api.primaryapi.com/v1/run/bing-webmaster.crawl_stats`
- Category: Search & SEO · Platform: `bing-webmaster` · Kind: search · Status: live
- Price: 1 credit per call. Every call costs the same, including calls that were retried automatically.
- Billing unit: per successful call
- Reliability: routed to a healthy upstream and retried automatically when an attempt fails; live 30-day status: `GET https://api.primaryapi.com/v1/status/apis?sku=bing-webmaster.crawl_stats`
- Execution: synchronous (answers 202 only if it outlives the wait window)

## Input

| Field | Type | Required | Default | Constraints | Description |
|---|---|---|---|---|---|
| `siteUrl` | string | yes |  | max 2048 chars | The site as Bing Webmaster Tools lists it (bing-webmaster.sites), e.g. "https://www.example.com/". |
| `startDate` | string | no |  | pattern: ^\d{4}-\d{2}-\d{2}$ | Only rows dated on or after this day (YYYY-MM-DD). Optional. |
| `endDate` | string | no |  | pattern: ^\d{4}-\d{2}-\d{2}$ | Only rows dated on or before this day (YYYY-MM-DD). Optional. |
| `limit` | integer | no | 100 | 1–500 | Maximum number of results to return (1-500, default 100). |
| `cursor` | string | no |  |  | Opaque pagination cursor: pass the previous response's nextCursor. |
| `connection` | string | no |  | max 200 chars | Which connected account to use when the workspace has several for this provider: the customId you gave it (exact), its connection id ("con_…"), its handle (login, email or @handle) or its name. Optional; prefer the customId or id, which never match two accounts. |

Unknown fields are rejected with `400 invalid_input`. The routing controls `preferLatencyUnderMs` and `maxCredits` may be sent in the same JSON body.

## Output

When `output.found` is `true`, `output.data` has this shape:

| Field | Type | Description |
|---|---|---|
| `days` | object[] |  |
| `days[].date` | string \| null | The day (YYYY-MM-DD) |
| `days[].crawledPages` | number \| null | Pages Bingbot crawled |
| `days[].crawlErrors` | number \| null |  |
| `days[].inIndex` | number \| null | Pages in the Bing index |
| `days[].inLinks` | number \| null | Inbound links Bing knows of |
| `days[].code2xx` | number \| null |  |
| `days[].code301` | number \| null |  |
| `days[].code302` | number \| null |  |
| `days[].code4xx` | number \| null |  |
| `days[].code5xx` | number \| null |  |
| `days[].allOtherCodes` | number \| null |  |
| `days[].blockedByRobotsTxt` | number \| null |  |
| `days[].containsMalware` | number \| null |  |
| `nextCursor` | string \| null |  |

When the thing you asked about does not exist (or a search matches nothing) the call still succeeds: `output.found` is `false`, `output.data` is `null` and `output.reason` says why (`not_found`, `private`, `no_results`, …). Misses are free unless the notes below say misses are billed.

Pagination: pass the previous response’s `nextCursor` as `cursor` to get the next page; `nextCursor: null` means there are no more results.

## Example request

```bash
curl -sS -X POST "https://api.primaryapi.com/v1/run/bing-webmaster.crawl_stats" \
  -H "Authorization: Bearer $PRIMARYAPI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"siteUrl":"https://www.example.com/"}'
```

## Example response

_Values are placeholders that follow the output schema; `credits` is what this call would cost at the usual price._

```json
{
  "output": {
    "found": true,
    "data": {
      "days": [
        {
          "date": "2011-09-16",
          "crawledPages": 0,
          "crawlErrors": 0,
          "inIndex": 1000,
          "inLinks": 2048,
          "code2xx": 9998,
          "code301": 0,
          "code302": 0,
          "code4xx": 1,
          "code5xx": 1,
          "allOtherCodes": 0,
          "blockedByRobotsTxt": 0,
          "containsMalware": 5
        }
      ],
      "nextCursor": null
    }
  },
  "provider": "PrimaryAPI",
  "credits": 1,
  "items": 1,
  "requestId": "req_01JBXK6Y2N9V8T4R3Q2P1M0A7Z",
  "nextCursor": null
}
```

## Pricing and reliability

- Usual price: 1 credit per call
- Price ceiling: the usual price, even when a call is retried. A quote’s `maxCredits` is the most a given call can cost; the `maxCredits` routing control caps it per call
- Live 30-day status, success rate, uptime and latency: `GET https://api.primaryapi.com/v1/status/apis?sku=bing-webmaster.crawl_stats`

## Errors to handle

`invalid_input`, `unauthorized`, `insufficient_balance`, `key_limit_reached`, `trial_cap_reached`, `forbidden`, `not_found`, `idempotency_conflict`, `rate_limited`, `all_sources_failed`, `service_unavailable`, `timeout`. See https://primaryapi.com/docs/errors.

## Notes

Needs the Read Bing Webmaster Tools capability (webmaster_read). Runs as your connected Bing Webmaster Tools account (Bing sign-in or a pasted Bing API key). Bing returns the whole history it keeps for the site; startDate/endDate narrow it and nextCursor pages through it. Dates are calendar days (YYYY-MM-DD). A site the account has not verified is a miss with reason no_access. Bing keeps crawl statistics for the last 6 months and refreshes them daily.

