For those saying it just happens to match the url- this is called api parsing. Embedded within the url is the email id search parameter that is leveraged as either a database query or a REST API against a JSON dataset (most likely in this case) depending on how the interface is set up. I didn't dig deep enough to determine which method WL is using. Feel free to back trace this. How to use this via a direct method: If you go to the url below, click on "Search by Email-ID", and then enter the hash key, an email will be retrieved from the search criteria. You can use the image named 630f371317c497114eb3a252057c56b19ec0d22173dc7d4920dc5ff42185db25 to verify.
For those saying it just happens to match the url- this is called api parsing. Embedded within the url is the email id search parameter that is leveraged as either a database query or a REST API against a JSON dataset (most likely in this case) depending on how the interface is set up. I didn't dig deep enough to determine which method WL is using. Feel free to back trace this.
How to use this via a direct method:
If you go to the url below, click on "Search by Email-ID", and then enter the hash key, an email will be retrieved from the search criteria. You can use the image named 630f371317c497114eb3a252057c56b19ec0d22173dc7d4920dc5ff42185db25 to verify.