Convertkit Integrations

Unknown Facts About Convertkit Integrations

The 3-Minute Rule for Convertkit IntegrationsUnknown Facts About Convertkit Integrations

Unknown Facts About Convertkit Integrations

e-mail – Subscriber email address. first_name – Customer given name. fields – Things of key/value pairs for customized fields (the custom field must exist prior to you can utilize it here). tags – Variety of tag ids to subscribe to. courses – Array of sequence ids to register for. You should add the subscriber to each course individually.

The Definitive Guide to Convertkit IntegrationsWhat Does Convertkit Integrations Do?

You need to add the subscriber to the type straight. name – Customer very first name. You ought to choose using first_name noted above. Example request curl class=” o” >= Example response “total_subscriptions”: 2, “page”: 1, “total_pages”: 1, “memberships”: [“id”: 1, “state”: “active”, “created_at”: “2016-02-28T 08:07:00 Z”, “source”: null, “referrer”: null, “subscribable_id”: 1, “subscribable_type”: “course”, “customer”: “id”: 1, “first_name”: “Jon”, “email_address”: “[email protected]”, “state”: “active”, “created_at”: “2016-02-28T 08:07:00 Z”, “fields”: “last_name”: “Snow”,, “id”: 2, “state”: “active”, “created_at”: “2016-02-27T 08:07:00 Z”, “source”: null, “referrer”: null, “subscribable_id”: 1, “subscribable_type”: “course”, “customer”: “id”: 2, “first_name”: “Arya”, “email_address”: “[email protected]”, “state”: “active”, “created_at”: “2016-02-27T 08:07:00 Z”, “fields”: “last_name”: “Stark”,] List subscriptions to a sequence including customer data.

The smart Trick of Convertkit Integrations That Nobody is Talking AboutThe Ultimate Guide To Convertkit Integrations

asc is the default order. subscriber_state?-? active?or?? cancelled: receive just active customers or cancelled customers Example demand curl class=” o” >= Example action “tags”: [“id”: 1, “name”: “House Stark”, “created_at”: “2016-02-28T 08:07:00 Z”, “id”: 2, “name”: “House Lannister”, “created_at”: “2016-02-28T 08:07:00 Z”] Returns a list of tags for the account.

Example request Single tag curl -X POST -H ‘Content-Type: application/json’ \ -d’ “api_key”: “”, \ “tag”: \ “name”: “Example Tag” \’ Numerous tags curl -X POST -H ‘Content-Type: application/json’ \ -d’ “api_key”: “”, \ “tag”: [\ “name”: “Example Tag” \, \ “name”: “Example Tag 2” \]’ Example reaction “account_id”: 1, “created_at”: “2017-04-12T 11:10:32 Z”, “deleted_at”: null, “id”: 1, “name”: “Example Tag”, “state”: “offered”, “updated_at”: “2017-04-12T 11:10:32 Z” A demand to develop numerous tags will receive a JSON selection with the same type of things: [“account_id”: 1, “created_at”: “2017-04-12T 11:10:32 Z”, “deleted_at”: null, “id”: 1, “name”: “Example Tag”, “state”: “readily available”, “updated_at”: “2017-04-12T 11:10:32 Z”, “account_id”: 1, “created_at”: “2017-04-12T 11:11:566 Z”, “deleted_at”: null, “id”: 1, “name”: “Example Tag 2”, “state”: “readily available”, “updated_at”: “2017-04-12T 11:11:566 Z”] POST/ v 3/tags api_key – Your account API secret.

The Single Strategy To Use For Convertkit Integrations

Subscribe an e-mail address to a tag to have that tag applied to the customer with that e-mail address. POST/ v 3/tags/ # tag_id/ subscribe api_key – Your account API key. email – Subscriber e-mail address. first_name – Customer given name. fields – Item of key/value sets for custom-made fields (the custom field need to exist prior to you can utilize it here).

courses – Range of series ids to sign up for. You should add the customer to the series straight. types – Array of kind ids to register for. You ought to add the subscriber to the type straight. name – Customer first name. You need to choose utilizing first_name listed above. Example demand curl -X DELETE class=” o” >= Example reaction “id”: 1, “name”: “Home Stark”, “created_at”: “2016-02-28T 08:07:00 Z” DELETE/ v 3/subscribers/ # subscriber_id/ tags/ # tag_id api_secret – Your api secret key.

e-mail – Subscriber e-mail address. Example demand curl class=” o” >= Example response “total_subscriptions”: 2, “page”: 1, “total_pages”: 1, “memberships”: [“id”: 1, “state”: “active”, “created_at”: “2016-02-28T 08:07:00 Z”, “source”: null, “referrer”: null, “subscribable_id”: 1, “subscribable_type”: “tag”, “customer”: “id”: 1, “first_name”: “Jon”, “email_address”: “[email protected]”, “state”: “active”, “created_at”: “2016-02-28T 08:07:00 Z”, “fields”: “last_name”: “Snow”,, “id”: 2, “state”: “active”, “created_at”: “2016-02-27T 08:07:00 Z”, “source”: null, “referrer”: null, “subscribable_id”: 1, “subscribable_type”: “tag”, “subscriber”: “id”: 2, “first_name”: “Arya”, “email_address”: “[email protected]”, “state”: “active”, “created_at”: “2016-02-27T 08:07:00 Z”, “fields”: “last_name”: “Stark”,] List subscriptions to a tag consisting of customer data.

asc is the default order. subscriber_state – active or cancelled: receive only active subscribers or cancelled subscribers Example demand curl class=” o” >=& from= 2016-02-01 & to= 2015-02-28 Example action “total_subscribers”: 3, “page”: 1, “total_pages”: 1, “customers”: [“id”: 1, “first_name”: “Jon”, “email_address”: “[email protected]”, “state”: “active”, “created_at”: “2016-02-28T 08:07:00 Z”, “fields”: “last_name”: “Snow”, “id”: 2, “first_name”: “Arya”, “email_address”: “[email protected]”, “state”: “active”, “created_at”: “2016-02-28T 08:07:00 Z”, “fields”: “last_name”: “Stark”] Returns a list of your customers.

Some Known Factual Statements About Convertkit Integrations

Browse subscribers by email address by providing the email_address param. GET/ v 3/subscribers api_secret – Your api secret key. page – Page for paginated results. from – Filter customers added on or after this date (format yyyy-mm-dd). to – Filter customers included on or prior to this date (format yyyy-mm-dd). updated_from – Filter subscribers who have actually been upgraded after this date (format yyyy-mm-dd) updated_to – Filter subscribers who have been upgraded prior to this date (format yyyy-mm-dd) sort_order – Sort order for outcomes (asc or desc).

email_address – Search subscribers by email address. Example demand curl class=” o” >= Example reaction “customer”: “id”: 1, “first_name”: “Jon”, “email_address”: “[email protected]”, “state”: “active”, “created_at”: “2016-02-28T 08:07:00 Z”, “fields”: “last_name”: “Snow” Returns data for a single subscriber GET/ v 3/subscribers/ # subscriber_id api_secret – Your api secret key. Example demand curl -X PUT class=” se” > \ -H ‘Content-Type: application/json’ \ -d’ “api_secret”: “”, \ “first_name”: “Jon”, \ “email_address”: “[email protected]”, \ “fields”: \ “last_name”: “Snow” \’ Example action: Up to 10 custom-made fields, status 200 “customer”: “id”: 1, “first_name”: “Jon”, “email_address”: “[email protected]”, “state”: “active”, “created_at”: “2016-02-28T 08:07:00 Z”, “fields”: “last_name”: “Snow” Example response: 11 to 125 custom-made fields, status 202 “customer”: “id”: 1, “first_name”: “Jon”, “email_address”: “[email protected]”, “state”: “active”, “created_at”: “2016-02-28T 08:07:00 Z”, “fields”: “last_name”: “Snow” Updates the information for a single customer.

first_name – Upgraded first name for the subscriber. email_address – Upgraded e-mail address for the customer. fields – Updated custom-made fields for your subscriber as object of key/value sets (the custom-made field need to exist prior to you can utilize it here). NOTE: The API reaction returned when upgrading custom-made fields depends on the number of custom-made fields in the demand, as shown by the examples at right.

  • Form Integrations
  • Example response
  • required parameter
  • Example Request
  • Example response
  • Full Integration
  • required parameter
  • Example response
  • official integration
  • Example Request
  • Example response
  • required parameter
  • Example response
  • Integrations page
  • Example response
  • required parameter
  • mailing list
  • Example Request
  • Example response
  • required parameter
  • Example response
  • required parameter
  • Example Request
  • Example response
  • required parameter
  • Example response
  • required parameter
  • Example response
  • Example Request
  • active development
  • Example Request
  • Example response
  • underscored representationv
  • required parameter
  • Example Request
  • Example response
  • subscribable type
  • Example response
  • required parameter
  • Full Integration
  • Example Request
  • embed code
  • official integration
  • Example response
  • key/value pairs
  • required parameter
  • Subscriber Field
  • Click Save
  • Subscriber Field
  • required parameter
  • embed code
  • Example response
  • Example Request
  • left side
  • Optional parameters
  • Subscriber Field
  • required parameter
  • mailing list
  • Click Integrations
  • embed code
  • default order
  • Example response
  • required parameter
  • direct integration
  • key/value pairs
  • Subscriber Field
  • Optional parameters
  • default order
  • Example response
  • Example Request
  • required parameter
  • webhook automation
  • Optional parameters
  • Standard Builder
  • key/value pairs
  • default order
  • Example Request
  • Subscriber Field
  • required parameter
  • trigger name
  • required parameter
  • subscriber data
  • webhook automation
  • line item
  • Click Integrations
  • large integration
  • required parameter
  • Standard Builder
  • Example response
  • Subscriber Field
  • form fields
  • larger integration
  • exact same predefined options/values
  • required parameter
  • Standard Builder
  • subscriber data
  • Product variants
  • Optional parameters
  • line item
  • Example response
  • required parameter
  • Example response
  • required parameter
  • unique identifiers
  • form fields
  • subscriber data
  • Subscriber Field
  • Example Request
  • Example response
  • Optional parameters
  • response body
  • Example Request
  • subscriber data
  • response body
  • required parameter
  • line item
  • Example response
  • form fields
  • Subscriber Field
  • Optional parameters
  • subscriber data
  • specific features
  • required parameter
  • Example response
  • subscriber data
  • Optional parameters
  • Optional parameters
  • specific automations
  • Optional parameters
  • Experience Manager interface
  • API Secret section
  • required parameter
  • line item
  • latest content
  • subscriber data
  • Optional parameters
  • activate name
  • Example Request
  • exponential backoff
  • Example response
  • Example Request
  • underscored representation
  • Landing Page
  • Optional parameters
  • Optional parameters
  • required parameter
  • Example response