Systeme

Systeme.io is an all-in-one marketing platform for building sales funnels, sending email campaigns, and hosting online courses and memberships. Its public REST API exposes contacts, tags, contact fields, funnels, funnel steps, newsletters, courses, and enrollments. Nexla connects to the Systeme API to ingest these resources into your data flows and to push records back to create and manage them.

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

Prerequisites

Before creating a Systeme credential, you need a public API key from your Systeme.io account. Systeme authenticates every API request with this key, sent in the X-API-Key request header.

To obtain your Systeme public API key, follow these steps:

1. Sign in to your Systeme.io account.

2. Click the settings gear icon in the top-right corner, or click your profile picture and select Settings.

3. In the left-side menu, select Public API Keys.

4. Click Create to open the create public API key dialog.

5. Enter a name for the key and, optionally, an expiration date and time. Leave the Expiration field empty to keep the key active indefinitely.

6. Copy the generated API key token immediately. Systeme does not display the token again after this step.

7. Store the token securely, as you will need it to configure your Nexla credential. The token is sensitive and should be kept confidential.

An account can hold a maximum of three API keys at any time, and existing keys can be revoked from the same Public API Keys screen. If a key is compromised, revoke it in Systeme and generate a new one. For detailed information about authentication and available resources, see the Systeme.io Public API documentation.

Authenticate

Credentials required

An authentication method that requires sending a unique secret token with each API request

Field	Required	Secret	Description
API Key Value	Yes	Yes	An encoded string value used as a secret token to authenticate API requests

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.

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

3. Enter your Systeme public API key in the API Key Value field. This is the token you generated in Prerequisites. Nexla sends it in the X-API-Key header for all API requests to the Systeme API, so it must be kept confidential.

   If your API key is compromised, revoke it in your Systeme account under Public API Keys and generate a new one. The API key grants access to your Systeme account data and should be treated as sensitive information.

   For detailed information about API authentication and available resources, see the Systeme.io Public API documentation.

4. 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 Systeme connector tile, then select the credential that will be used to connect to the Systeme instance, and click Next; or, create a new Systeme 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 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.

[Rest API] Retrieve contact collection

Retrieve contact collection.

This endpoint returns a collection of contacts from your Systeme account. Optional query parameters let you page through results and control ordering. For detailed information about the response structure and available parameters, see the Systeme.io Public API documentation.

[Rest API] Retrieve a single contact

Retrieve a single contact.

This endpoint returns a single contact identified by its contact ID. For detailed information about the response structure, see the Systeme.io Public API documentation.

[Rest API] Retrieve tag collection

Retrieve tag collection.

This endpoint returns a collection of tags defined in your Systeme account. For detailed information about the response structure, see the Systeme.io Public API documentation.

[Rest API] Retrieve a single tag

Retrieve a single tag.

This endpoint returns a single tag identified by its tag ID. For detailed information about the response structure, see the Systeme.io Public API documentation.

[Rest API] Retrieve contact field collection

Retrieve contact field collection.

This endpoint returns the collection of contact fields configured in your Systeme account. For detailed information about the response structure, see the Systeme.io Public API documentation.

[Rest API] Retrieve funnel collection

Retrieve funnel collection.

This endpoint returns a collection of funnels from your Systeme account. For detailed information about the response structure, see the Systeme.io Public API documentation.

[Rest API] Retrieve a single funnel

Retrieve a single funnel.

This endpoint returns a single funnel identified by its funnel ID. For detailed information about the response structure, see the Systeme.io Public API documentation.

[Rest API] Retrieve funnel steps collection

Retrieve funnel steps collection.

This endpoint returns the collection of steps for a funnel identified by its funnel ID. For detailed information about the response structure, see the Systeme.io Public API documentation.

[Rest API] Retrieve a single funnel step

Retrieve a single funnel step.

This endpoint returns a single funnel step identified by its funnel step ID. For detailed information about the response structure, see the Systeme.io Public API documentation.

[Rest API] Retrieve newsletter collection

Retrieve newsletter collection.

This endpoint returns a collection of newsletters from your Systeme account. For detailed information about the response structure, see the Systeme.io Public API documentation.

[Rest API] Retrieve a single newsletter

Retrieve a single newsletter.

This endpoint returns a single newsletter identified by its newsletter ID. For detailed information about the response structure, see the Systeme.io Public API documentation.

[Rest API] Retrieve course collection

Retrieve course collection.

This endpoint returns a collection of courses from your Systeme account. For detailed information about the response structure, see the Systeme.io Public API documentation.

[Rest API] Retrieve enrollment collection

Retrieve enrollment collection.

This endpoint returns a collection of course enrollments from your Systeme account. For detailed information about the response structure, see the Systeme.io Public 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

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

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.

Use as a destination

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 the Systeme account, and click Next; or, create a new Systeme 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 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.

[Rest API] Create a contact

Create a contact.

This endpoint sends each record from your Nexset as a JSON request body to create a new contact in your Systeme account. The request body must match the format expected by the Systeme API. For detailed information about the request body and available fields, see the Systeme.io Public API documentation.

[Rest API] Update a contact

Update a contact.

This endpoint updates an existing contact identified by its contact ID, using the JSON request body from each Nexset record. For detailed information about the request body and available fields, see the Systeme.io Public API documentation.

[Rest API] Remove a contact

Remove a contact.

This endpoint deletes a contact identified by its contact ID. For detailed information, see the Systeme.io Public API documentation.

[Rest API] Assign a tag to a contact

Assign a tag to a contact.

This endpoint assigns a tag to a contact identified by its contact ID, using the JSON request body from each Nexset record. For detailed information about the request body, see the Systeme.io Public API documentation.

[Rest API] Remove a tag from a contact

Remove a tag from a contact.

This endpoint removes a tag from a contact identified by its contact ID. For detailed information, see the Systeme.io Public API documentation.

[Rest API] Create a new tag

Create a new tag.

This endpoint sends each record from your Nexset as a JSON request body to create a new tag in your Systeme account. For detailed information about the request body, see the Systeme.io Public API documentation.

[Rest API] Replace a tag

Replace a tag.

This endpoint replaces an existing tag identified by its tag ID, using the JSON request body from each Nexset record. For detailed information about the request body, see the Systeme.io Public API documentation.

[Rest API] Remove a tag

Remove a tag.

This endpoint deletes a tag identified by its tag ID. For detailed information, see the Systeme.io Public API documentation.

[Rest API] Create a contact field

Create a contact field.

This endpoint sends each record from your Nexset as a JSON request body to create a new contact field in your Systeme account. For detailed information about the request body, see the Systeme.io Public API documentation.

[Rest API] Update a contact field

Update a contact field.

This endpoint updates an existing contact field identified by its slug, using the JSON request body from each Nexset record. For detailed information about the request body, see the Systeme.io Public API documentation.

[Rest API] Remove a contact field

Remove a contact field.

This endpoint deletes a contact field identified by its slug. For detailed information, see the Systeme.io Public API documentation.

[Rest API] Create a funnel

Create a funnel.

This endpoint sends each record from your Nexset as a JSON request body to create a new funnel in your Systeme account. For detailed information about the request body, see the Systeme.io Public API documentation.

[Rest API] Create a funnel step

Create a funnel step.

This endpoint creates a new step for a funnel identified by its funnel ID, using the JSON request body from each Nexset record. For detailed information about the request body, see the Systeme.io Public API documentation.

[Rest API] Create a newsletter

Create a newsletter.

This endpoint sends each record from your Nexset as a JSON request body to create a new newsletter in your Systeme account. For detailed information about the request body, see the Systeme.io Public API documentation.

[Rest API] Replace a newsletter

Replace a newsletter.

This endpoint replaces an existing newsletter identified by its newsletter ID, using the JSON request body from each Nexset record. For detailed information about the request body, see the Systeme.io Public API documentation.

[Rest API] Create an enrollment for a course

Create an enrollment for a course.

This endpoint creates an enrollment for a course identified by its course ID, using the JSON request body from each Nexset record. For detailed information about the request body, see the Systeme.io Public API documentation.

[Rest API] Remove an enrollment

Remove an enrollment.

This endpoint removes a course enrollment identified by its enrollment ID. For detailed information, see the Systeme.io Public API documentation.

Manual configuration

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.

Systeme APIs expect JSON format for create, update, and replace operations. For update, replace, and delete operations, include the ID or slug of the object at the end of the endpoint URL.

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