The short answer
To tag a sign-up from your own site, make 2 calls: create the subscriber, then add the tag by email address. Both answered 201 Created. To check that it worked, read that one subscriber's tags. Don't read the tag's subscriber list. In our run it lagged by more than 3 minutes.
| Call (API v4) | What it did | Status | Time |
|---|---|---|---|
| POST /v4/tags | Made the tag site-signup | 201 | 1.42 s |
| POST /v4/subscribers | Added sign-up 1, then sign-up 2 | 201, 201 | 4.20 s, 1.41 s |
| POST /v4/tags/{id}/subscribers | Tagged sign-up 1, then sign-up 2 | 201, 201 | 2.02 s, 1.41 s |
| Same call again for sign-up 1 | Nothing new, no error | 200 | 1.40 s |
| GET /v4/subscribers/{id}/tags | Showed site-signup for sign-up 1 when we first checked, at about 2.5 minutes | 200 | 1.20 s |
| GET /v4/tags/{id}/subscribers | 0 subscribers for over 3 minutes, then 2 | 200 | 1.07 to 1.66 s |
What buyers worry about, and what we found
"Can I tag people from my own form without Kit's form code?"
Yes. Your server makes the 2 calls with an API key. We set each subscriber to active when we added them, and no confirm email went out. That fits people who already said yes on your site. We didn't test double opt-in.
"What if the same person signs up twice?"
When we tagged sign-up 1 a second time, the call came back 200 instead of 201 and the first tag date stayed. There was no error and no duplicate, so retrying after a timeout looks safe.
"How do I check the tag landed?"
Ask for that one subscriber's tags. We checked sign-up 1 once, about 2.5 minutes after tagging, while the tag's own list still said 0, and it already showed site-signup. We didn't check sign-up 2's list. The subscriber page in the Kit app showed the tag too.

The list of everyone with the tag was a different story. We polled it every 11 seconds or so for about 2 minutes and it stayed at 0. It was still 0 at about 3 minutes after tagging, and again at 04:17 UTC. Around 4 minutes in, the Subscribers page in the app, filtered by Confirmed and the tag, said "No matching subscribers". By about 6 minutes the API list showed both.

That page also said "Total subscribers 1" and "New subscribers (today) 0", though we had already added 2. The totals were behind as well.
How we ran it
We used our Kit account and one API key from the developer settings. Each call sends the key in the X-Kit-Api-Key header.
- Make the tag once:
POST /v4/tagswith{"name": "site-signup"}. Keep the id it returns. - Add the sign-up:
POST /v4/subscriberswithemail_address,first_nameand"state": "active". - Tag them:
POST /v4/tags/{tag id}/subscriberswith the sameemail_address. 201 meant newly tagged, and 200 came back when they already had it. - Check one person:
GET /v4/subscribers/{subscriber id}/tags. Use this for a quick check instead of the tag's list.
curl -X POST https://api.kit.com/v4/tags/TAG_ID/subscribers \
-H "X-Kit-Api-Key: $KIT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"email_address": "reader@example.com"}'
When a paid plan makes sense
Tags and API access are on the free plan, which allows up to 10,000 subscribers. Visual automations and sequences need Creator or higher. Our trial account shows the Creator plan with a 1,000-subscriber limit, and the trial lapses on 2026-11-04. If you only want to group people with a tag, you don't need to pay for that.
What this test does not show
- 2 subscribers on one account on one day. A bigger list may lag more or less.
- We checked only sign-up 1's own tag list, and only once.
- We did not test Kit forms, double opt-in or the bulk endpoints.
- We did not test whether an automation fires when the tag is added through the API.
Frequently asked questions
How do I add a tag to a Kit subscriber with the API?
Call POST /v4/tags/{tag id}/subscribers with the subscriber's email address. In our test it answered 201 in 1.4 to 2.0 seconds.
Why does my Kit tag show 0 subscribers right after I tag someone?
The tag's subscriber list lagged. In our test it stayed empty for more than 3 minutes and showed both people by about 6 minutes. Sign-up 1's own tag list was already right when we checked at about 2.5 minutes.
Does tagging the same Kit subscriber twice cause an error?
Not in our test. The second call returned 200 instead of 201, kept the first tag date and made no duplicate.
Sources
- Kit API v4 documentation: the tag and subscriber calls we made.
- Kit plans: Free up to 10,000 subscribers, visual automations and sequences on Creator and higher.
- Our first Kit test: a scheduled broadcast through the same API.