For the complete documentation index, see llms.txt. This page is also available as Markdown.

Creating your widget keys

Register your domain in the dashboard to get the Widget ID and Signing Secret your widget uses to authenticate.

Before you can configure or embed the widget, you need a widget key. A widget key is a Widget ID + Signing Secret pair, created in the SwapKit dashboard and bound to the domain where the widget will run. Everything else (Widget Studio, the embed snippet, all settings) starts from this key, so this is the first step of any integration.

Prerequisites

  • A SwapKit dashboard account with an app. You can register in our dashboard to access it.

  • The domain (or domains) where the widget will be embedded.

Add a domain

Key setup example
  1. Open your application in the SwapKit dashboard and enter or create your app.

  2. Open the Widget Keys tab.

  3. Click + Add Domain.

  4. Enter the domain where the widget will be embedded, without https://. The widget will only work on that domain.

    • Use a wildcard prefix (e.g. *.example.com) to allow all subdomains. The base domain (example.com) is included automatically.

  1. Confirm. The dashboard creates a Widget ID and Widget Key string scoped to that domain.

The Signing Secret is only shown when the key is created or rotated. Copy it somewhere safe at creation time. If you lose it, rotate the key to generate a new one. Rotating invalidates the old secret immediately, so any live widget still using it will stop authenticating until you update your deployed integration with the new secret.

Managing keys

From the Widget Keys table you can:

  • Copy the Widget ID.

  • Open the key in Widget Studio.

  • Enable or disable a key.

  • Rotate the Widget Key string (open the dropdown when hovering the key).

  • Delete a key.

Keep in mind:

  • Rotating a Widget Key invalidates the old key immediately. Update your deployed snippet with the new key at the same time.

  • Disabling or deleting a key stops the widget from authenticating on that domain.

  • Keys are domain-bound. A key created for one domain will not authenticate on another, so create a separate domain entry (or use a wildcard) for each place the widget runs.

Affiliate fees

As mentioned earlier, affiliate fees won't be charged until you set it up explicitly beforehand. Click on the Affiliate Config tab at the top of the dashboard and follow the steps on the monetization page.

Next

With a key created and Studio open, continue to Settings & Configuration to theme the widget, choose wallets, and generate your embed snippet, or start by trying out the default integration.

Last updated