Systeme.io is an all-in-one marketing platform for building sales funnels, sending email campaigns, and hosting online courses, communities, and memberships. The Systeme connector reads contacts, tags, funnels, newsletters, campaigns, automation emails and email statistics, automation rules, courses, communities, products, offers, coupons, bookings, SMS templates, and webhooks, and can create, update, and delete most of them, send newsletters, and enroll contacts in courses.
Power end-to-end data operations for your Systeme API with Nexla. Our bi-directional Systeme connector is purpose-built for Systeme, 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 Systeme or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Systeme 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 the Systeme.io Public API with a public API key from your Systeme.io account. Systeme authenticates every request with this key, sent in the X-API-Key request header. To create a key:
Sign in to your Systeme.io account.
Click your profile picture, and select Settings.
In the left menu, select MCP & API keys.
In the Public API keys section, click Create.
Enter a unique name for the key and, optionally, an expiration date and time. Leave the Expiration field empty to keep the key active indefinitely, and click Save.
Copy the key immediately. Systeme shows the key only once, right after you create it; if you did not copy it, delete the key and create a new one.
An account can hold up to three public API keys, and Systeme sends an email notification each time a key is created. The key gives access to all of your account's data, so keep it confidential. For details, see Systeme's How to use the systeme.io public API help article.
Systeme API rate limits
Systeme applies a rate limit that is shared by all of the API keys on your account. Requests over the limit receive an HTTP 429 Too Many Requests response with a Retry-After header. Templates that page through large collections, such as contacts, make one request per page of 100 records. See the rate-limiting section of the Systeme Public API documentation for details.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter your Systeme public API key in the API Key Value field. This is the key you created in Prerequisites. Nexla sends it in the X-API-Key header of every request to the Systeme API.
If your API key is compromised, delete it in Systeme under Settings > MCP & API keys, create a new one, and update the API Key Value on this credential.
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.
Nexla tests the credential by reading the contact list from your Systeme account.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Systeme connector tile, then select the credential that will be used to connect to your Systeme account, and click Next; or, create a new Systeme 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 Systeme 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 area.
Templates that say "Results are paged automatically" read every page, 100 records at a time, by passing the ID of the last record on each page to the next request. Templates that need an ID, such as a contact or course ID, read one object; use the matching list template to find the ID.
Lists all contacts in the Systeme account, including each contact's ID, email address, field values, tags, and registration date. Results are paged automatically.
Lists statistics per newsletter for a send-date range of up to 31 days. Systeme marks this API as beta. Returns at most the first 100 rows.
Enter the Date From and Date To of the send-date range, in YYYY-MM-DD format in the account's time zone. The range can span at most 31 days, and Date To cannot be in the future. The defaults, {now-30} and {now}, cover the last 30 days.
Retrieves total and per-day newsletter statistics for a send-date range of up to 31 days.
Enter the Date From and Date To of the send-date range, in YYYY-MM-DD format in the account's time zone. The range can span at most 31 days, and Date To cannot be in the future. The defaults, {now-30} and {now}, cover the last 30 days.
Lists statistics per campaign step for a send-date range of up to 31 days. Systeme marks this API as beta. Returns at most the first 100 rows.
Enter the Date From and Date To of the send-date range, in YYYY-MM-DD format in the account's time zone. The range can span at most 31 days, and Date To cannot be in the future. The defaults, {now-30} and {now}, cover the last 30 days.
Retrieves total and per-day campaign step statistics for a send-date range of up to 31 days.
Enter the Date From and Date To of the send-date range, in YYYY-MM-DD format in the account's time zone. The range can span at most 31 days, and Date To cannot be in the future. The defaults, {now-30} and {now}, cover the last 30 days.
Lists statistics per automation email for a send-date range of up to 31 days. Systeme marks this API as beta. Returns at most the first 100 rows.
Enter the Date From and Date To of the send-date range, in YYYY-MM-DD format in the account's time zone. The range can span at most 31 days, and Date To cannot be in the future. The defaults, {now-30} and {now}, cover the last 30 days.
Retrieves total and per-day automation email statistics for a send-date range of up to 31 days.
Enter the Date From and Date To of the send-date range, in YYYY-MM-DD format in the account's time zone. The range can span at most 31 days, and Date To cannot be in the future. The defaults, {now-30} and {now}, cover the last 30 days.
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.
Systeme data sources can also be manually configured to ingest data from any valid Systeme API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters such as the optional filters on the contacts list. 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. Systeme endpoint URLs take the form https://api.systeme.io/api/..., and collection responses hold their records in $.items[*]; see the Systeme API reference for the available endpoints.
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 Systeme 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 Systeme destination, and select the Send to Destination option from the menu. Select the Systeme connector from the list of available destination connectors, then select the credential that will be used to connect to your Systeme account, and click Next; or, create a new Systeme credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Systeme 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, one record at a time. ID settings, such as a contact, course, or newsletter ID, are fixed on the destination and apply to every record it sends, so each record acts on the same object. Update templates send the record as a JSON merge patch (application/merge-patch+json): only the fields present in the record change. Templates marked Side effect delete data, send email, or change access in ways that cannot be undone from Nexla.
Systeme destinations can also be manually configured to send data to any valid Systeme 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.
The Systeme API expects JSON request bodies; its PATCH operations accept only application/merge-patch+json. For update, replace, and delete operations, put the ID or slug of the object at the end of the endpoint URL.
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 Systeme endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Systeme endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.