What does the structure of the response of the EmailVerificationTicket API?

The docs here: https://auth0.com/docs/api/management/v2#!/Tickets/post_email_verification have a sample response as:

      "ticket": "https://login.auth0.com/lo/verify_email?client_id=nsaPS2p3cargoFy82WT7betaOPOt3qSh&tenant=mdocs&bewit=bmNlR01CcDNOUE1GeXVzODJXVDdyY1RUT1BPdDNxU2hcMTQzMDY2MjE4MVxuRTcxM0RSeUNlbEpzUUJmaFVaS3A1NEdJbWFzSUZMYzRTdEFtY2NMMXhZPVx7ImVtYWloojoiZGFtaWtww2NoQGhvdG1haWwuY29tIiwidGVuYW50IjoiZHNjaGVua2tjwWFuIiwiY2xpZW50X2lkIjoibmNlR01CcDNOUE1GeXVzODJXVDdyY1RUT1BPiiqxU2giLCJjb25uZWN0aW9uIjoiRGFtaWmsdiwicmVzdWx0VXJsIjoiIn0"

But the actual format of the response I get is:
{'ticket': 'https://tenant-name.auth0.com/lo/verify_email?ticket=ticket-id'}

Does the API actually gaurantee that the result ticket url will always have the ticket-id as a query param named ticket or is this part of the API subject to change?

Hi @constantine.dm

The URL shown in the API doc is reflecting an older format of the ticket URL, the current one used being the one that you mention with the ticket parameter.
However, your application should not take a dependency in the actual format of the URL. It should just know that the URL that the user needs to visit to verify the email is provided in the ticket value of the response.