SplashThat

SplashThat is an event marketing platform that helps businesses create, manage, and promote events with tools for event pages, ticketing, attendee management, and marketing automation.

Power end-to-end data operations for your SplashThat API with Nexla. Our bi-directional SplashThat connector is purpose-built for SplashThat, 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 SplashThat or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your SplashThat 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 SplashThat credential, you need to obtain your Client ID, Client Secret, Username, and Password from your SplashThat account. SplashThat uses OAuth2 2-legged authentication (password grant type) for all API requests, with credentials sent in the request body to obtain an access token.

To obtain your SplashThat credentials, follow these steps:

1. Sign in to your SplashThat account using your administrator credentials.

2. Navigate to your account settings or API management section in the SplashThat interface.

3. Look for the API or OAuth section in your account settings, or navigate to Settings > API or Account > API Settings.

4. If you don't have OAuth credentials yet, look for the option to create or register an OAuth application.

5. Click Create OAuth App or Register Application to create a new OAuth application.

6. Configure your OAuth application settings:

   • Enter a name for the application (e.g., "Nexla Integration")
   • Review and select the permissions or scopes for the application (typically user scope)
   • Note the Client ID and Client Secret that are generated

7. Copy the Client ID and Client Secret immediately after they are generated, as the Client Secret may not be accessible again after you navigate away from the page.

8. Your Username and Password are your SplashThat account credentials that you use to sign in to your SplashThat account.

9. Store all credentials securely, as you will need them to configure your Nexla credential. The Client ID, Client Secret, Username, and Password are sensitive information and should be kept confidential.

The OAuth2 credentials are used to obtain an access token via the password grant type. The Client ID and Client Secret are sent along with your Username and Password in the OAuth token request to obtain an access token. The access token is then sent in the Authorization: Bearer {token} header for all API requests to the SplashThat API. The token authenticates your requests and grants access to SplashThat resources based on your account permissions. If your credentials are compromised, you should immediately revoke them in your SplashThat account settings and generate new ones. For detailed information about OAuth2 authentication, API access, and available endpoints, refer to the SplashThat API documentation.

Authenticate

Credentials required

SplashThat uses OAuth2 2-legged authentication (password grant type): the Client ID, Client Secret, Username, and Password are exchanged for a Bearer access token.

Field	Required	Secret	Description
Client ID	Yes	No	SplashThat Client ID
Client Secret	Yes	Yes	SplashThat Client Secret
Username	Yes	No	Username
Password	Yes	No	Password

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 – SplashThat

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

SplashThat uses OAuth2 2-legged authentication with password grant type for all API requests. The Client ID, Client Secret, Username, and Password are used to obtain an access token, which is then sent in the Authorization header with the Bearer prefix.

3. Enter your SplashThat Client ID in the Client ID field. This is the Client ID you obtained from your SplashThat account settings (Settings > API or Account > API Settings) when creating your OAuth application. The Client ID is used along with the Client Secret, Username, and Password to obtain an access token for API requests.

4. Enter your SplashThat Client Secret in the Client Secret field. This is the Client Secret you obtained from your SplashThat account settings when creating your OAuth application. The Client Secret is used along with the Client ID, Username, and Password to obtain an access token for API requests. The Client Secret is sensitive information and must be kept confidential.

5. Enter your SplashThat Username in the Username field. This is the username you use to sign in to your SplashThat account. The Username is used along with the Password, Client ID, and Client Secret to obtain an access token for API requests.

6. Enter your SplashThat Password in the Password field. This is the password you use to sign in to your SplashThat account. The Password is used along with the Username, Client ID, and Client Secret to obtain an access token for API requests. The Password is sensitive information and must be kept confidential.

   Your SplashThat OAuth credentials can be found in your SplashThat account settings under Settings > API or Account > API Settings. The Client ID and Client Secret are generated when you create an OAuth application. The Username and Password are your SplashThat account credentials.

   These credentials are used together to obtain an access token via the OAuth2 password grant type. The access token is then sent in the Authorization: Bearer {token} header for all API requests to the SplashThat API.

   If your credentials are compromised, you should immediately revoke them in your SplashThat account settings and generate new ones. The credentials provide access to your SplashThat account data and should be treated as sensitive information. Keep your credentials secure and do not share them publicly.

   For detailed information about OAuth2 authentication, API access, and available endpoints, see the SplashThat API documentation.

7. 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 SplashThat connector tile, then select the credential that will be used to connect to your SplashThat account, and click Next; or, create a new SplashThat 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 SplashThat endpoints. Each template is designed specifically for the corresponding SplashThat endpoint, making data source setup easy and efficient. 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.

Get All Events

This endpoint template retrieves all events from your SplashThat organization. Use this template when you need to retrieve information about events, including event details, attendee information, and other event metadata.

• This endpoint automatically retrieves all events from your SplashThat organization. The endpoint uses incrementing page-based pagination to handle large datasets efficiently, returning up to 100 records per page by default.

This endpoint returns all events from your SplashThat organization, including event details, attendee information, and other event metadata. The endpoint uses incrementing page-based pagination with page and limit parameters to handle large datasets efficiently. Nexla will automatically fetch subsequent pages of data by incrementing the page parameter.

For detailed information about events, API response structures, pagination, optional filter criteria, and available event data, see the SplashThat 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

SplashThat data sources can also be manually configured to ingest data from any valid SplashThat 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.

SplashThat API endpoints use the base URL https://api.splashthat.com (for example, https://api.splashthat.com/events) and typically use the GET method. For the Response Data Path, use $.data[*] to extract all items from the data array, or $[*] depending on the structure returned by your specific endpoint. Most endpoints support incrementing page-based pagination using page and limit parameters.

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