How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Microsoft Office Integration HistoricalStatus API

The HistoricalStatus API from Microsoft Office Integration — 1 operation(s) for historicalstatus.

Microsoft Office Integration HistoricalStatus API is one of 6 APIs that Microsoft Office Integration publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 6 JSON Schema definitions.

Tagged areas include HistoricalStatus. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 6 JSON Schemas.

This API exposes 1 operation across 1 path, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 4 base URLs: https://manage.office.com/api/v1.0/{tenantId}/activity/feed, https://manage-gcc.office.com/api/v1.0/{tenantId}/activity/feed, https://manage.office365.us/api/v1.0/{tenantId}/activity/feed, https://manage.protection.apps.mil/api/v1.0/{tenantId}/activity/feed.

1 operations 1 paths 2 schemas 1 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Servers
https://manage.office.com/api/v1.0/{tenantId}/activity/feed
https://manage-gcc.office.com/api/v1.0/{tenantId}/activity/feed
https://manage.office365.us/api/v1.0/{tenantId}/activity/feed
https://manage.protection.apps.mil/api/v1.0/{tenantId}/activity/feed
Authentication
HTTP Bearer
Contact
Resource Areas
1

Authentication & Security 1

Microsoft Office Integration HistoricalStatus API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — OAuth2 JWT access token obtained from Microsoft Entra ID with ActivityFeed.Read claim.

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 GET. Each is listed below with its method, path, parameters, and response codes.

HistoricalStatus 1
GET
/HistoricalStatus
Microsoft Office Integration Get Historical Status
getHistoricalStatus 3 params → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are WorkloadStatus (7 properties), FeatureStatus (3 properties). Each schema is shown below with its type and property counts.

WorkloadStatus
object
7 properties
FeatureStatus
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

microsoft-office-integration-historicalstatus-api-openapi.yml Raw ↑

Other APIs Microsoft Office Integration publishes across the network.

Microsoft Office Integration CurrentStatus API
Microsoft Office Integration Messages API
Microsoft Office Integration Resources API
Microsoft Office Integration Services API
Microsoft Office Integration Subscriptions API
Where this information came from

This is an independent, third-party profile of Microsoft Office Integration HistoricalStatus API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.