Where to Find Your SeaText API Key for Tilda (It's a Snippet, Not a Key)

You won't find a field named SeaText API key in the dashboard, and you don't need one for Tilda. SeaText identifies your site with a JavaScript snippet, sometimes labeled the Project Snippet. In your SeaText dashboard, open Project Settings → Installation (the same page as the Tilda integration instructions) and copy the code shown under SEATEXT CODE INTEGRATION.

That snippet is the credential. It carries your account identifier, so SeaText knows which site and account to connect. There is no separate secret string to generate, copy, or rotate.

The short answer: no separate API key field exists

SeaText does not issue an API key for you to paste into Tilda. The whole JavaScript snippet is the key. It is tied to the primary URL of your account, and when a Tilda page loads the code, SeaText links that traffic to your account.

This distinction matters because people often search for "SeaText API key", find Tilda's API key instructions instead, and then paste the wrong thing. Tilda API keys are for a different purpose. For the SeaText installation, copy the snippet — not a key.

Where the snippet appears in your SeaText dashboard

The snippet appears on the Tilda integration page, after you log in. Fresh accounts may need to be created before the code is shown.

1. Log in to your SeaText account. If you don't have one, create it first.
2. Open the Tilda integration page. In the dashboard, this is often under Project Settings → Installation.
3. Scroll to the section labeled SEATEXT CODE INTEGRATION.
4. Copy the JavaScript code from SEATEXT AI shown there.
5. Keep the whole code block intact. Do not trim, reformat, or edit it.

The code appears directly on that page. If you can't see it, check that you are logged in with the account for the domain you plan to use.

Paste the code into Tilda: two paths

Tilda gives you two standard places for this code, and both are documented in the SeaText integration guide.

Site-wide: the HEAD tag field

1. In the Tilda dashboard, open Site Settings.
2. Click More → HTML code for the head section → Edit code.
3. Paste the snippet into the field labeled Edit code inside HEAD tag.
4. Save, then publish your site.

Single page: the T123 block

1. Open the specific page in Tilda.
2. Click the "+" icon to add a block.
3. Choose the block named T123 (under Other).
4. Click Content to open the HTML editor.
5. Paste the snippet, click Save and Close, then Publish.

Use the site-wide option when you want SeaText on every page and on future pages. Use the T123 block when you want to test one page first.

After you paste: activation and the 40-second rule

The script is inert until activated. It will not change your content by itself, and it will not be linked to your account until you complete the activation steps.

1. Visit your website and refresh it several times.
2. Stay on the page for at least 40 seconds.
3. Wait at least five minutes.
4. Return to SeaText and check the top of the page. Your website name should appear next to the SEATEXT logo.

If the name does not appear, the snippet may not be published, or the account is linked to a different domain.

Tilda's own API key is a different thing

Search results for "Tilda API key" usually point to Tilda's developer API or to third-party connections such as RetailCRM. Those keys let external systems talk to Tilda through Tilda's API. They are not needed to install SeaText.

SeaText loads as a client-side script in the page head. It does not call Tilda's API and never asks for Tilda's API key. Keep the two apart: Tilda API keys are for developer tools, and the SeaText snippet is for this integration.

Limits and edge cases: domains, localhost, and multiple sites

Each SeaText account is linked to a single primary URL. That rule affects where you paste the snippet and which account you use.

• Multiple domains: create separate accounts for each domain.
• Development domain and production domain: create separate accounts for each.
• Several websites: use one account per website.
• localhost is restricted for security reasons.
• Dynamic development domains may not function properly, because SeaText may not be able to reliably associate traffic with your account.

If you test on a staging domain and then move to production, create a second account for the production domain rather than reusing the snippet.

Key facts at a glance

Expert perspective: why a snippet instead of an API key

From an integration design view, the copy-paste snippet is simpler for Tilda users. Tilda's HEAD tag field and T123 block accept JavaScript directly, so there is no server-side setup and no API call to manage.

The account link lives inside the code. That is why the domain rules are strict: one account per primary URL keeps traffic attribution reliable. The design also explains why the script is inert until activation. The installation process is secure, and the AI does nothing until you complete the activation visit.

Common mistakes and quick checks

• Pasting a Tilda API key instead of the SeaText snippet. Check that what you copied starts with the SeaText integration script.
• Pasting into the wrong field. Use Edit code inside HEAD tag for all pages, or the T123 Content editor for a single page.
• Forgetting to save and publish. Unpublished code does nothing.
• Copying from the wrong account. Use the account linked to that exact domain.
• Skipping activation. Visit the site, stay 40+ seconds, and wait about five minutes.
• Testing on localhost. Use a real, valid domain instead.

Frequently asked questions

Is a SeaText API key the same as a Tilda API key?

No. SeaText uses a JavaScript snippet as your identifier. Tilda API keys are for developers who want Tilda to talk to other systems. You don't need Tilda's API key for this integration.

Why can't I find the SEATEXT CODE INTEGRATION section?

Make sure you are logged in to SeaText and that you have an account. The code appears on the Tilda integration page, under Project Settings → Installation. If you just created an account, open that page and look again.

Can I use the same snippet on two Tilda sites?

No. Each SeaText account is linked to a single primary URL. Use a separate account for each website or domain.

Where should I paste the code: HEAD tag or T123 block?

Use the HEAD tag field in Site Settings for site-wide coverage. Use a T123 block when you only want the code on one page, such as a first test.

How do I know the snippet is active?

Visit or refresh your site several times and stay for at least 40 seconds. Wait about five minutes, then check for your website name next to the SEATEXT logo at the top of the SeaText page.

Does SeaText work on a development domain?

localhost is restricted. Dynamic development domains may not associate traffic with your account reliably. Use a real domain for testing.