Skip to main content

Understand Web IDs and API IDs

Understanding web IDs and API IDs​

If you are using console.legalesign.com for your web experience you'll notice the IDs in the web urls do not match the API IDs.

The console web app is using base64 encoded versions of the API IDs.

The base64 encoded versions are also prefixed with 3 characters that identify the relevant object.

For example, on the web app a document details page URL might look like this:

http://console.legalesign.com/group/Z3JwMGJjZTY3ZTgtYTVlOS00MzM4LTlmMDYtMmM3OWY2ZTVmMmY3/detail/ZG9jNjc4NDc3N2YtMDExNC00OTdhLTk0NmYtNTc2OTE0YjU0YzZj/

The first ID after /group/ is the base64 encoded group ID, and the second, after /detail/, is the base64 encoded document ID. Simply decode them and strip the first 3 characters to get the underlying UUID.

For example, using the atob function in javascript:

atob("Z3JwMGJjZTY3ZTgtYTVlOS00MzM4LTlmMDYtMmM3OWY2ZTVmMmY3")
"grp0bce67e8-a5e9-4338-9f06-2c79f6e5f2f7"

atob("ZG9jZTZiMjNjYTEtODQ0My00MTZkLTgzMTktYzgwYTBhZmEyMDAy")
"doce6b23ca1-8443-416d-8319-c80a0afa2002"

Your API identifiers are revealed. Your group is '0bce67e8-a5e9-4338-9f06-2c79f6e5f2f7' and the relevant document is 'e6b23ca1-8443-416d-8319-c80a0afa2002'.