ConvertKit (now Kit) is an email marketing and audience management platform built for creators, offering customizable forms and landing pages to grow subscribers, audience tagging and segmentation, automated email sequences and broadcasts, and tools to sell digital products and paid newsletter subscriptions.
Power end-to-end data operations for your ConvertKit API with Nexla. Our bi-directional ConvertKit connector is purpose-built for ConvertKit, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to ConvertKit or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your ConvertKit workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Nexla connects to Kit (formerly ConvertKit) with an API key from your own Kit account. Kit now issues V4 API keys, which work with the Kit API v4 (https://api.kit.com/v4). Most templates on this page use API v4, so a V4 API key is the recommended way to connect. A small set of legacy templates still call the deprecated API v3 and need the older API Secret Key instead.
Click Add a new key, and give the key an internal name.
Copy the key and store it somewhere safe. Kit shows the key only once; if you lose it, you have to reset the key in the same Developer settings, which stops the old value from working.
Kit allows an API key up to 120 requests in a 60-second period. A few Kit endpoints accept only OAuth and reject API keys, including all bulk endpoints (/v4/bulk/*) and the purchase endpoints, so this connector has no templates for them. For details, see Kit's API authentication and rate limits guides.
Legacy API v3
Kit has deprecated API v3 and recommends API v4 for new projects, and V4 API keys do not work with API v3. Use the API Secret Key method only if you need the legacy v3 templates listed under Legacy v3 templates; it takes the v3 API secret of your account. See Kit's API v3 authentication reference and Upgrading to V4 guide.
The ConvertKit connector offers two authentication methods. Each credential works only with the templates for its own API version:
V4 API Key (recommended): Kit API v4 key, sent in the X-Kit-Api-Key request header. Use it with every template on this page except the legacy v3 templates.
API Secret Key (legacy): Kit API v3 secret, sent as the api_secret query parameter. Use it only with the five legacy v3 templates.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
New Credential Overlay – ConvertKit
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Select the authentication method you want to use, and enter the key:
V4 API Key (recommended): Enter the Kit V4 API key you created in Prerequisites in the V4 API Key field. Nexla tests the credential by reading your Kit account (GET /v4/account).
API Secret Key (legacy): Enter your Kit API v3 secret in the API Secret Key field. Nexla tests the credential by reading your account through API v3.
Keep your Kit keys secure and do not share them publicly. A Kit key gives access to your account's data, including subscribers and broadcasts. If a V4 API key is exposed, reset it in your Kit Developer settings and update the credential with the new value.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the ConvertKit connector tile, then select the credential that will be used to connect to your Kit account, and click Next; or, create a new ConvertKit credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Kit endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below, grouped by the part of Kit they read.
Every template except the legacy v3 templates uses Kit API v4 and needs a V4 API Key credential. Kit's list endpoints use cursor-based pagination; the v4 list templates request up to 1,000 records per page (100 for List Apps) and follow the cursor until every page is read.
These templates call the deprecated Kit API v3 (https://api.convertkit.com/v3) and need an API Secret Key credential, which Nexla sends as the api_secret query parameter. They read in a single request without pagination. For new flows, use the v4 templates above.
Get Statistics
Retrieves delivery and engagement statistics for one broadcast from the v3 API.
Broadcast ID (required): The ID of the broadcast. Use List resources with broadcasts to find it.
Lists one v3 collection of your account, such as subscribers, forms, sequences, tags, broadcasts, custom fields, purchases or webhooks, in a single request.
Resource Type (required): The v3 collection to list: subscribers (default), forms, sequences, tags, broadcasts, custom_fields, purchases or webhooks.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
ConvertKit data sources can also be manually configured to ingest data from any valid Kit API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Kit API v4 endpoint URLs follow the pattern https://api.kit.com/v4/.... A V4 API Key credential adds the X-Kit-Api-Key header to each request automatically. List endpoints return a pagination object; pass its end_cursor value as the after query parameter to request the next page. For the available endpoints, see the Kit API reference.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new ConvertKit data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the ConvertKit destination, and select the Send to Destination option from the menu. Select the ConvertKit connector from the list of available destination connectors, then select the credential that will be used to connect to your Kit account, and click Next; or, create a new ConvertKit credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Kit endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Each record in the Nexset is sent as the JSON body of one request (Content-Type: application/json), one record at a time. ID settings, such as Subscriber ID or Tag ID, are fixed on the destination and apply to every record it sends, so each record acts on the same subscriber, tag, or other object. Every template except the legacy v3 templates needs a V4 API Key credential. Read each template's Side effect note before you activate the destination: some templates send email to subscribers, and some delete data.
Creates a subscriber from each record (email_address, first_name, state, fields). If a subscriber with that email address already exists, Kit updates it instead.
Side effect: Creates or updates a subscriber in your Kit account.
Removes a tag from a subscriber by subscriber ID. Kit documents no request body for this call, so send an empty record ({}); each record performs the action once.
Tag ID (required): The Kit ID of the tag. Use List Tags to find it.
Subscriber ID (required): The Kit ID of the subscriber. Use List Subscribers to find it.
Removes a tag from the subscriber whose email address is configured on the destination. Kit documents no request body for this call, so send an empty record ({}); each record performs the action once.
Tag ID (required): The Kit ID of the tag. Use List Tags to find it.
Subscriber Email (required): Email address of the subscriber.
Tags an existing subscriber by subscriber ID. Kit documents no request body for this call, so send an empty record ({}); each record performs the action once.
Tag ID (required): The Kit ID of the tag. Use List Tags to find it.
Subscriber ID (required): The Kit ID of the subscriber. Use List Subscribers to find it.
Adds an existing subscriber to a form by subscriber ID. A record can carry an optional referrer. Kit returns a 422 error for archived or deleted forms.
Form ID (required): The Kit ID of the form. Use List Forms to find it.
Subscriber ID (required): The Kit ID of the subscriber. Use List Subscribers to find it.
Adds an existing subscriber, identified by each record's email_address, to a form. A record can carry an optional referrer. Kit returns a 422 error for archived or deleted forms.
Form ID (required): The Kit ID of the form. Use List Forms to find it.
Adds an existing subscriber to a sequence by subscriber ID. Kit documents no request body for this call, so send an empty record ({}); each record performs the action once.
Sequence ID (required): The Kit ID of the sequence. Use List Sequences to find it.
Subscriber ID (required): The Kit ID of the subscriber. Use List Subscribers to find it.
Side effect: The sequence's published emails start sending to the subscriber.
Side effect: A record with send_at schedules the email to subscribers, and public: true publishes it to the web. Keep send_at null and public false to create a draft.
Creates a content snippet from each record: a name, plus either snippet_type inline with content, or snippet_type block with document_attributes.value_html.
Side effect: Adds a new snippet to your Kit account.
Creates a previous-generation (legacy) webhook from each record: a target_url and an event object with the event name and, depending on the event, a form_id, tag_id, sequence_id, product_id or initiator_value. Kit recommends webhook endpoints for new integrations.
Side effect: Kit starts sending event notifications to the target URL.
These templates call the deprecated Kit API v3 (https://api.convertkit.com/v3) and need an API Secret Key credential. For new flows, use the v4 templates above.
Add subscriber
Subscribes an email address to a v3 form, sequence or tag, with each record as the request body. The template URL needs a resource type (forms, sequences or tags) and a resource ID, but the live template defines no settings fields for them. If the destination does not ask for them, use a v4 template such as Add Subscriber to Form by Email, or set up the request on the Advanced tab.
Side effect: Subscribes the email address to the resource.
Creates a v3 resource, such as a broadcast or a webhook, from each record. The template URL needs a resource type (for example broadcasts), but the live template defines no settings field for it. If the destination does not ask for one, use a v4 template such as Create Broadcast, or set up the request on the Advanced tab.
Side effect: Creates the resource in your Kit account.
ConvertKit destinations can also be manually configured to send data to any valid Kit API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
Kit API v4 endpoint URLs follow the pattern https://api.kit.com/v4/..., and use POST to create, PUT or PATCH to update, and DELETE to remove objects, with a JSON request body. A V4 API Key credential adds the X-Kit-Api-Key header to each request automatically.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured ConvertKit endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the ConvertKit endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.