Bing Webmaster Tools
Read Bing search traffic, crawl errors and sitemaps, and submit URLs for indexing.
Connect it with: API key. Bing Webmaster Tools's own documentation: https://learn.microsoft.com/en-us/bingwebmaster/getting-access.
What agents can do
Connect Bing Webmaster Tools so the agents working your tasks can reach it. With it connected, they can:
- List the sites in your Bing Webmaster Tools account and whether each is verified.
- Read search query and page traffic stats (clicks, impressions, position) for a site.
- Read crawl errors and crawl stats after a release changes URLs.
- Submit new or changed URLs and sitemaps so Bing recrawls them.
Before you start
- A site added and verified in Bing Webmaster Tools (bing.com/webmasters), on the account whose API key you use.
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with Bing Webmaster Tools
Jaah connects to Bing Webmaster Tools with an API key, not with a sign-in button.
Connect with an API key
Find each value first:
- API key: bing.com/webmasters > Settings (gear, top right) > API access > accept the terms on first use > API Key > Generate API Key. Bing allows one key per user.
Then add it to Jaah:
- In Jaah, open Secrets, select New, and pick the Bing Webmaster Tools card.
- Name the secret and choose who can use it.
- Fill in API key.
- Select Save. Jaah tests the secret straight away (see Test the connection).
Jaah encrypts what you type and never shows it again — not to you, and not to an admin.
Use your own OAuth app
Not used: Jaah connects to Bing Webmaster Tools with an API key, not through an OAuth app.
Test the connection
Select Test on the secret. Jaah calls Bing Webmaster Tools's API once (GET https://ssl.bing.com/webmaster/api.svc/json/GetUserSites) with the stored values, and shows whether Bing Webmaster Tools accepted it, or which value Bing Webmaster Tools refused and the status it answered. Jaah also tests automatically when you save or reconnect.
The last result and its time stay on the secret's page, so you can see whether it still works without testing again.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
A key connection hands the agent its fields: api_key.
Tell the agent in your task description which secret to use, for example “use the Bing Webmaster Tools secret org/bing-webmaster”.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Bing Webmaster Tools once the test passes. Steps: Replace or delete a secret.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Bing Webmaster Tools's side too, revoke or delete the key at Bing Webmaster Tools.
Limitations
- One API key per Bing user: generating a new key retires the old one, so every place that uses it must be replaced at once.
- URL submission has a daily quota per site that Bing sets; agents see the remaining quota and stop when it is spent.
- The key reaches every site on the account; Bing has no per-site key.
- Agents can do only what the connected Bing Webmaster Tools account allows.
Troubleshooting
Test says Bing Webmaster Tools rejected the API key (400)
The key was regenerated or mistyped. Open Settings > API access, copy the current key and select Replace on the secret.
Test says credentials accepted but an agent sees no sites
The key belongs to a Bing account with no sites. Add and verify the site in Bing Webmaster Tools, or use the key of the account that owns it.
An agent's URL submission fails with a quota error
The site's daily submission quota is spent. Wait for the next day, or submit a sitemap instead.
Still stuck? Select Test and read the result: it names the value Bing Webmaster Tools refused and the status it answered.
FAQ
Can I import my sites from Google Search Console?
Yes, in Bing Webmaster Tools under Add a site > Import from Google Search Console. Do it there before connecting.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one Bing Webmaster Tools account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.