{"id":2081,"date":"2013-07-22T08:59:35","date_gmt":"2013-07-22T08:59:35","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/bharry\/2013\/07\/22\/rest-api-for-team-rooms\/"},"modified":"2013-07-22T08:59:35","modified_gmt":"2013-07-22T08:59:35","slug":"rest-api-for-team-rooms","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/bharry\/rest-api-for-team-rooms\/","title":{"rendered":"REST API for Team Rooms"},"content":{"rendered":"

I had someone ask about this so I decided to go ahead and post something.  Below is the contents of a Word doc that describes our REST API for working with Team Rooms.  It should work both on Team Foundation Service and on a public preview of TFS 2013.  Please let me know if you have any feedback on the doc.\nThis is a very early preview and we’ll launch it officially later this year.  It’s also incomplete but it’s a start.  Hopefully it will give you what you need to know to do basic Team Room extensions.  Ultimately we’ll follow up with samples and more but right now we’re trying to get TFS 2013 finished up.\n \nBrian\n \nChatRoom Service <\/b>\nGeneral Information<\/b><\/p>\n\n\n\n\n\n\n\n
Service Name<\/b><\/p>\n<\/td>\n\n

ChatRoom service<\/b><\/p>\n<\/td>\n<\/tr>\n

\n

Area<\/b><\/p>\n<\/td>\n

\n

Chat<\/p>\n<\/td>\n<\/tr>\n

\n

Version<\/b><\/p>\n<\/td>\n

\n

V1<\/b><\/p>\n<\/td>\n<\/tr>\n

\n

Application URL<\/b><\/p>\n<\/td>\n

\n

N\/A<\/p>\n<\/td>\n<\/tr>\n

\n

Account URL<\/b><\/p>\n<\/td>\n

\n

{account}.visualstudio.com\/DefaultCollection\/_apis\/Chat<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

<\/b>\nDescription<\/b>\nThe ChatRoom service allows users to interact with their team chat rooms. The service allows developer-centric users to real-time collaborate with their team.\nThe Team Chat Room must be open for allowing authenticated extensions to communicate. This will allow other services within Microsoft and external 3rd<\/sup> party apps to perform basic operations on the team room such as the following:\n· room-level operations such as create(or delete) rooms, get a list of rooms, etc\n· user-level operations such as join(or leave) a given user from a team room,\n· message-level operations such as post a message, get a list of messages (recent, given day or given time window)\nBy default chat rooms created by the chat service live at the collection level and have no affiliation with a team in TFS. However, we will be automatically creating a chat room for each TFS team. This room will be stored as a team favorite and show up on the team homepage.\nResources<\/b><\/p>\n\n\n\n\n\n\n
Resources<\/b><\/p>\n<\/td>\n\n

Description<\/b><\/p>\n<\/td>\n<\/tr>\n

\n

\/rooms<\/p>\n<\/td>\n

\n

Represents chat room resource container<\/p>\n<\/td>\n<\/tr>\n

\n

<RoomUri>\/users<\/p>\n<\/td>\n

\n

Represents chat users resource container<\/p>\n<\/td>\n<\/tr>\n

\n

<RoomUri>\/messages<\/p>\n<\/td>\n

\n

Represents chat messages resource container<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

API Flows<\/b>\nSome of the common flows are as follows:\nUser joins a given team room to chat<\/b>\nA chat client with a given user’s credentials, gets a list of team rooms, joins a given team room, retrieves transcripts, posts a message to the team room, leaves the team room.<\/p>\n\n\n\n\n\n\n\n\n
Verb<\/b><\/p>\n<\/td>\n\n

Request & Response<\/b><\/p>\n<\/td>\n

\n

API Details<\/b><\/p>\n<\/td>\n<\/tr>\n

\n

GET<\/p>\n<\/td>\n

\n

\/rooms<\/p>\n

· 200: Wrapped array of team room information<\/p>\n<\/td>\n

\n

Get a list of rooms<\/a><\/p>\n<\/td>\n<\/tr>\n

\n

POST<\/p>\n<\/td>\n

\n

\/rooms\/{roomId}\/users<\/p>\n

· 201: User joins the given chat room<\/p>\n<\/td>\n

\n

User joins a given room<\/a><\/p>\n<\/td>\n<\/tr>\n

\n

GET<\/p>\n<\/td>\n

\n

\/rooms\/{roomId}\/messages<\/p>\n

· 200: Wrapped array\/ transcript of chat messages from the given chat room<\/p>\n<\/td>\n

\n

Gets room transcript<\/a><\/p>\n<\/td>\n<\/tr>\n

\n

POST<\/p>\n<\/td>\n

\n

\/rooms\/{roomId}\/messages<\/p>\n

· 201: Message posted to the given chat room<\/p>\n<\/td>\n

\n

Send a message<\/a><\/p>\n<\/td>\n<\/tr>\n

\n

DELETE<\/p>\n<\/td>\n

\n

\/rooms\/{roomId}\/users\/me<\/p>\n

· 200: User leaves the given chat room<\/p>\n<\/td>\n

\n

Leave chat room<\/a><\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

NOTE: Streaming APIs will come online at a later date\nUser status<\/b>\nA chat client with a given user’s credentials, would display the list of users currently in the team room. For other regular chat operations, the above API flow works.<\/p>\n\n\n\n\n
Verb<\/b><\/p>\n<\/td>\n\n

Request & Response<\/b><\/p>\n<\/td>\n

\n

API Details<\/b><\/p>\n<\/td>\n<\/tr>\n

\n

GET<\/p>\n<\/td>\n

\n

\/rooms\/{roomId}\/users<\/p>\n

· 200: Wrapped array of users currently online in the given chat room<\/p>\n<\/td>\n

\n

Get list of users statuses<\/a><\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

API Details<\/b>\nThis section has the details for each web API.  Each individual API goes through a status of review, then once approved it will get a status of the initial production release of v1.preview.  This will be covered in more detail in the versioning doc.\nGet Rooms<\/b>\nRetrieve chat rooms in a given account, the account information is retrieved from the URL.<\/p>\n\n\n\n\n\n\n\n
Status<\/b><\/p>\n<\/td>\n\n

V1 <\/p>\n<\/td>\n<\/tr>\n

\n

GET<\/b><\/p>\n<\/td>\n

\n

\/chat\/Rooms<\/p>\n<\/td>\n<\/tr>\n

\n

Params<\/b><\/p>\n<\/td>\n

\n

Check OData filters below<\/p>\n<\/td>\n<\/tr>\n

\n

Response Body<\/b><\/p>\n<\/td>\n

\n

{
  “count”: 2,
  “value”: [<\/p>\n

    {
      “id”: 1,
      “name”: “First Room”,
      “description”: “RoomDescription”,
      “lastActivity”: “2013-04-11T00:32:29.673Z”,
      “isClosed”: false,
      “creatorUserTfId”: “edfab9de-17c2-49ef-99cb-abfc159a1224”,
      “createdDate”: “2013-0411T00:32:29.673Z”
    }<\/p>\n

    {
      “id”: 2,
      “name”: “Updated Room Name”,
      “description”: “Updated Description”,
      “lastActivity”: “2013-04-11T00:32:29.673Z”,
      “isClosed”: false,
      “creatorUserTfId”: “edfab9de-17c2-49ef-99cb-abfc159a1224”,
      “createdDate”: “2013-0411T00:32:29.673Z”
    }
  ]
}<\/p>\n<\/td>\n<\/tr>\n

\n

Return Codes<\/b><\/p>\n<\/td>\n

\n

200:<\/b> OK<\/b> – success<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Create Chat Room<\/b>\nCreate a new chat room in a given account.<\/p>\n\n\n\n\n\n\n\n
Status<\/b><\/p>\n<\/td>\n\n

V1<\/p>\n<\/td>\n<\/tr>\n

\n

POST<\/b><\/p>\n<\/td>\n

\n

\/Chat\/Rooms<\/p>\n<\/td>\n<\/tr>\n

\n

Params<\/b><\/p>\n<\/td>\n

\n

{<\/p>\n

“Name”:”NewRoom”,<\/p>\n

“Description”:”Description1″<\/p>\n

}<\/p>\n<\/td>\n<\/tr>\n

\n

Response Body<\/b><\/p>\n<\/td>\n

\n

{<\/p>\n

“id”:2,”name”:”NewRoom”,<\/p>\n

“description”:”Description1″,<\/p>\n

“lastActivity”:”2013-04-11T00:32,<\/p>\n

“creatorUserTfId”:”edfab9de-17c2-49ef-99cb-abfc159a1224″,<\/p>\n

“createdDate”:”2013-04-11T00:32:29.673Z”<\/p>\n

}<\/p>\n<\/td>\n<\/tr>\n

\n

Return Codes<\/b><\/p>\n<\/td>\n

\n

201:<\/b> Created<\/b> – success<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Get Room Info<\/b>\nGets individual chat room information such as name, description.<\/p>\n\n\n\n\n\n\n\n
Status<\/b><\/p>\n<\/td>\n\n

V1<\/p>\n<\/td>\n<\/tr>\n

\n

GET<\/b><\/p>\n<\/td>\n

\n

\/Chat\/Rooms\/{RoomId}<\/p>\n<\/td>\n<\/tr>\n

\n

Params<\/b><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
\n

Response Body<\/b><\/p>\n<\/td>\n

\n

{<\/p>\n

“id”: 2,<\/p>\n

“name”: “Second Room”,<\/p>\n

“description”: “”,<\/p>\n

“lastActivity”: “2013-03-22T19:53:33.683Z”,<\/p>\n

“isClosed”: false,<\/p>\n

“creatorUserTfId”:”4ea29d8a-00d9-4e76-b798-f6be3b0967c0″,<\/p>\n

“createdDate”: “2013-03-22T19:53:33.683Z”<\/p>\n

}<\/p>\n<\/td>\n<\/tr>\n

\n

Return Codes<\/b><\/p>\n<\/td>\n

\n

200:<\/b> OK<\/b>– success
404: Not Found<\/b>– Room not found<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Update Room Info<\/b>\nUpdates a given chat room’s information such as name, description.<\/p>\n\n\n\n\n\n\n\n
Status<\/b><\/p>\n<\/td>\n\n

V1<\/p>\n<\/td>\n<\/tr>\n

\n

PATCH<\/b><\/p>\n<\/td>\n

\n

\/Chat\/Rooms\/{RoomId}<\/p>\n<\/td>\n<\/tr>\n

\n

Params<\/b><\/p>\n<\/td>\n

\n

{<\/p>\n

“Name”:”New Room Name”,<\/p>\n

“Description”:”Updated Description”<\/p>\n

}<\/p>\n<\/td>\n<\/tr>\n

\n

Response Body<\/b><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
\n

Return Codes<\/b><\/p>\n<\/td>\n

\n

200:<\/b> OK<\/b>– success
404: Not Found<\/b>– Room not found<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Delete a Room <\/b>\nDeletes a given chat room.<\/p>\n\n\n\n\n\n\n\n
Status<\/b><\/p>\n<\/td>\n\n

NOT IMPLEMENTED YET<\/p>\n<\/td>\n<\/tr>\n

\n

DELETE<\/b><\/p>\n<\/td>\n

\n

\/Chat\/Rooms\/{RoomId}<\/p>\n<\/td>\n<\/tr>\n

\n

Params<\/b><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
\n

Response Body<\/b><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
\n

Return Codes<\/b><\/p>\n<\/td>\n

\n

200:<\/b> OK<\/b>– success
404: Not Found <\/b>– Room not found<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Get users in a room<\/b>\nGets a list of currently online users in a given team room<\/p>\n\n\n\n\n\n\n\n
Status<\/b><\/p>\n<\/td>\n\n

V1<\/p>\n<\/td>\n<\/tr>\n

\n

GET<\/b><\/p>\n<\/td>\n

\n

\/Chat\/Rooms\/{RoomId}\/Users<\/p>\n<\/td>\n<\/tr>\n

\n

Params<\/b><\/p>\n<\/td>\n

\n

Odata filters applicable here<\/p>\n<\/td>\n<\/tr>\n

\n

Response Body<\/b><\/p>\n<\/td>\n

\n

{
  “count”: 1,
  “value”: [
    {
      “roomId”: 1,
      “userId”: “b918ff7a-52f7-4bdf-8186-2d5cdbf707d7”,
      “lastActivity”: “2013-04-11T00:43:35.903Z”,
      “joinedDate”: “2013-04-11T00:43:35.903Z”
    }
  ]
}<\/p>\n<\/td>\n<\/tr>\n

\n

Return Codes<\/b><\/p>\n<\/td>\n

\n

200:<\/b> OK<\/b>– success
404: Not Found <\/b>– Room not found<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Get user status info<\/b>\nGets status of a given user in the context of a given chat room. The ‘me’ resource is a special resource to store the currently logged in user.<\/p>\n\n\n\n\n\n\n\n
Status<\/b><\/p>\n<\/td>\n\n

V1<\/p>\n<\/td>\n<\/tr>\n

\n

GET<\/b><\/p>\n<\/td>\n

\n

\/Chat\/Rooms\/{RoomId}\/Users\/UserId or<\/p>\n

\/Chat\/Rooms\/{RoomId}\/Users\/me<\/p>\n<\/td>\n<\/tr>\n

\n

Params<\/b><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
\n

Response Body<\/b><\/p>\n<\/td>\n

\n

{
  “roomId”: 1,
  “userId”: “b918ff7a-52f7-4bdf-8186-2d5cdbf707d7”,
  “lastActivity”: “2013-04-11T00:48:02.69Z”,
  “joinedDate”: “2013-04-11T00:48:02.69Z”
}<\/p>\n<\/td>\n<\/tr>\n

\n

Return Codes<\/b><\/p>\n<\/td>\n

\n

200:<\/b> OK<\/b>– success
404: Not Found <\/b>– Room not found\/ user not present in room<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Join room<\/b>\nJoins the currently authenticated user to a given team room<\/p>\n\n\n\n\n\n\n\n
Status<\/b><\/p>\n<\/td>\n\n

V1<\/p>\n<\/td>\n<\/tr>\n

\n

PUT<\/b><\/p>\n<\/td>\n

\n

\/Chat\/Rooms\/{RoomId}\/Users\/UserId or<\/p>\n

\/Chat\/Rooms\/{RoomId}\/Users\/me<\/p>\n<\/td>\n<\/tr>\n

\n

Params<\/b><\/p>\n<\/td>\n

\n

{
  “UserId”: “b918ff7a-52f7-4bdf-8186-2d5cdbf707d7”
}<\/p>\n<\/td>\n<\/tr>\n

\n

Response Body<\/b><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
\n

Return Codes<\/b><\/p>\n<\/td>\n

\n

200:<\/b> OK<\/b>– success
404: Not Found <\/b>– Room not found<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Leave room<\/b>\nLeaves the currently authenticated user from a given team room<\/p>\n\n\n\n\n\n\n\n
Status<\/b><\/p>\n<\/td>\n\n

Review       (Review, v1.preview, v1, etc…)<\/p>\n<\/td>\n<\/tr>\n

\n

DELETE<\/b><\/p>\n<\/td>\n

\n

\/Chat\/Rooms\/{RoomId}\/Users\/UserId or<\/p>\n

\/Chat\/Rooms\/{RoomId}\/Users\/me<\/p>\n<\/td>\n<\/tr>\n

\n

Params<\/b><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
\n

Response Body<\/b><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
\n

Return Codes<\/b><\/p>\n<\/td>\n

\n

200:<\/b> OK<\/b>– success
404: Not Found <\/b>– Room not found\/ user not present in room<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Post message<\/b>\nPosts a message to a given team room<\/p>\n\n\n\n\n\n\n\n
Status<\/b><\/p>\n<\/td>\n\n

Review       (Review, v1.preview, v1, etc…)<\/p>\n<\/td>\n<\/tr>\n

\n

POST<\/b><\/p>\n<\/td>\n

\n

\/Chat\/Rooms\/{RoomId}\/Messages<\/p>\n<\/td>\n<\/tr>\n

\n

Params<\/b><\/p>\n<\/td>\n

\n

{ <\/p>\n

  “content”: “Message content”<\/p>\n

}<\/p>\n<\/td>\n<\/tr>\n

\n

Response Body<\/b><\/p>\n<\/td>\n

\n

Location header contains message Id<\/p>\n

Rooms\/{RoomId}\/Messages\/{MessageId}<\/p>\n<\/td>\n<\/tr>\n

\n

Return Codes<\/b><\/p>\n<\/td>\n

\n

201:<\/b> Created <\/b>– success
404: Not Found <\/b>– Room not found<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Get chat transcript<\/b>\nGets a given room’s chat messages transcript.<\/p>\n\n\n\n\n\n\n\n
Status<\/b><\/p>\n<\/td>\n\n

Review       (Review, v1.preview, v1, etc…)<\/p>\n<\/td>\n<\/tr>\n

\n

GET<\/b><\/p>\n<\/td>\n

\n

\/Chat\/Rooms\/{RoomId}\/Messages<\/p>\n<\/td>\n<\/tr>\n

\n

Params<\/b><\/p>\n<\/td>\n

\n

Odata params applicable here<\/p>\n<\/td>\n<\/tr>\n

\n

Response Body<\/b><\/p>\n<\/td>\n

\n

{
  “count”: 2,
  “value”: [
    {
      “id”: 97,
      “content”: “First message in the room”,
      “messageType”: “normal”,
      “postedTime”: “2013-04-11T01:01:09.097Z”,
      “postedRoomId”: 1,
      “postedByUserTfid”: “b918ff7a-52f7-4bdf-8186-2d5cdbf707d7”
    },
    {
      “id”: 98,
      “content”: “Hello”,
      “messageType”: “normal”,
      “postedTime”: “2013-04-11T01:01:11.69Z”,
      “postedRoomId”: 1,
      “postedByUserTfid”: “b918ff7a-52f7-4bdf-8186-2d5cdbf707d7”
    }
  ]
}<\/p>\n<\/td>\n<\/tr>\n

\n

Return Codes<\/b><\/p>\n<\/td>\n

\n

200:<\/b> OK<\/b>– success
404: Not Found <\/b>– Room not found<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Get a given message<\/b>\nGets a given message in a given chat room<\/p>\n\n\n\n\n\n\n\n
Status<\/b><\/p>\n<\/td>\n\n

V1<\/p>\n<\/td>\n<\/tr>\n

\n

GET<\/b><\/p>\n<\/td>\n

\n

\/Chat\/Rooms\/{RoomId}\/Messages\/{MessageId}<\/p>\n<\/td>\n<\/tr>\n

\n

Params<\/b><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
\n

Response Body<\/b><\/p>\n<\/td>\n

\n

{
  “id”: 97,
  “content”: “First message in the room”,
  “messageType”: “normal”,
  “postedTime”: “2013-04-11T01:01:09.097Z”,
  “postedRoomId”: 1,
  “postedByUserTfid”: “b918ff7a-52f7-4bdf-8186-2d5cdbf707d7”
}<\/p>\n<\/td>\n<\/tr>\n

\n

Return Codes<\/b><\/p>\n<\/td>\n

\n

200:<\/b> OK<\/b>– success
404: Not Found <\/b>– Room\/Message not found<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Update a given message<\/b>\nUpdates a given message in a given chat room<\/p>\n\n\n\n\n\n\n\n
Status<\/b><\/p>\n<\/td>\n\n

NOT IMPLEMENTED YET<\/p>\n<\/td>\n<\/tr>\n

\n

PATCH<\/b><\/p>\n<\/td>\n

\n

\/Chat\/Rooms\/{RoomId}\/Messages\/{MessageId}<\/p>\n<\/td>\n<\/tr>\n

\n

Params<\/b><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
\n

Response Body<\/b><\/p>\n<\/td>\n

\n

{ <\/p>\n

  “message”: “Message content”<\/p>\n

}<\/p>\n<\/td>\n<\/tr>\n

\n

Return Codes<\/b><\/p>\n<\/td>\n

\n

200:<\/b> OK<\/b>– success
404: Not Found <\/b>– Room\/Message not found<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Delete a given message<\/b><\/p>\n

Deletes a given message in a given chat room<\/p>\n\n\n\n\n\n\n\n
\n

Status<\/b><\/p>\n<\/td>\n

\n

NOT IMPLEMENTED YET<\/p>\n<\/td>\n<\/tr>\n

\n

DELETE<\/b><\/p>\n<\/td>\n

\n

\/Chat\/Rooms\/{RoomId}\/Messages\/{MessageId}<\/p>\n<\/td>\n<\/tr>\n

\n

Params<\/b><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
\n

Response Body<\/b><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
\n

Return Codes<\/b><\/p>\n<\/td>\n

\n

200:<\/b> OK<\/b>– success
404: Not Found <\/b>– Room\/Message not found<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"

I had someone ask about this so I decided to go ahead and post something.  Below is the contents of a Word doc that describes our REST API for working with Team Rooms.  It should work both on Team Foundation Service and on a public preview of TFS 2013.  Please let me know if you […]<\/p>\n","protected":false},"author":244,"featured_media":14617,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[5],"class_list":["post-2081","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-tfs"],"acf":[],"blog_post_summary":"

I had someone ask about this so I decided to go ahead and post something.  Below is the contents of a Word doc that describes our REST API for working with Team Rooms.  It should work both on Team Foundation Service and on a public preview of TFS 2013.  Please let me know if you […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/posts\/2081","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/users\/244"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/comments?post=2081"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/posts\/2081\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/media\/14617"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/media?parent=2081"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/categories?post=2081"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/tags?post=2081"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}