Decode the body of an Verdocs access token. Note that raw tokens contain namespaced fields, e.g.
https://verdocs.com/profile_id. To make these tokens easier to use in front-end code, this name-spacing
will be removed. Note that user and signing sessions have different access token formats. The calling
application should distinguish between the two based on the context of the authenticated session, or by
the presence of the document_id field, which will only be present for signing sessions.
Decode the body of an Verdocs access token. Note that raw tokens contain namespaced fields, e.g.
https://verdocs.com/profile_id. To make these tokens easier to use in front-end code, this name-spacing will be removed. Note that user and signing sessions have different access token formats. The calling application should distinguish between the two based on the context of the authenticated session, or by the presence of thedocument_idfield, which will only be present for signing sessions.