Microsoft APIsupport.microsoft.com ↗
Retrieve the latest Windows 11 25H2 KB updates from support.microsoft.com, including KB number, release date, and known issues per update.
What is the Microsoft API?
The Microsoft Support KB Updates API exposes 1 endpoint, get_latest_kbs, that returns structured data from the Windows 11 version 25H2 update history page. Each response object includes the full update name, KB number, release date, and any known issues pulled from each update's detail page. Developers can use the limit parameter to cap how many of the most recent KB entries are returned.
curl -X GET 'https://api.parse.bot/scraper/f2263cfd-0109-4544-befe-60ae7d729505/get_latest_kbs?limit=3' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace support-microsoft-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: MicrosoftUpdates SDK — bounded, re-runnable; every call capped."""
from parse_apis.support_microsoft_com_api import MicrosoftUpdates, ParseError
client = MicrosoftUpdates()
# List the latest KB updates with known issues
for kb in client.kb_updates.list(limit=3):
print(kb.name, kb.release_date)
if kb.known_issues:
for issue in kb.known_issues[:2]:
print(f" Issue: {issue[:80]}...")
else:
print(" No known issues")
# Get just the most recent KB
latest = client.kb_updates.list(limit=1).first()
try:
print(latest.kb_number, latest.release_date, len(latest.known_issues), "issues")
except ParseError as e:
print(f"error: {e}")
print("exercised: kb_updates.list")
Retrieves the latest KB updates from the Windows 11 version 25H2 update history page. Each KB includes its full name, KB number, release date, and any known issues documented on its detail page. Known issues are fetched by following each KB's detail link and extracting the 'Known issues in this update' section. Results are ordered newest-first.
| Param | Type | Description |
|---|---|---|
| limit | integer | Maximum number of latest KB updates to retrieve. |
{
"type": "object",
"fields": {
"kbs": "array of KB update objects, each containing name, kb_number, release_date, and known_issues"
},
"sample": {
"data": {
"kbs": [
{
"name": "July 14, 2026—KB5101650 (OS Builds 26200.8875 and 26100.8875)",
"kb_number": "KB5101650",
"known_issues": [],
"release_date": "July 14, 2026"
},
{
"name": "June 23, 2026—KB5095093 (OS Builds 26200.8737 and 26100.8737) Preview",
"kb_number": "KB5095093",
"known_issues": [
"Microsoft Office applications might fail to open from certain third-party apps..."
],
"release_date": "June 23, 2026"
},
{
"name": "June 9, 2026—KB5094126 (OS Builds 26200.8655 and 26100.8655)",
"kb_number": "KB5094126",
"known_issues": [
"Microsoft Office applications might fail to open from certain third-party apps...",
"Deleting from Recycle Bin displays an internal file name..."
],
"release_date": "June 9, 2026"
}
]
},
"status": "success"
}
}About the Microsoft API
What the API returns
The get_latest_kbs endpoint returns an array of KB update objects sourced from the Windows 11 version 25H2 update history on support.microsoft.com. Each object in the kbs array contains four fields: name (the full display name of the update), kb_number (the KB article identifier such as KB5055627), release_date (when Microsoft published the update), and known_issues (a list of documented issues extracted from each KB's individual detail page).
Parameters and filtering
The single optional input is limit, an integer that controls how many KB update objects are returned. When omitted, the endpoint returns all available KB entries from the history page. Setting limit to a small value like 5 is useful when you only need to check the most recent patches without processing the full update history.
Known issues data
The known_issues field is populated by following each KB's linked detail page and extracting the documented issues section. This means the field reflects whatever Microsoft has currently listed for that update, including issues that are still under investigation or have been resolved. If Microsoft has not documented any known issues for a given KB, the field will be empty.
The Microsoft API is a managed, monitored endpoint for support.microsoft.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when support.microsoft.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official support.microsoft.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Alert a sysadmin Slack channel when a new KB number appears in the 25H2 update history
- Build a changelog feed that surfaces Windows 11 25H2 release dates for patch management dashboards
- Cross-reference known_issues fields to detect if a newly released KB affects a specific software dependency
- Populate an internal IT wiki with the latest KB names and release dates automatically
- Monitor known_issues across multiple KBs to track whether open issues have been resolved between releases
- Generate a weekly digest of Windows 11 25H2 patches for enterprise desktop support teams
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Microsoft offer an official developer API for KB update data?+
What does the known_issues field actually contain?+
known_issues field contains the issues Microsoft has listed on each KB's individual detail page at the time the endpoint is called. This can include issues still under investigation, issues with documented workarounds, and issues marked as resolved. If Microsoft lists no known issues for a KB, the field is empty.