Search code examples
apirestoutlookoutlook-restapihttp-status-code-500

Outlook REST API calls return internal server error 500


When using the Microsoft Outlook REST API to make calls to my own Outlook Calendar, I receive an internal server error 500. My access tokens are apparently fine and everything, but I still get this error. I thought there might be a problem somewhere in my script, but I get the error even when using the Outlook OAuth Sandbox. I understand that certain Outlook accounts are not REST API-enabled yet, but according to the documentation,

making API calls to mailboxes that are not yet upgraded will return a MailboxNotEnabledForRESTAPI or MailboxNotSupportedForRESTAPI error code.

I do not receive those error codes. So does anyone know what the problem might be?


Solution

  • Sorry to hear that you're having this problem. We recently discovered a scenario where Outlook.com accounts that haven't been migrated onto the REST-enabled platform will get this error instead of the expected MailboxNotEnabledForRESTAPI or MailboxNotSupportedForRESTAPI code. It sounds like your account hasn't been migrated yet. This is a problem on our side in that we're not returning the correct error.

    In the meantime if you need an account to test against, if you create a new account it should be REST-enabled right away.