Hi @philipp ,
You are right, thank you for pointing this out. Try requiring registration and testing with manual or automatic registration approval:
I believe you should see registration_url returned in the response body even though it is not documented. I will test this out myself later, but here’s a thread on some interesting, related API results that can guide your testing:
@marcus … you are correct that the documentation does not mention registration_url or join_url … but in my testing, they are returned (one or the other depending on the meeting type).
In my testing, a type 2 meeting returns registration_url, see below.
But please note I have found another problem with the API when you use it to create a meeting requiring registration (type 1 and 0) - this may be your root problem and why registration_url is not returned. Double-check your response. (Note that…
Please let me know the results of your testing.
Gianni
