Creating a registration in virtual event returns 401 Unauthorized

Question

Creating a registration in virtual event returns 401 Unauthorized

Monica Wittwer 0

I am trying to create a new registration for the virtual event with Graph API, but it returns 401, The steps I am performing are:

Create a virtual event (webinar)
Create a presenter
Publish the event

Up to this point, everything works fine, but when I try to create a registration for the event, it returns 401, I already have added the delegated permission VirtualEvent.ReadWrite and app permission VirtualEventRegistration-Anon.ReadWrite.All and the access token does have these permissions.

scopes which I am passing to generate the access token are as below

offline_access https://graph.microsoft.com/.default

This is the request

curl --location 'https://graph.microsoft.com/v1.0/solutions/virtualEvents/webinars/{webinarId}/registrations' \
--header 'Content-Type: application/json' \
--header 'Authorization: ••••••' \
--data '{
  "firstName":"John",
  "lastName":"Doe",
  "email": "john.doe@example.com"
  "preferredTimezone":"Pacific Standard Time",
  "preferredLanguage":"en-us",
}'

and this is the response I receive

{
    "error": {
        "code": "Unauthorized",
        "message": "Unauthorized",
        "innerError": {
            "date": "2025-02-26T10:08:15",
            "request-id": "cb5f9d23-efdd-4bf2-8b41-8139190a5c22",
            "client-request-id": "cb5f9d23-efdd-4bf2-8b41-8139190a5c22"
        }
    }
}

2 answers

Your answer

Answer 1

CarlZhao-MSFT 46,376

Hi @Monica Wittwer

If you are registering anonymous users for the webinar, then make sure you are using application permissions (client credentials flow).

User's image

Hope this helps.

If the reply is helpful, please click Accept Answer and kindly upvote it. If you have additional questions about this answer, please click Comment.

Answer 2

Akhil Nasalwai - MSFT 1,685 Microsoft External Staff

Hello Monica Wittwer,

Thank you for reaching out to Microsoft support!

The 401 error typically indicates the access token is either missing, invalid or expired.

Please ensure that the access token you are using is valid and not expired. You can decode the token using a tool like jwt.ms or jwt.io

Ensure that the Authorization header in your request is correctly formatted and includes the word Bearer followed by a space and then access token.

Also double check the webinarId is properly replaced with the actual ID of the webinar and the endpoint is used as per the documentation.

Above steps might help resolve the issue.

Hope this helps.

If the answer is helpful, please click Accept Answer and kindly upvote it. If you have any further questions about this answer, please click Comment.

Vishwamurthy-MSFT 105 Reputation points Volunteer Moderator

2025-02-27T00:36:35.1566667+00:00

@Monica Wittwer please let us know if you were able to identify the root cause by decoding the token permissions.

Monica Wittwer 0

I decoded the token and it was a valid JWT token, and it was not expired.

According to my experience, if the token is expired then we get below response, which specifically says the token is expired

{
    "error": {
        "code": "InvalidAuthenticationToken",
        "message": "Lifetime validation failed, the token is expired.",
        "innerError": {
            "date": "2025-02-27T04:54:20",
            "request-id": "07188eb4-3061-450a-a616-06c39bbfa9c8",
            "client-request-id": "07188eb4-3061-450a-a616-06c39bbfa9c8"
        }
    }
}

and if we do not provide token, then also it says clearly that token is empty

{
    "error": {
        "code": "InvalidAuthenticationToken",
        "message": "Access token is empty.",
        "innerError": {
            "date": "2025-02-27T04:55:33",
            "request-id": "27e3ed0f-a7e3-441d-a306-5e2091936e09",
            "client-request-id": "27e3ed0f-a7e3-441d-a306-5e2091936e09"
        }
    }
}

Also, if we talk about webinar id, I think I am passing a valid webinar id, because if we don't pass a valid webinar id, then it returns a response which explains it well

{
    "error": {
        "code": "NotFound",
        "message": "Not Found",
        "innerError": {
            "date": "2025-02-27T05:12:29",
            "request-id": "c3393f74-dfc2-46a8-8c3d-98b752a5f672",
            "client-request-id": "c3393f74-dfc2-46a8-8c3d-98b752a5f672"
        }
    }
}

so I am sure that I am passing a correct access token and a valid webinar id, because, If I call the LIST api for registration, then it returns me a valid response with the same token and webinar id,


{
    "@odata.context": "https://graph.microsoft.com/v1.0/$metadata#solutions/virtualEvents/webinars('5f7a9f01-a0d7-4d4b-9295-335ba59dcd06%401d46436e-6891-434f-94fa-251850152e34')/registrations",
    "value": []
}

so I am pretty sure that I am passing a correct access token and correct Webinar ID, also I have one central point of sending request to Graph APIs, and creating the event, adding the presenter and publishing works, I am facing problem only with Create Registration API

Monica Wittwer 0 Reputation points

2025-02-27T05:36:12.9833333+00:00

I have decoded the JWT token, and it was a valid token, and at the time of decode it was not expired

Share via

Creating a registration in virtual event returns 401 Unauthorized

2 answers

Your answer