Bloomerang

Bloomerang is a comprehensive donor management platform designed specifically for nonprofits, helping organizations build stronger relationships with donors, track fundraising activities, and create lasting impact through better donor engagement and retention strategies.

Power end-to-end data operations for your Bloomerang API with Nexla. Our bi-directional Bloomerang connector is purpose-built for Bloomerang, 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 Bloomerang or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Bloomerang 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 Bloomerang credential, you need to obtain an API key from your Bloomerang account. The API key is required to authenticate with the Bloomerang REST API v2.

To obtain your API key, you need to have a Bloomerang account with API access enabled. Once you have access to your account, you can generate an API key from your account settings. The API key is used to authenticate all API requests to the Bloomerang REST API v2 using the X-API-KEY header. For detailed information about API key setup and authentication, refer to the Bloomerang REST API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
API Key Value	Yes	Yes	The API key for your Bloomerang account, sent in the X-API-KEY header to authenticate all requests to the Bloomerang REST API v2.

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

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 Bloomerang API key in the API Key Value field. This is the API key you obtained from your Bloomerang account settings. The API key is sent in the X-API-KEY header to authenticate all API requests to the Bloomerang REST API v2.

   Keep your API key secure and do not share it publicly. The API key provides access to your Bloomerang account and should be treated as a sensitive 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/destination creation and can be selected for use with a new data source or destination.

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

Campaigns

This endpoint retrieves a list of campaigns from your Bloomerang account. Use this endpoint when you need to access campaign information for fundraising activities, donor engagement, or campaign analysis.

• This endpoint automatically retrieves all campaigns from your Bloomerang account. No additional configuration is required beyond selecting this endpoint template.
• The endpoint uses GET requests to https://api.bloomerang.co/v2/campaigns. The endpoint URL is automatically constructed based on the Bloomerang API base URL.
• The endpoint uses offset-based pagination, automatically fetching additional pages as needed using the skip and take query parameters. The endpoint starts from offset 0 and continues fetching pages until all available campaigns have been retrieved. By default, the endpoint retrieves up to 100 items per page.
• The endpoint will return all campaigns in your account. The response data is extracted from the Results array in the API response ($.Results[*]), with each campaign record processed individually.

This endpoint supports pagination through skip and take query parameters. Nexla automatically handles pagination to retrieve all available records by incrementing the offset until no more data is returned. The endpoint uses offset-based pagination (iteration.type: paging.incrementing.offset), starting from offset 0. By default, the endpoint retrieves up to 100 items per page (page.expected.rows: 100). The response data path is $.Results[*], which extracts all items from the Results array in the API response. For detailed information about retrieving campaigns, see the Bloomerang REST API documentation.

Constituents

This endpoint retrieves a list of constituents (donors, volunteers, and other supporters) from your Bloomerang account. Use this endpoint when you need to access constituent information for donor management, engagement tracking, or relationship analysis.

• This endpoint automatically retrieves all constituents from your Bloomerang account. No additional configuration is required beyond selecting this endpoint template.
• The endpoint uses GET requests to https://api.bloomerang.co/v2/constituents. The endpoint URL is automatically constructed based on the Bloomerang API base URL.
• The endpoint uses offset-based pagination, automatically fetching additional pages as needed using the skip and take query parameters. The endpoint starts from offset 0 and continues fetching pages until all available constituents have been retrieved. By default, the endpoint retrieves up to 100 items per page.
• The endpoint will return all constituents in your account. The response data is extracted from the Results array in the API response ($.Results[*]), with each constituent record processed individually.

This endpoint supports pagination through skip and take query parameters. Nexla automatically handles pagination to retrieve all available records by incrementing the offset until no more data is returned. The endpoint uses offset-based pagination (iteration.type: paging.incrementing.offset), starting from offset 0. By default, the endpoint retrieves up to 100 items per page (page.expected.rows: 100). The response data path is $.Results[*], which extracts all items from the Results array in the API response. For detailed information about retrieving constituents, see the Bloomerang REST 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

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

Bloomerang API endpoints follow the pattern https://api.bloomerang.co/v2/{endpoint_path} and require API key authentication in the X-API-KEY header, which is handled automatically by your credential configuration. Bloomerang API responses typically use a Results array to contain the actual data, so set the path to data to $.Results[*] to extract all items from the response.

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 Bloomerang 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 Bloomerang destination, and select the Send to Destination option from the menu. Select the Bloomerang connector from the list of available destination connectors, then select the credential that will be used to connect to the Bloomerang organization, and click Next; or, create a new Bloomerang 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 Bloomerang 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.

Create Campaign

This endpoint creates a new campaign in your Bloomerang account. Use this endpoint when you need to create fundraising campaigns, donor engagement campaigns, or other campaign types from your data sources.

• The endpoint uses POST requests to https://api.bloomerang.co/v2/campaign. The endpoint URL is automatically constructed based on the Bloomerang API base URL.
• The endpoint sends data from your Nexset as the request body in JSON format. Each record in your Nexset will be sent as a JSON object containing the campaign data to create. The request body should follow the Bloomerang REST API v2 specification for creating campaigns, including required fields and field names.
• Batch mode is disabled by default for this endpoint. Each record in your Nexset will be sent as a separate API request to create a campaign. If you need to create multiple campaigns, you can send multiple records, but each will be processed as a separate request.

The request body must be properly formatted JSON that matches the Bloomerang REST API v2 specification for creating campaigns. The endpoint requires API key authentication in the X-API-KEY header, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. Batch mode is disabled by default (batch.mode: false), so each record will be sent as a separate request. For detailed information about creating campaigns, including required fields, field names, and request formats, see the Bloomerang REST API documentation.

Create Constituent

This endpoint creates a new constituent (donor, volunteer, or supporter) in your Bloomerang account. Use this endpoint when you need to add new constituents from your data sources, such as importing donor information or creating supporter records.

• The endpoint uses POST requests to https://api.bloomerang.co/v2/constituent. The endpoint URL is automatically constructed based on the Bloomerang API base URL.
• The endpoint sends data from your Nexset as the request body in JSON format. Each record in your Nexset will be sent as a JSON object containing the constituent data to create. The request body should follow the Bloomerang REST API v2 specification for creating constituents, including required fields and field names.
• Batch mode is disabled by default for this endpoint. Each record in your Nexset will be sent as a separate API request to create a constituent. If you need to create multiple constituents, you can send multiple records, but each will be processed as a separate request.

The request body must be properly formatted JSON that matches the Bloomerang REST API v2 specification for creating constituents. The endpoint requires API key authentication in the X-API-KEY header, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. Batch mode is disabled by default (batch.mode: false), so each record will be sent as a separate request. For detailed information about creating constituents, including required fields, field names, and request formats, see the Bloomerang REST API documentation.

Manual configuration

Bloomerang destinations can also be manually configured to send data to any valid Bloomerang REST API v2 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, and request body. Using manual configuration, you can also configure Nexla to automatically send the response received from the Bloomerang API after each call to a new Nexla webhook data source.

Bloomerang API endpoints follow the pattern https://api.bloomerang.co/v2/{endpoint_path} and primarily use POST requests with JSON request bodies for write operations. API key authentication in the X-API-KEY header and the Content-Type: application/json header are handled automatically by your credential configuration, so you do not need to add them to the Request Headers field.

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 Bloomerang endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Bloomerang endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.