signature parameter covers the parameter values concatenated into a single newline-delimited string.
Parameter encoding
JSON-valued parameters -userAttributes, connectionRoles, modelRoles, customTheme, uiSettings, and groups - must be stringified and then URL encoded, like every other parameter in the URL.
For example, this JSON-valued parameter:
Manually generate a v0 signed URL
To generate the signature:1
Concatenate the required properties, delimited by a newline character in the exact order enumerated below. Note: The properties are in alphabetical order, with the exception of the leading login URL:
2
Concatenate the optional properties in alphabetical order, delimited by a newline character in the exact order enumerated below:Do not include leading or trailing spaces. Include only a single newline between each part of the signature.The following example includes optional parameters for custom theme, entity, filter search param, prefers dark, link access, theme, and user attributes:Refer to the Embed parameters reference for more information about available parameters.
3
Sign the string using your secret key with an HMAC sha256 digest algorithm, encoded as a base64url string:Refer to the Base64 spec for more information about base64url.
Node.js example
4
URL encode each parameter as part of a URL query string and attach the generated signature. The order of parameters is irrelevant when generating the login URL.

