Humanitix

Humanitix is the world's first not-for-profit event ticketing platform, founded in 2016. The platform enables event hosts to create and manage ticketed events of any size—from community gatherings to large-scale festivals and conferences—while donating 100% of its booking fee profits to charities focused on education, healthcare, and essential services for children worldwide. Humanitix provides a comprehensive suite of event management tools including customizable event pages, flexible ticket types (paid, free, and donation-based), reserved seating, multi-session events, discount codes, automated waitlists, one-tap express checkout, and real-time attendee reporting and analytics. Its public REST API enables programmatic access to event, order, ticket, and tag data, making it easy to integrate Humanitix event data into downstream analytics, reporting, and data management workflows.

Power end-to-end data operations for your Humanitix API with Nexla. Our bi-directional Humanitix connector is purpose-built for Humanitix, 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 Humanitix or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Humanitix 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

To connect Nexla to Humanitix, you will need a Humanitix account with at least one event and an API key generated from your account settings. Humanitix uses API key authentication — all requests are authenticated by including your API key in the x-api-key request header.

Obtain a Humanitix API Key

1. Sign in to your Humanitix account at console.humanitix.com.

2. Click your account name or profile icon in the top menu bar to open the account menu.

3. Navigate to Account > Advanced > Public API Key.

4. Click Generate to create a new API key, or copy your existing API key from the field displayed on the page.

Important

Generating a new API key will immediately invalidate any previously issued API key. Any existing integrations using the old key will stop working and will need to be updated with the new key. Copy and store the key in a secure location before leaving this page.

5. Keep your API key secure and do not share it with others. Your API key provides read access to all event, order, ticket, and tag data in your Humanitix account.

Additional details about the Humanitix Public API are available in the Humanitix Public API documentation and the interactive API reference on Stoplight.

Authenticate

Create a credential in Nexla

1. After selecting the data source 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 Humanitix API key in the API Key field. This key authenticates Nexla with the Humanitix API and is included automatically as the x-api-key header in all API requests. The key must be kept confidential, as it provides access to your account's event and attendee data.

   All requests to the Humanitix API must be made over HTTPS. Nexla handles this requirement automatically when using a configured credential.

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 creation and can be selected for use with a new data source.

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

Retrieves a paginated list of all events owned by or shared with your Humanitix account. Use this endpoint to ingest event metadata — including event names, dates, venues, ticket types, and status — for reporting, analytics, or downstream processing.

• This endpoint returns all events accessible to your account. No additional parameters are required beyond selecting the template — Nexla will automatically paginate through all available results.
• The response includes an array of event objects along with pagination fields (total, page, pageSize). Nexla processes the pagination automatically to retrieve the complete event list.

The Humanitix API returns up to 100 events per page (the maximum pageSize). Nexla handles multi-page retrieval automatically when you use this template. For the complete list of fields returned per event, refer to the Humanitix API reference.

Get Orders for Event

Retrieves a paginated list of all orders for a specific event. Use this endpoint to analyze ticket sales, track order statuses, or export attendee purchase records for a given event.

• Enter the ID of the event whose orders you want to retrieve in the Event ID field. You can find event IDs by first running the Get Events endpoint to retrieve a list of your events and their corresponding IDs.

• The endpoint supports optional date range filtering. To limit results to orders created within a specific period, enter the start and end dates in the appropriate filter fields. Dates should be provided in ISO 8601 format (e.g., 2024-01-01T00:00:00Z).
• The response includes an array of order objects along with pagination fields. Nexla automatically retrieves all pages of results.

Orders contain purchase details such as buyer name, email, order total, and line items. If you need to retrieve individual ticket information rather than order-level data, use the Get Tickets for Event endpoint instead.

Get Tickets for Event

Retrieves a paginated list of all tickets issued for a specific event. Use this endpoint to track individual ticket holders, check-in status, and ticket type details for attendee management or reporting purposes.

• Enter the ID of the event whose tickets you want to retrieve in the Event ID field. Event IDs can be obtained from the Get Events endpoint.

• The endpoint supports optional filtering by date range and ticket status. Use date filters to narrow results to tickets issued within a specific period. Use the status filter to retrieve only tickets with a particular status (e.g., active, voided, or transferred).
• The response includes an array of ticket objects along with pagination fields. Nexla automatically paginates through all results.

Ticket records contain individual attendee-level details, including the ticket holder's name, email, ticket type, and check-in status. This endpoint is particularly useful for post-event analysis and attendee reconciliation.

Get Tags

Retrieves a paginated list of all tags defined in your Humanitix account. Tags in Humanitix are labels that can be applied to events for organization and categorization. Use this endpoint to ingest your tag library for use in reporting or to cross-reference tagged events.

• This endpoint retrieves all tags in your account without requiring any additional parameters. Nexla automatically paginates through all available tags.
• Each tag record includes the tag ID and name. Tag IDs can be used to filter or join with event records that reference those tags.

Tags are created and managed in the Humanitix event management console. For more information on creating tags, refer to the Humanitix Help Centre.

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

Humanitix data sources can also be manually configured to ingest data from any valid Humanitix API endpoint, including endpoints not covered by the pre-built templates or custom API configurations. 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.

The Humanitix REST API base URL is https://api.humanitix.com/v1, followed by the resource path (for example, https://api.humanitix.com/v1/events). The Humanitix Public API is read-only — all endpoints use the GET method and require the x-api-key header, which Nexla appends automatically from your credential, so no additional headers are needed. Each list response wraps its records in a top-level array named for the resource (events, orders, tickets, or tags), so set the path to data accordingly — for example, $.events[*] for the Get Events endpoint or $.tickets[*] for Get Tickets for Event. The sibling pagination fields (total, page, pageSize) can be captured as metadata if needed.

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