Seismic Data Source
The Seismic connector enables you to extract reporting and operational data directly from your Seismic Enablement Cloud instance into Nexla. Use this connector to build data pipelines that pull content usage analytics, user activity, AI engagement metrics, program data, library contents, and team management data from Seismic's Reporting API — ideal for feeding data lakes, data warehouses, and downstream analytics platforms.
Seismic
Create a New Data Flow
-
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Then, select the desired flow type from the list, and click the Create button.
-
Select the Seismic connector tile from the list of available connectors. Then, select the credential that will be used to connect to the Seismic instance, and click Next; or, create a new Seismic credential for use in this flow.
-
In Nexla, Seismic data sources can be created using pre-built endpoint templates, which expedite source setup for common Seismic Reporting API endpoints. Each template is designed specifically for the corresponding Seismic endpoint, making source configuration easy and efficient.
• To configure this source using a template, follow the instructions in Configure Using a Template.Seismic sources can also be configured manually, allowing you to ingest data from Seismic endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
• To configure this source manually, follow the instructions in Configure Manually.
Configure Using a Template
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Seismic Reporting API endpoints. Each template is designed specifically for the corresponding Seismic endpoint, making data source setup easy and efficient.
Endpoint Settings
- 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. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.
Endpoint Testing
Once the selected endpoint template has been configured, Nexla can retrieve a sample of the data that will be fetched according to the current settings. This allows users to verify that the source is configured correctly before saving.
-
To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.
-
If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.
Configure Manually
Seismic data sources can be manually configured to ingest data from any valid Seismic API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations, such as endpoints from Seismic's Integration API, Content Management API, or other API surfaces beyond the Reporting API.
With manual configuration, you can also create more complex Seismic sources, such as sources that use chained API calls to fetch data from multiple endpoints or sources that require custom request parameters.
API Method
-
To manually configure this source, select the Advanced tab at the top of the configuration screen.
-
Select the API method that will be used for calls to the Seismic API from the Method pulldown menu. The most common methods are:
- GET: For retrieving data from the Seismic API (used by all Seismic Reporting API endpoints)
- POST: For sending data to the API or triggering actions (used by certain Seismic Integration API endpoints)
API Endpoint URL
- Enter the URL of the Seismic API endpoint from which this source will fetch data in the Set API URL field. All Seismic API endpoints begin with
https://api.seismic.com/. For example, the Reporting API fields endpoint ishttps://api.seismic.com/reporting/fields.
Ensure the API endpoint URL is correct and accessible with your current credentials. The credential must include the OAuth2 scope required for the target endpoint. Refer to the Seismic API Reference for the complete list of available endpoints and their required scopes.
Date/Time Macros (API URL)
Optionally, the API URL can be customized using macros—all macros added to the API URL will be converted into values when Nexla executes the API call. Macros are dynamic placeholders that allow you to create flexible API endpoints that can adapt to different time periods or data requirements. This is particularly useful for Seismic Reporting API endpoints that accept date range parameters.
Most Seismic Reporting API endpoints accept timestamp parameters in ISO 8601 format (e.g., modifiedAtStartTime=2026-05-01T00:00:00Z). Use Nexla's datetime macros to dynamically set these parameters for automated incremental data loads.
-
To add a macro, type
{at the appropriate position in the API URL (within the Set API URL field), and select the desired macro from the dropdown list.{now}– The current datetime{now-1}– The datetime one time unit before the current datetime{now+1}– The datetime one time unit after the current datetimecustom– Datetime macros can reference any number of time units before or after the current datetime—for example, enter(now-7)to indicate the datetime seven time units before the current datetime
-
Select the format that will be applied to datetime macros from the Date Format for Date/Time Macro pulldown menu. Seismic Reporting API endpoints that accept timestamps expect ISO 8601 format (
yyyy-MM-dd'T'HH:mm:ss'Z'), while the Daily Active Users endpoint expectsyyyy-MM-dd. -
Select the datetime unit that will be used to perform mathematical operations in the included macro(s) from the Time Unit for Operations pulldown menu—for example, for the macro
{now-1}, whenDayis selected,{now-1}will be converted to the datetime one day before the current datetime.
Lookup-Based Macros (API URL)
Column values from existing lookups can also be included as macros in the API URL. Lookup-based macros allow you to reference data from previously configured data sources or lookups, enabling dynamic API endpoints that can adapt based on existing data.
Lookup-based macros are particularly useful for Seismic endpoints that require specific IDs (such as Channel ID or Post ID) that may come from a prior step in a multi-source data flow.
-
To include a lookup column value macro, select the relevant lookup from the Add Lookups to Supported Macros pulldown menu.
-
Type
{at the appropriate position in the API URL, and select the lookup column-based macro from the dropdown list. Lookup-based macros are automatically populated into the macro list when a lookup is selected in the Add Lookups to Supported Macros pulldown menu.
Path to Data
If only a subset of the data returned by the Seismic API endpoint is needed, you can designate the part(s) of the response that should be included in the Nexset(s) produced from this source. Seismic API responses typically return data nested inside a top-level array property.
Path to Data is important when working with Seismic API responses, as Seismic wraps result records inside named arrays. For example, the Reporting API typically wraps results in $.records[*], $.data[*], $.fields[*], or $.tables[*] depending on the endpoint.
-
To specify which data should be treated as relevant in responses from this source, enter the path to the relevant data in the Set Path to Data in Response field.
- For responses in JSON format, enter the JSON path that points to the object or array that should be treated as relevant data. JSON paths use dot notation (e.g.,
$.records[*]to access the records array, or$.data[*]to access the data array).
Path to Data Example:For the Seismic Content Usage History endpoint, the response wraps records inside a top-level
recordsarray. Enter$.records[*]as the path to data to treat each usage record as a separate row. - For responses in JSON format, enter the JSON path that points to the object or array that should be treated as relevant data. JSON paths use dot notation (e.g.,
Autogenerate Path Suggestions
Nexla can also autogenerate data path suggestions based on the response from the API endpoint. These suggested paths can be used as-is or modified to exactly suit your needs.
-
To use this feature, click the Test button next to the Set API URL field to fetch a sample response from the API endpoint. Suggested data paths generated based on the content & format of the response will be displayed in the Suggestions box below the Set Path to Data in Response field.
-
Click on a suggestion to automatically populate the Set Path to Data in Response field with the corresponding path. The populated path can be modified directly within the field if further customization is needed.
Metadata
If metadata is included in the response but is located outside of the defined path to relevant data, you can configure Nexla to include this data as common metadata in each record. For example, the Seismic Reporting API may return pagination metadata or summary counts at the top level of the response alongside the primary records array.
Metadata paths are particularly useful for preserving API response context like request IDs, timestamps, or total count values that apply to all records in the Seismic API response.
-
To specify the location of metadata that should be included with each record, enter the path to the relevant metadata in the Path to Metadata in Response field.
- For responses in JSON format, enter the JSON path to the object or array that contains the metadata.
Request Headers
-
If Nexla should include any additional request headers in API calls to this source, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g.,
header1:value1,header2:value2).You do not need to include an Authorization header — it is automatically handled by the Seismic OAuth2 credential. All Seismic Reporting API endpoints require
Content-Type: application/json, which Nexla includes automatically.
Endpoint Testing
After configuring all settings for the selected endpoint, Nexla can retrieve a sample of the data that will be fetched according to the current configuration. This allows users to verify that the source is configured correctly before saving.
-
To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.
-
If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.
Save & Activate the Source
- Once all of the relevant steps in the above sections have been completed, click the Create button in the upper right corner of the screen to save and create the new Seismic 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.