Bloomerang

This is an unofficial bloomerang.co REST API v2 client for Ruby.

Note: you must be a Bloomerang customer with an active account to access the API

This gem is based upon the initial work of @allynfolksjr at https://github.com/mcsweeneys/bloomerang. They added limited endpoint support for:

• Constituent
• Fund
• Transaction

This gem adds support for all other endpoints, except:

• Processor
• User
• WalletItem

Add this line to your application's Gemfile:

gem "bloomerang_api", "~> 1.0"

And then execute:

$ bundle install

1. Get your Bloomerang API Key:

• Generate your v2.0 API key from your Bloomerang user settings

2. Add your API key to your app using a secure method:

• Credentials strategy (preferred):

  # ./config/credentials.yml
  bloomerang:
    api_key: myapikey

• dotenv strategy:

  # ./.env
  BLOOMERANG_API_KEY=myapikey

• ENV strategy:

  $ export BLOOMERANG_API_KEY=myapikey

3. Run the generator to create the initializer file:

$ rails generate bloomerang:initializer

This will create the file ./config/initializers/bloomerang.rb where you can set your API key:

require 'bloomerang'

Bloomerang.configure do |config|
  ### Set your Bloomerang API key:
  # Generate your v2.0 API key from your Bloomerang user settings:
  # https://crm.bloomerang.co/Settings/User/Edit
  #
  # UNSECURE: DO NOT ADD THE KEY DIRECTLY TO THIS FILE!
  # It will be exposed in your source code.
  # Instead, use a secure method to store your API key
  #
  # Rails credentials example (preferred):
  # Learn about encrypted credentials: https://edgeguides.rubyonrails.org/security.html#custom-credentials
  # config.api_key = Rails.application.credentials.dig(:bloomerang, :api_key)
  #
  # ENV or dotenv example:
  # Learn about dotenv gem: https://github.com/bkeepers/dotenv
  # config.api_key = ENV["BLOOMERANG_API_KEY"]
end

👇👇👇👇👇👇👇👇👇👇👇👇👇👇👇👇👇👇👇👇👇👇👇👇👇👇👇👇👇👇👇👇

Bloomerang does not offer a sandbox environment or any way to test API calls without actually affecting your production data.

Please encourage Bloomerang to address this issue.

Any POST, PUT and DELETE requests will be run against your live Bloomerang account!

👆👆👆👆👆👆👆👆👆👆👆👆👆👆👆👆👆👆👆👆👆👆👆👆👆👆👆👆👆👆👆👆

• Reading records:

  • #fetch: a GET request that returns a batch of records, 50 by default (see paging/batching below for more)
  • #show: a GET request returns a single record that matches the provided ID

• Creating, updating and deleting records:

  • #create: a POST request that creates a record based on the provided body variable.
  • #update: a PUT request that updates a record
  • #delete: a DELETE request that deletes a record

  It is highly recommended to reference the documentation to identify required and allowed attributes.

Some Classes have custom endpoints. For example:

• Bloomerang::Campaign.refresh_summaries
• Bloomerang::Constituent.fetch_relationships
• Bloomerang::Constituent.update_communication_settings
• Bloomerang::Constituent.search
• Bloomerang::CustomField.categories

Check the specific class for available methods.

Most GET requests have URL parameters that can be set.

Each Class lists the available parameters you can append to GET requests, you can also check each endpoints' documentation.

#search methods, #fetch methods, and methods that start with #fetch_ have two parameters in common that allow you to fetch results in batches:

• skip - defaults to 0, the number of records to "skip" before returning results
• take - defaults to 50, the number of records to return.

Responses will include the total number of results available. For example:

params = { skip: 0, take: 50 }
first_fifty_constituents = Bloomerang::Constituent.fetch(params)

The result will include these keys:

{
  "Total": 1850, // All records in the database
  "TotalFiltered": 1850, // All records that match query/filters
  "Start": 0,
  "ResultCount": 50,
  "Results": []

"Start" should be equal to skip and "ResultCount should be equal to take.

Increase your skip value by your take value to get the next page/batch of records:

params = { skip: 50, take: 50 }
next_fifty_constituents = Bloomerang::Constituent.fetch(params)

{
  "Total": 1850, // All records in the database
  "TotalFiltered": 1850, // All records that match query/filters
  "Start": 50,
  "ResultCount": 50,
  "Results": []

WARNING: Bloomerang has no test/sandbox feature! Any POST, PUT and DELETE requests will be run against your live Bloomerang account! Proceed with caution!

#update, and #delete methods require a record ID and a body object. Not all Classes implement a #delete endpoint.

#create methods require only a body object.

It is highly recommended to reference the documentation to identify required and allowed attributes.

# fetch the first 50 individual constituents
params = { skip: 0, take: 50, type: "Individual" }
Bloomerang::Constituent.fetch(params)

# fetch the next 50 individual constituents
params = { skip: 50, take: 50, type: "Individual" }
Bloomerang::Constituent.fetch(params)

# get the email addresses (first 50) for a constituent
params = { constituent: "12345" }
Bloomerang::Email.fetch(params)

# create a task
body = {
  "DueDate": "2023-01-21",
  "Subject": "Schedule meeting",
  "Note": "Schedule a meeting with Tom and Sidney to request a renewed family foundation gift",
  "Channel": "Email",
  "Purpose": "ImpactCultivation",
  "UserId": 12, # the ID of the user responsible for the task
  "AccountId": 123456, # the ID of the constituent related to the task
}
Bloomerang::Task.create(body)

Bug reports and pull requests are welcome. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the code of conduct.

The gem is available as open source under the terms of the MIT License.

Everyone interacting in the Bloomerang API project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.