OsborneProPATCH INTELLIGENCE

DEVELOPER REFERENCE

Patch intelligence API.

Read-only update, CVE and prerequisite queries for your change workflows.

Connection

Base URL: Loading…

Checking API availability…

The API requires TLS 1.3. Your client and any TLS-inspecting proxy must support it. Read access is public during beta; no API key is needed. Customer profiles and environment names remain in your browser.

Results describe the latest published Microsoft snapshot, not a device scan or an installation guarantee. Check generatedAt (or sourceGeneratedAt on health) for freshness. Changes appear after collection and publication.

Endpoints

GET endpointQuery parameters
/v1/healthConnection status and source timestamp.
/v1/updatesRepeated product; optional architecture (x64, x86, ARM64), month (YYYY-MM), q (KB/CVE/product/build), limit (1–500, default 100), offset.
/v1/cves/{CVE-ID}Optional repeated product, architecture, month. Returns product-specific fixing KB records in the loaded snapshot.
/v1/prerequisitesRequired target (KB number) and product; optional baseline (KB or build) and architecture. Returns documented requirements and build comparisons.

Examples from the current snapshot

Select a saved environment in the workspace to generate requests for its OS versions. These examples use an update from the current dataset.

Loading examples…

Pagination, errors & limits

For updates, keep the same filters and follow nextOffset until it is null. total counts matching OS/KB records, not unique KBs. Save the response timestamp with your change request.

400: invalid parameters. 404: unknown route. 413: narrow the request or reduce the page size. 429: back off and retry with jitter. 503: source snapshot unavailable. An empty result is not proof that an OS has no updates or prerequisites. The starting service throttle is five requests/second with burst ten; avoid polling unnecessarily.

The API has no browser home page at its root URL. Use one of the /v1/ endpoints above. Cross-origin browser access is enabled for the OsbornePro website. Server-side integrations can call the API directly.

ServiceNow and Freshservice exports are reviewable drafts, not automatic ticket submissions. No customer credentials should be sent to this API.