Hi Jen,
For Microsoft Graph API calls to create Teams meetings, here's what those status codes actually mean
200 OK - This is your clear success case. The meeting was created immediately and the response body contains the full meeting details including your join link. This is what you're hoping to see most of the time.
201 Created - Also a success, but indicates the resource was newly created. You'll get the same complete meeting object with the join web URL in the response body.
202 Accepted - This one is tricky. It means the request was accepted for processing, but the meeting might not be fully created yet. You might not get the join link immediately in the response, or you might need to poll for completion.
204 No Content - This is not a success for meeting creation. It means the request succeeded but there's no response body, which means no meeting object and crucially - no join link.
The Microsoft Graph API documentation explains these status codes in detail https://free.blessedness.top/en-us/graph/use-the-api.
For your Salesforce integration, I'd recommend treating only 200 and 201 as definite successes where you can immediately extract the meeting link. For 202 responses, you might need to implement a retry mechanism to check if the meeting was eventually created.
The 204 response should definitely go to your error handler since no meeting link will be available.
Also watch out for 207 Multi Status if you're creating multiple meetings in batch - this returns multiple status codes for different items in the batch.
Another thing to check is the response body even for successful codes. Sometimes the meeting gets created but the join web URL might be missing if there are permission issues or the user doesn't have a valid Teams license.
regards,
Alex
and "yes" if you would follow me at Q&A - personaly thx.
P.S. If my answer help to you, please Accept my answer