Skip to main content

ConvertKit

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.

ConvertKit icon

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

Prerequisites​

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.

To create a V4 API key:

  1. Sign in to Kit and open the Developer tab of your account settings.

  2. Click Add a new key, and give the key an internal name.

  3. 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.

Authenticate​

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.

Credentials required​

Kit API v4 key, sent in the X-Kit-Api-Key header. For the v4 endpoints only; the v3 endpoints need the API Secret Key template.

FieldRequiredSecretDescription
V4 API KeyYesYesA Kit v4 API key. Create one under Settings > Developer > Add a new key; it is shown only once.

Both key fields are masked when you enter them, and Nexla stores them as secrets.

Create a credential in Nexla​

  1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – ConvertKit

ConvertKitCred.png
  1. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

  2. 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.

  3. 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.

Use as a data source​

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.

Endpoint templates​

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.

Account​

Get Account

Retrieves the Kit account and user behind the key: account ID, name, plan, primary email, timezone and sending addresses.

Get Account Colors

Retrieves the account's saved brand color palette (up to 10 hex codes) as one record.

Get Creator Profile

Retrieves the public Creator Profile: name, byline, bio, image and profile URL (404 when the account has none).

Get Email Stats

Retrieves account email stats for the last 90 days: sent, opened, clicked and the open, click, unsubscribe and bounce rates.

Get Growth Stats

Retrieves subscriber growth (new, cancelled, net new, total) for the last 90 days, in the account's sending time zone.

Subscribers​

Get Subscriber

Retrieves one subscriber with state, custom field values and dates.

  • Subscriber ID (required): The Kit ID of the subscriber. Use List Subscribers to find it.
  • Reference: Kit API documentation

Get Subscriber Stats

Retrieves one subscriber's email engagement stats (sends, opens, clicks, bounces, rates).

  • Subscriber ID (required): The Kit ID of the subscriber. Use List Subscribers to find it.
  • Reference: Kit API documentation

List Subscriber Tags

Lists the tags on one subscriber with the date each was added.

  • Subscriber ID (required): The Kit ID of the subscriber. Use List Subscribers to find it.
  • Nexla follows the pagination and fetches every page.
  • Reference: Kit API documentation

List Subscribers

Lists the account's subscribers by status (default active).

  • Status (required): Which records by status. Kit's default is active. Options: active (default), inactive, bounced, complained, cancelled, all.
  • Nexla follows the pagination and fetches every page.
  • Reference: Kit API documentation

Tags​

List Tag Subscribers

Lists the subscribers with one tag by status (default active).

  • Tag ID (required): The Kit ID of the tag. Use List Tags to find it.
  • Status (required): Which records by status. Kit's default is active. Options: active (default), inactive, bounced, complained, cancelled, all.
  • Nexla follows the pagination and fetches every page.
  • Reference: Kit API documentation

List Tags

Lists the tags of the account.

Forms​

List Form Subscribers

Lists the subscribers of one form by status (default active).

  • Form ID (required): The Kit ID of the form. Use List Forms to find it.
  • Status (required): Which records by status. Kit's default is active. Options: active (default), inactive, bounced, complained, cancelled, all.
  • Nexla follows the pagination and fetches every page.
  • Reference: Kit API documentation

List Forms

Lists forms and landing pages by status (default active).

  • Status (required): Which records by status. Kit's default is active. Options: active (default), archived, trashed, all.
  • Nexla follows the pagination and fetches every page.
  • Reference: Kit API documentation

Sequences and sequence emails​

Get Sequence

Retrieves one sequence's schedule, sending address, template and active/repeat/hold flags.

  • Sequence ID (required): The Kit ID of the sequence. Use List Sequences to find it.
  • Reference: Kit API documentation

Get Sequence Email

Retrieves one sequence email with its full content and timing.

  • Sequence ID (required): The Kit ID of the sequence. Use List Sequences to find it.
  • Email ID (required): The Kit ID of the email. Use List Sequence Emails to find it.
  • Reference: Kit API documentation

List Sequence Emails

Lists the emails of one sequence in send order with timing and publish state.

  • Sequence ID (required): The Kit ID of the sequence. Use List Sequences to find it.
  • Nexla follows the pagination and fetches every page.
  • Reference: Kit API documentation

List Sequence Subscribers

Lists the subscribers in one sequence by status (default active).

  • Sequence ID (required): The Kit ID of the sequence. Use List Sequences to find it.
  • Status (required): Which records by status. Kit's default is active. Options: active (default), inactive, bounced, complained, cancelled, all.
  • Nexla follows the pagination and fetches every page.
  • Reference: Kit API documentation

List Sequences

Lists the email sequences of the account with their schedule and flags.

Broadcasts​

Get Broadcast

Retrieves one broadcast: subject, HTML content, targeting, template, schedule and publishing details.

  • Broadcast ID (required): The Kit ID of the broadcast. Use List Broadcasts to find it.
  • Reference: Kit API documentation

Get Broadcast Stats

Retrieves delivery and engagement stats for one broadcast, with its sending status and progress.

  • Broadcast ID (required): The Kit ID of the broadcast. Use List Broadcasts to find it.
  • Reference: Kit API documentation

List Broadcast Link Clicks

Lists each link in one broadcast with its unique clicks and click rates.

  • Broadcast ID (required): The Kit ID of the broadcast. Use List Broadcasts to find it.
  • Nexla follows the pagination and fetches every page.
  • Reference: Kit API documentation

List Broadcast Stats

Lists delivery and engagement stats (recipients, opens, clicks, unsubscribes, rates) for all broadcasts.

List Broadcasts

Lists all broadcasts with content, targeting, template and publishing settings.

Custom fields​

List Custom Fields

Lists the subscriber custom fields of the account (ID, name, key, label).

Segments, email templates, snippets and posts​

Get Post

Retrieves one post with its HTML content, status, slug, SEO fields and public URL.

Get Snippet

Retrieves one content snippet with its content.

  • Snippet ID (required): The Kit ID of the snippet. Use List Snippets to find it.
  • Reference: Kit API documentation

List Email Templates

Lists the account's email templates (ID, name, default flag, category).

List Posts

Lists the posts on the creator's Kit site with status, slug, URL and dates (content omitted).

List Segments

Lists the subscriber segments of the account (ID, name, created date).

List Snippets

Lists the account's content snippets (name, type, Liquid key).

Webhooks​

Get Webhook Delivery

Retrieves one webhook delivery attempt with its status and timing.

  • Endpoint ID (required): The Kit ID of the endpoint. Use List Webhook Endpoints to find it.
  • Delivery ID (required): The Kit ID of the delivery. Use List Webhook Deliveries to find it.
  • Reference: Kit API documentation

Get Webhook Endpoint

Retrieves one webhook endpoint with its URL, events and status.

  • Endpoint ID (required): The Kit ID of the endpoint. Use List Webhook Endpoints to find it.
  • Reference: Kit API documentation

List Legacy Webhooks

Lists the previous-generation (legacy) webhooks of the account.

List Webhook Deliveries

Lists the delivery attempts of one webhook endpoint with status and response codes.

  • Endpoint ID (required): The Kit ID of the endpoint. Use List Webhook Endpoints to find it.
  • Nexla follows the pagination and fetches every page.
  • Reference: Kit API documentation

List Webhook Endpoints

Lists the webhook endpoints (URL, events, status) of the account.

Apps​

Get App

Retrieves one Kit App Store app with its description, capabilities, links and install URL.

List Apps

Lists the Kit App Store apps the account can see (store apps plus its own).

Legacy v3 templates​

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.
  • Reference: Kit API documentation

List resources

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.
  • Reference: Kit API documentation

List subscriptions

Lists the subscriptions, with subscriber data, of one v3 form, sequence or tag.

  • Resource Type (required): The v3 collection whose subscriptions are listed: forms (default), sequences or tags.
  • Resource ID (required): The ID of the form, sequence or tag. Use List resources to find it.
  • Reference: Kit API documentation

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.

Manual configuration​

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.

Use as a destination​

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.

Endpoint templates​

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.

Account​

Update Account Colors

Replaces the account's brand color palette with each record's colors (up to 10 hex codes).

  • Side effect: Replaces the whole palette, so send every color you want to keep.
  • Reference: Kit API documentation

Subscribers​

Create Subscriber

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.

Delete Subscriber Location

Removes a subscriber's pinned location.

  • Subscriber ID (required): The Kit ID of the subscriber. Use List Subscribers to find it.
  • Side effect: Clears the subscriber's pinned location.
  • Reference: Kit API documentation

Pin Subscriber Location

Pins a subscriber's location from each record's location object (city, country code, time zone and so on).

  • Subscriber ID (required): The Kit ID of the subscriber. Use List Subscribers to find it.
  • Side effect: Sets the subscriber's pinned location.
  • Reference: Kit API documentation

Unsubscribe Subscriber

Unsubscribes a subscriber. Kit documents no request body for this call, so send an empty record ({}); each record performs the action once.

  • Subscriber ID (required): The Kit ID of the subscriber. Use List Subscribers to find it.
  • Side effect: The subscriber stops receiving all future emails. Consent is revoked, so treat this as permanent.
  • Reference: Kit API documentation

Update Subscriber

Updates a subscriber's email_address, first_name or custom field values from each record.

  • Subscriber ID (required): The Kit ID of the subscriber. Use List Subscribers to find it.
  • Side effect: Changes the subscriber's stored details.
  • Reference: Kit API documentation

Update Subscriber Location

Updates a subscriber's pinned location from each record's location object.

  • Subscriber ID (required): The Kit ID of the subscriber. Use List Subscribers to find it.
  • Side effect: Changes the subscriber's pinned location.
  • Reference: Kit API documentation

Tags​

Create Tag

Creates a tag from each record's name.

Remove Tag from Subscriber

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.
  • Side effect: Removes the tag from the subscriber.
  • Reference: Kit API documentation

Remove Tag from Subscriber by Email

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.
  • Side effect: Removes the tag from the subscriber.
  • Reference: Kit API documentation

Tag 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.
  • Side effect: Adds the tag to the subscriber.
  • Reference: Kit API documentation

Tag Subscriber by Email

Tags an existing subscriber, identified by each record's email_address.

  • Tag ID (required): The Kit ID of the tag. Use List Tags to find it.
  • Side effect: Adds the tag to the subscriber.
  • Reference: Kit API documentation

Update Tag

Renames a tag from each record's name.

  • Tag ID (required): The Kit ID of the tag. Use List Tags to find it.
  • Side effect: Renames the tag.
  • Reference: Kit API documentation

Forms​

Add Subscriber to Form

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.
  • Side effect: Adds the subscriber to the form.
  • Reference: Kit API documentation

Add Subscriber to Form by Email

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.
  • Side effect: Adds the subscriber to the form.
  • Reference: Kit API documentation

Sequences and sequence emails​

Add Subscriber to Sequence

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.
  • Reference: Kit API documentation

Add Subscriber to Sequence by Email

Adds an existing subscriber, identified by each record's email_address, to a sequence.

  • Sequence ID (required): The Kit ID of the sequence. Use List Sequences to find it.
  • Side effect: The sequence's published emails start sending to the subscriber.
  • Reference: Kit API documentation

Create Sequence

Creates an empty email sequence from each record; name is required.

Create Sequence Email

Adds an email to a sequence from each record (subject, delay_value, delay_unit).

  • Sequence ID (required): The Kit ID of the sequence. Use List Sequences to find it.
  • Side effect: With published: true, the email sends to the sequence's subscribers.
  • Reference: Kit API documentation

Delete Sequence

Deletes a sequence.

  • Sequence ID (required): The Kit ID of the sequence. Use List Sequences to find it.
  • Side effect: Deletes the sequence and stops deliveries to its subscribers.
  • Reference: Kit API documentation

Delete Sequence Email

Removes an email from a sequence.

  • Sequence ID (required): The Kit ID of the sequence. Use List Sequences to find it.
  • Email ID (required): The Kit ID of the email. Use List Sequence Emails to find it.
  • Side effect: Subscribers still in the queue skip the email.
  • Reference: Kit API documentation

Update Sequence

Updates a sequence's name, schedule, sender, template or flags from each record.

  • Sequence ID (required): The Kit ID of the sequence. Use List Sequences to find it.
  • Side effect: active: true activates the sequence.
  • Reference: Kit API documentation

Update Sequence Email

Updates a sequence email from each record. Only the fields sent change.

  • Sequence ID (required): The Kit ID of the sequence. Use List Sequences to find it.
  • Email ID (required): The Kit ID of the email. Use List Sequence Emails to find it.
  • Side effect: published: true sends the email to the sequence's subscribers.
  • Reference: Kit API documentation

Broadcasts​

Create Broadcast

Creates a broadcast from each record.

  • 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.
  • Reference: Kit API documentation

Delete Broadcast

Deletes a draft or scheduled broadcast. Kit returns a 422 error for broadcasts that were already sent.

  • Broadcast ID (required): The Kit ID of the broadcast. Use List Broadcasts to find it.
  • Side effect: Permanently deletes the broadcast.
  • Reference: Kit API documentation

Update Broadcast

Updates a broadcast from each record. Send only the fields to change.

  • Broadcast ID (required): The Kit ID of the broadcast. Use List Broadcasts to find it.
  • Side effect: public: true with send_at schedules the email to subscribers. Leave out send_at and public to keep a draft.
  • Reference: Kit API documentation

Custom fields​

Create Custom Field

Creates a subscriber custom field from each record's label, which must be unique in the account.

Delete Custom Field

Deletes a custom field.

  • Custom Field ID (required): The Kit ID of the custom field. Use List Custom Fields to find it.
  • Side effect: Deletes the field and its value on every subscriber.
  • Reference: Kit API documentation

Update Custom Field

Renames a custom field's label from each record. The field's key changes; its name does not.

  • Custom Field ID (required): The Kit ID of the custom field. Use List Custom Fields to find it.
  • Side effect: Renames the field for every subscriber.
  • Reference: Kit API documentation

Segments, email templates, snippets and posts​

Create Snippet

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.

Update Snippet

Updates a snippet from each record.

  • Snippet ID (required): The Kit ID of the snippet. Use List Snippets to find it.
  • Side effect: Emails that use the snippet get the new content the next time they send.
  • Reference: Kit API documentation

Webhooks​

Create Legacy Webhook

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.

Create Webhook Endpoint

Registers a public URL to receive event deliveries, from each record's url and events.

  • Side effect: Kit starts sending events to the URL. The signing secret appears only in Kit's response, and Nexla does not keep it.
  • Reference: Kit API documentation

Delete Legacy Webhook

Deletes a legacy webhook.

  • Webhook ID (required): The Kit ID of the webhook. Use List Legacy Webhooks to find it.
  • Side effect: Kit stops delivering events to it.
  • Reference: Kit API documentation

Delete Webhook Endpoint

Deletes a webhook endpoint.

  • Endpoint ID (required): The Kit ID of the endpoint. Use List Webhook Endpoints to find it.
  • Side effect: Kit stops delivering events to it.
  • Reference: Kit API documentation

Update Webhook Endpoint

Updates a webhook endpoint's name, url, description, status or events from each record.

  • Endpoint ID (required): The Kit ID of the endpoint. Use List Webhook Endpoints to find it.
  • Side effect: Changes where and which events Kit delivers.
  • Reference: Kit API documentation

Legacy v3 templates​

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.

Create a 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.

Manual configuration​

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.

Save & activate​

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.