FAQ

Questions about configuring and integrating a signed embed. For step-by-step details, see Integration steps; for tenant isolation, see Multi-tenant; for design examples, see Use cases.

Missing param: xxx is shown when issuing a token

When issuing a token, the request must include all of the server-side parameters you've configured. The missing parameter ID is shown as xxx.

The following parameters must be set by the server is shown when sending a client-side parameter

You're trying to change a server-side parameter from the client side. Changing a server-side parameter requires issuing a new token.

Sending a client-side parameter doesn't change the value

Check the following.

1. Whether the target parameter is configured as a server-side parameter.
2. Whether param_value is a valid JSON string.
3. Whether param_id matches an existing parameter ID.

Can't embed after configuring allowed origins

Check whether the origin of the page embedding it matches one of the origins you set in Allowed origins. If you've configured origins, you can't open the embed by attaching the token directly to the URL.

No API key is granted

Add the API key you want to use for issuing tokens to API keys granted permission on the settings screen. You can't issue a token if none is configured.

Relative dates don't behave as expected

Relative dates aren't recalculated for server-side parameters. Treat it as a client-side parameter, and configure it to use the default value as the initial value. See Relative dates for details.