Your site and form IDs
Every ID in Seaforms starts with what it is, so one in a log or a file tells you what it names. IDs are case-sensitive. Use them as they are, and don’t take them apart.
A form’s ID
Section titled “A form’s ID”A form’s ID is frm_ and ten lower-case letters and digits, such as frm_7f3kq2m4xa. It never changes, even when the form is renamed.
You need it for getForm and for the API. Find it:
- In the app: open the form from Forms. Its ID is under its name, with a button to copy it.
- In its file: the
idat the top ofsrc/forms/contact.seaforms.json. - From the API:
GET /v1/forms?site=site_…lists a site’s forms with their IDs.
The form’s name in the app (contact) is only for you and your files. It’s unique on its site, not across your workspace, so an agency can have a contact form on every client’s site.
A site’s ID
Section titled “A site’s ID”A site’s ID is site_ and 26 letters and digits, such as site_01JC8H2K4M9V6Q3T7X0B5N2R8D. A site is one website: every form on it shares its addresses, its connected apps and its plan.
You rarely type it. npx seaforms link (or the first pull) picks your project’s site and saves its ID in seaforms.json, at your project’s root:
{ "siteId": "site_01JC8H2K4M9V6Q3T7X0B5N2R8D", "dir": "src/forms"}Commit it, so everyone who pulls, and your CI, gets the same site’s forms. To choose again, run npx seaforms link, or give the ID yourself with --site. In the app, a site’s ID is under Settings, then Site details, with a button to copy it. GET /v1/sites lists the sites a key can see, with their IDs.
Every prefix
Section titled “Every prefix”| Prefix | What it is |
|---|---|
frm_ |
a form |
site_ |
a site |
sub_ |
a submission |
blk_ |
a submission caught as spam. Not spam turns blk_<id> into sub_<id>, keeping the rest. |
ptl_ |
someone who left part way |
upl_ |
an uploaded file |
con_ |
a connection: a webhook, Discord, Teams, Slack, Cal.com, Mailchimp or Stripe |
dlv_ |
one delivery of one submission to one place |
evt_ |
one webhook event |
tpl_ |
one of your workspace’s own templates |
Everything after the prefix in the 26-character IDs sorts by when it was made, which is how lists page through results.
Secrets
Section titled “Secrets”Secrets have prefixes too, so GitHub’s secret scanning can spot one in a commit:
| Prefix | Secret | Where it’s made |
|---|---|---|
sfk_ |
an API key | the app, Settings, then API keys |
sfd_ |
a dev token, for trying forms on localhost |
the app, Settings, then Site details |
whsec_ |
a webhook’s signing secret | the app, Settings, then Connections |
Each is shown once, when it’s made. Keep API keys and signing secrets on your server or in your build’s environment, never in code a browser loads.
ChatGPT is a trademark of OpenAI, and Claude and Claude Code are trademarks of Anthropic. Other product names and logos belong to their owners. None of them makes or endorses Seaforms. Trademarks