Share via

GetNewAccessToken overview

  • Article

You must set the new EndPoints property in response to the existing GetNewAccessToken request. The contents of this property should be a nested JSON-formatted object. The object should have the following properties, with values that exactly match what would be returned in response to a CheckFileInfo request:

  • RealTimeChannelEndpointUrl
  • OfficeCollaborationServiceEndpointUrl

Sample response

The following sample response includes the new JSON properties:

{
  "Bootstrap": {
    "EcosystemUrl": "http://.../wopi*/ecosystem?access_token=",
    "UserId": "User ID",
    "SignInName": "user@contoso.com",
    "UserFriendlyName": "User Name"
  },
  "AccessTokenInfo": {
    "AccessToken": "1234567890abcdef",
    "AccessTokenExpiry": 1234567890
  },
  "EndPoints": {
    "RealTimeChannelEndpointUrl": "http://rtc",
    "OfficeCollaborationServiceEndpointUrl": "http://ocs"
  }
}

Next steps

  • Learn what's new in the CheckFileInfo coauthoring extensions.
  • Learn what's new in the WOPI locks coauthoring extensions.