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 Yammer Messages API

The Messages API from Microsoft Yammer — 12 operation(s) for messages.

Microsoft Yammer Messages API is one of 10 APIs that Microsoft Yammer publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Message. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 14 operations across 12 paths. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://www.yammer.com/api/v1.

14 operations 12 paths 0 schemas 2 DELETE10 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://www.yammer.com/api/v1/
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Microsoft Yammer Messages API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2) using the authorizationCode flow. By default, every request must be authenticated.

  • OAuth2 — Yammer OAuth 2.0 legacy tokens or Microsoft Entra tokens. Delegated access only.

Paths & Operations 14

Across 12 paths, the API surfaces 14 operations — 2 DELETE, 10 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Messages 14
GET
/messages/my_feed.json
Get current user's feed messages
getMyFeed → 200
GET
/messages/algo.json
Get algorithmically sorted messages
getAlgoMessages → 200
GET
/messages/following.json
Get messages from followed users
getFollowingMessages → 200
GET
/messages.json
Get messages from user's network feed
listMessages → 200
POST
/messages.json
Post a new message
postMessage body → 201
GET
/messages/sent.json
Get messages sent by the current user
getSentMessages → 200
GET
/messages/private.json
Get private messages received by current user
getPrivateMessages → 200
GET
/messages/received.json
Get messages received by current user
getReceivedMessages → 200
GET
/messages/in_thread/{thread_id}.json
Get messages in a thread
getMessagesInThread 1 param → 200
GET
/messages/in_group/{group_id}.json
Get messages in a group
getMessagesInGroup 1 param → 200
GET
/messages/about_topic/{id}.json
Get messages about a topic
getMessagesAboutTopic 1 param → 200
POST
/messages/liked_by/current.json
Like a message
likeMessage 1 param → 201
DELETE
/messages/liked_by/current.json
Unlike a message
unlikeMessage 1 param → 204
DELETE
/messages/{id}.json
Delete a message
deleteMessage 1 param → 204

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

microsoft-yammer-messages-api-openapi.yml Raw ↑

Other APIs Microsoft Yammer publishes across the network.

Yammer REST API
Microsoft Yammer Files API
Microsoft Yammer Groups API
Microsoft Yammer Networks API
Microsoft Yammer Search API
Microsoft Yammer Subscriptions API
Microsoft Yammer Threads API
Microsoft Yammer Topics API
Microsoft Yammer Users API
Where this information came from

This is an independent, third-party profile of Microsoft Yammer Messages 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.