How to Use Kit to Route Product Signups Into Sequences

The short answer: create a V4 API key in Kit's Developer settings, create your tags and custom fields once, then for each signup from your app or checkout create the subscriber (an upsert), tag them by email address, add them to the right sequence, record purchases for buyers, and subscribe a webhook endpoint so your own systems hear about activations and changes, within the API key limit of 120 requests a minute.

Disclosure: I may earn a commission through some links on this site. It does not change what this page says.

A signup in your product and a subscriber in your newsletter are usually the same person living in two databases. Kit's API is built to close that gap: one call creates or updates the subscriber, another tags them, and the tag decides which sequence they get. The steps below come from Kit's developer documentation, which stayed readable on 24 October 2026 while Kit's pricing page and help centre returned a bot check. For what Kit is, see the Kit glossary entry.

What decides the setup:

1. The rate limit, worked out. API keys allow 120 requests per rolling 60 seconds; OAuth allows 600 (authentication docs). For example, backfilling 3,000 existing users with one create call and one tag call each is 3,000 x 2 = 6,000 requests, which at 120 a minute is 6,000 / 120 = 50 minutes. Fine for a one-off script; too slow for a nightly sync, which is what OAuth and the bulk endpoints are for.
2. The events you already have. Signup, trial start, purchase: your product already records them. Each becomes either a tag (who someone is) or a purchase record (what they bought).
3. The check that it worked. Pick ten test users, run the sync, and look each one up in Kit with their tags and sequence before you switch it on for everyone.

Step 1: Create an API key, or plan for OAuth

For a script that only touches your own account, an API key is the simplest route. Go to the Developer tab in your account settings, click Add a new key, name it, and copy it at once; Kit shows it only once, and a reset breaks every script using the old value (authentication docs). Some endpoints, including bulk operations and creating purchases, require OAuth, which means registering an app; check each endpoint's page before you build on it.

Step 2: Define tags and custom fields once

Create the tags your sequences will hang on, such as signed-up-app or trial-started. Tag creation is idempotent on the name, case-insensitive, so re-running a setup script returns the existing tag rather than a duplicate (create a tag). Create any custom fields, like plan or company, before you send values for them: the create subscriber endpoint returns an error for a field key the account does not have (create a subscriber).

Step 3: Upsert the subscriber

Send POST /v4/subscribers with the email address, first name and fields. It behaves as an upsert: a new address creates a subscriber, an existing one is updated. The documentation notes two limits: you cannot change a subscriber's state through this endpoint, and one request sets at most 140 custom fields. Only send people who agreed to hear from you; the product signup and the marketing opt-in are separate questions, and the second one is the one that counts here.

Step 4: Tag them by email address

Call the tag-by-email endpoint with the tag's ID. The subscriber must already exist, which is why step 3 comes first (tag a subscriber by email). Tag people for who they are or what they did, not for which email they should get next; sequences change more often than facts about a person.

Step 5: Add them to the sequence

Add the subscriber to a sequence by email address, again after they exist (add to sequence by email). Each sequence has its own send days, send hour and time zone, and each email inside it a delay, which you can read and set through the sequence endpoints. Keep the onboarding sequence short: three emails that each move one step of product adoption.

Step 6: Record purchases for buyers

When someone pays, record the order with the create purchase endpoint: it attaches the transaction, products and totals to the subscriber by email address, creates the subscriber if needed, and can drive purchase-based automations (create a purchase). This endpoint needs OAuth, not an API key.

Step 7: Listen with a webhook

Register an endpoint through the API or at app.kit.com/webhooks and subscribe it to the events you care about, such as a subscriber being created or activated. Kit sends a POST with a JSON envelope carrying 1 to 100 events of one type, signs each delivery, and keeps deliveries and attempts for 30 days in delivery history (webhooks overview). Verify the signature and deduplicate on the event ID before acting.

Respect the other direction too. Article 21(2) of the GDPR (EUR-Lex) gives people the right to object to direct marketing at any time. If someone opts out inside your product, call Kit's unsubscribe endpoint the same day; it moves them to cancelled and keeps the record.

Step 8: Let an agent draft, not send

The Kit MCP connects Claude, ChatGPT or Cursor to the account at app.kit.com/mcp, through OAuth, on the paid Creator and Creator Pro plans. Ask it to draft a broadcast to everyone tagged trial-started about the feature they have not tried; through the API a broadcast with no send time is saved as a draft (create a broadcast). Kit says sending broadcasts and deleting data always require your explicit confirmation, so the draft waits for you: read it, fix it, schedule it.

What Kit's documentation warns about

• Tagging before creating. Tag and sequence calls fail for subscribers who do not exist yet.
• Unknown field keys. A custom field missing from the account returns an error rather than being created.
• Double opt-in forms. Adding subscribers to a double opt-in form through the API sends them an incentive email (bulk form docs).
• API V3. It still works but is deprecated and will be sunset; build on V4 (API overview).

Kit's App Store and plugins make every connection easier to add and, by the same token, harder to unpick. That is the platform's interest, not a flaw. Keep the tag scheme in your own documentation and a regular export of subscribers, so the logic lives with you as well as in the vendor.

FAQ

Do I need a developer for this?

For the API, yes, or someone comfortable with a script. Without one, the Kit MCP can create, tag and update individual subscribers from a chat, which covers small volumes but not a live sync.

Will re-running my sync create duplicate subscribers?

No. Creating a subscriber is an upsert on email address, and creating a tag returns the existing one if the name is taken, per the developer documentation.

How fast can I backfill a large list?

Bulk endpoints handle 100 subscribers or fewer synchronously and larger batches asynchronously, with an optional callback URL (bulk create subscribers). They require OAuth.