# Bing Webmaster Submit URL (`bing-webmaster.submit_url`)

Submits one URL of a site to Bing for crawling and indexing (a change made with the connected Bing Webmaster Tools account; uses its URL quota).

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

- Endpoint: `POST https://api.primaryapi.com/v1/run/bing-webmaster.submit_url`
- Category: Search & SEO · Platform: `bing-webmaster` · Kind: lookup · 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.submit_url`
- 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/". |
| `url` | string | yes |  | max 2048 chars | The page to submit, e.g. "https://www.example.com/new-page". It must be on the site. |
| `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 |
|---|---|---|
| `siteUrl` | string |  |
| `url` | string |  |
| `submitted` | true |  |

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.

## Example request

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

## 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": {
      "siteUrl": "https://www.example.com/",
      "url": "https://www.example.com/url1.html",
      "submitted": true
    }
  },
  "provider": "PrimaryAPI",
  "credits": 1,
  "items": 1,
  "requestId": "req_01JBXK6Y2N9V8T4R3Q2P1M0A7Z"
}
```

## 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.submit_url`

## 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

WRITE: submits the URL to Bing as the connected Bing Webmaster Tools account and uses one URL of its daily and monthly quota (see bing-webmaster.url_submission_quota). Needs the Manage Bing Webmaster Tools capability (webmaster_manage). The URL must be on the site. A site the account has not verified is a miss with reason no_access and nothing is submitted.

