Hotmart

Hotmart is a comprehensive digital product marketplace and platform that enables creators to sell digital products, courses, and subscriptions online, providing payment processing, affiliate marketing tools, and analytics to help entrepreneurs build and scale their digital businesses.

Power end-to-end data operations for your Hotmart API with Nexla. Our bi-directional Hotmart connector is purpose-built for Hotmart, 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 Hotmart or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Hotmart 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 Hotmart credential, you need to obtain OAuth2 credentials (Client ID and Client Secret) from your Hotmart Developers account. The OAuth2 credentials are required for 2-legged OAuth2 authentication with the Hotmart API.

To obtain your OAuth2 credentials, follow these steps:

1. Sign in to your Hotmart account and navigate to Tools > Developer Credentials in your account dashboard.

2. Click Create Credential to create a new application credential. Provide a descriptive name for your credential to help identify it later.

3. Select the appropriate environment for your credential:

   • Sandbox: Use this environment for testing and development purposes. Sandbox credentials allow you to test API integrations without affecting production data.
   • Production: Leave this unchecked if you want to use the credential in production. Production credentials have access to real account data and transactions.

4. After creating the credential, you will receive:

   • Client ID: A unique identifier for your application
   • Client Secret: A secret key that must be kept confidential
   • Basic Token: An alternative authentication method (not used for OAuth2)

The Client ID and Client Secret are used for 2-legged OAuth2 authentication, which uses the client credentials flow to obtain an access token. This authentication method is suitable for server-to-server communication where user interaction is not required. The access token is then sent in the Authorization header with the Bearer prefix for all API requests to the Hotmart API. The Hotmart API provides access to various resources including subscriptions, sales, products, members areas, and affiliate data. For detailed information about OAuth2 credential setup, authentication flows, and available API endpoints, refer to the Hotmart API authentication documentation and Hotmart API overview.

Authenticate

Credentials required

Field	Required	Secret	Description
Client ID	Yes	No	Hotmart Client ID
Client Secret	Yes	Yes	Hotmart Client Secret

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

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

Hotmart uses 2-legged OAuth2 authentication with the client credentials flow. This authentication method is designed for server-to-server communication where user interaction is not required. The Client ID and Client Secret are used to obtain an access token, which is then used to authenticate API requests to the Hotmart API.

3. Enter your Hotmart Client ID in the Client ID field. This is the Client ID you obtained from your Hotmart Developers application settings (Tools > Developer Credentials). The Client ID is a unique identifier for your application and is used along with the Client Secret to obtain an access token for API authentication. The Client ID is not sensitive and can be shared, but it should be kept secure to prevent unauthorized use.

4. Enter your Hotmart Client Secret in the Client Secret field. This is the Client Secret you obtained from your Hotmart Developers application settings. The Client Secret is used along with the Client ID to obtain an access token for API authentication. The Client Secret is sensitive information and must be kept confidential.

   Keep your Client Secret secure and do not share it publicly. The Client Secret provides access to your Hotmart account data and should be treated as sensitive information. If your Client Secret is compromised, you should immediately regenerate it in your Hotmart Developers application settings. Your Hotmart Client Secret can be found in your Hotmart Developers application settings (Tools > Developer Credentials) where you manage your application credentials. The Client Secret is used along with the Client ID to obtain an access token using the 2-legged OAuth2 client credentials flow. Nexla automatically obtains and refreshes the access token as needed. The access token is valid for a limited time and is automatically refreshed when it expires. For detailed information about finding your Client Secret, setting up OAuth2 credentials, and managing access tokens, see the Hotmart API authentication documentation.

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

Get Subscriptions

This endpoint displays the detailed information of the creator's subscriptions/subscribers. Used for listing subscriptions and detailed information for them.

• This endpoint automatically retrieves all subscriptions and subscribers from your Hotmart account. No additional configuration is required beyond selecting this endpoint template.
• The endpoint uses GET requests to https://developers.hotmart.com/payments/api/v1/subscriptions. The endpoint URL is automatically constructed based on the Hotmart API base URL.
• The endpoint uses token-based pagination (iteration.type: paging.next.token) through the page_token parameter. The response data path is $.items[*], which extracts all items from the items array in the API response.
• When a response includes a page_info.next_page_token value, Nexla automatically uses it as the page_token parameter for the subsequent request to fetch the next page of results until all subscriptions have been retrieved.

This endpoint retrieves detailed information about subscriptions and subscribers from your Hotmart account. The endpoint provides comprehensive subscription data including subscriber information, subscription status, billing details, and more. The endpoint supports pagination through the page_token mechanism, which allows you to retrieve large lists of subscriptions efficiently. The response includes pagination metadata that indicates the current page and next page token available. For detailed information about the API response format and available fields, see the Hotmart Subscriptions 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

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

Hotmart API endpoints typically follow the pattern https://developers.hotmart.com/{endpoint_path} or https://api-sec-vlc.hotmart.com/{endpoint_path}, and the API typically returns data in JSON format.

Ensure the API endpoint URL is correct and accessible with your current credentials. You can test the endpoint using the Test button after configuring the URL. The endpoint requires 2-legged OAuth2 authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration. The access token is obtained using the OAuth2 client credentials flow with your Client ID and Client Secret. For detailed information about Hotmart API endpoints and available APIs, see the Hotmart API documentation.

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