Build Status Gem Version


Official Ruby client for the Bootic API


Add this line to your application's Gemfile:

gem 'bootic_client'

And then execute:

$ bundle

Or install it yourself as:

$ gem install bootic_client


Configure with you app's credentials

You first must create an OAuth2 Application in your Bootic dashboard. Then configure the client with your client_id and client_secret.

BooticClient.configure do |c|
  # these are required for OAuth2 strategies
  c.client_id = ENV['BOOTIC_CLIENT_ID']
  c.client_secret = ENV['BOOTIC_CLIENT_SECRET']
  # these are optional
  c.logger =
  c.logging = true
  c.cache_store = Rails.cache
  c.user_agent = "My App v1"

Using with an existing access token

bootic = BooticClient.client(:authorized, access_token: 'beidjbewjdiedue...')

root = bootic.root

if root.has?(:all_products)
  # All products
  all_products = root.all_products(q: 'xmas presents')
  all_products.total_items # => 23443
  all_products.each do |product|
    puts product.title
    puts product.price

  # Iterate through pages of products
  # See "iterating" section below for a more elegant option
  if all_products.has?(:next)
    next_page =


Entities representing lists of things (products, orders, etc) are fully enumerable.

# These will only iterate this page's worth of products
all_products.each{|pr| puts pr.title}
all_products.reduce(0){|sum, pr| sum + pr.price}

These lists might be part of a paginated data set. If you want to iterate items across pages and make sure you consume the full set, use #full_set.

# These will iterate all necessary pages
all_products.full_set.each{|pr| puts pr.title }

You can check whether an entity is iterable with:



The Bootic Client supports different authentication strategies depending on the use case.

1. Refresh token flow (web apps)

In this flow you first get a token by authorizing an app. ie. using omniauth-bootic

def client
  @client ||= BooticClient.client(:authorized, access_token: session[:access_token]) do |new_token|
    session[:access_token] = new_token

Note how the client takes an optional block. This block will be called with a new access token whenever the old one expires. It's up to your code to store this token somewhere.

2. User-less flow (client credentials - automated scripts)

This flow will first use your client credentials to obtain an access_token if started without one.

client = BooticClient.client(:client_credentials, scope: 'admin', access_token: some_store[:access_token]) do |new_token|
  some_store[:access_token] = new_token

3. Basic Auth

This strategy uses a username and password against APIs supporting HTTP's Basic Authentication scheme.

The official Bootic API only supports OAuth2 tokens, but this allows the client to be used against internal APIs or stub APIs on development.

client = BooticClient.client(:basic_auth, username: 'foo', password: 'bar')

root = client.root # etc

NOTE: username and password have nothing to do with your Bootic administrative credentials, and will be up to API maintainers to define.

4. Bearer token

This strategy adds an access token as a header in the format Authorization: Bearer <your-token-here>. It will not try to refresh an expired token from an Oauth2 server, so there's no need to configure Oauth2 credentials.

client = BooticClient.client(:bearer, access_token: 'foobar')

root = client.root # etc

Use this with APIs that don't expire tokens, or for testing.

Most resource links lead to GET resources, but some will expect POST, PUT, DELETE or others.

The Bootic API encodes this information in its link metadata so the client will do the right thing. The following example creates a new product on your first shop:

bootic = BooticClient.client(:client_credentials)

root = bootic.root

shop = root.shops.first

if shop.can?(:create_product)
  product = shop.create_product(
    title: 'A shiny new product',
    price: 122332,
    status: "visible",
    variants: [
        title: 'First variant',
        sku: 'F23332-X',
        available_if_no_stock: 1,
        stock: 12
    collections: [
      {title: "A new collection"},
      {id: 1234}

  puts product.rels[:web].href # => ''

Working with Files and IO instances

Instances of File, other readable IO objects (and in fact anything that responds to #read) will be base64-encoded internally before JSON-encoding payloads for POST, PUT and PATCH requests.

asset = product.create_product_asset(
  filename: 'foo.jpg',
  data:'/path/to/foo.jpg') # this will base64-encode the file data in the `data` field.

Because anything that responds to #read will be interpreted as file data and base64-encoded, you can also pass instances of open-uri.

require "open-uri"

asset = product.create_product_asset(
  filename: 'foo.jpg',
  data: open("") # this will base64-encode the file data in the `data` field.

.. or even your own readers

class MyReader
  def read
    "some data here"

asset = product.create_product_asset(
  filename: 'foo.jpg',
  data: # this will base64-encode the file data in the `data` field.

Non-JSON responses

HTTP responses are resolved by handler callables in BooticClient::Configuration#response_handlers.

The default stack is:

  • BooticClient::ResponseHandlers::Hal: handles application/json responses and wraps JSON data in BooticClient::Entity instances.
  • BooticClient::ResponseHandlers::File: handles image/* responses and wraps image data in IO-like objects.
# Fetching product images and saving them to local files:
product.images.each do |img|
  io = img.original # HTTP request to image file
  # now write image data to local file., 'wb') do |f|

You can register custom response handlers. The example below parses CSV response data.

require 'csv'

# Response handlers are callable (anything that responds to #call(faraday_response, client)
# if a handler returns `nil`, the next handler in the stack will be called.
CSVHandler = do |resp, _client|
  if resp.headers['Content-Type'] =~ /text\/csv/
    CSV.parse(resp.body, headings: true)

BooticClient.configure do |c|

# Now CSV resources will be returned as parsed CSV data
client = BooticClient.client(:authorized, access_token: 'abc')
root = client.root
csv = root.some_csv_resource # returns parsed CSV object.

Relation docs

All resource link relations include a "docs" URL so you can learn more about that particular resource.

shop = root.shops.first
puts shop.rels[:create_product].docs # => ''

Cache storage

BooticClient honours HTTP caching headers included in API responses (such as ETag and Last-Modified).

By default a simple memory store is used. It is recommended that you use a distributed store in production, such as Memcache. In Rails applications you can use the Rails.cache interface.

BooticClient.configure do |c|
  c.cache_store = Rails.cache

Outside of Rails, BooticClient ships with a wrapper around the Dalli memcache client. You must include Dalli in your Gemfile and require the wrapper explicitely.

require 'bootic_client/stores/memcache'

BooticClient.configure do |c|
  c.cache_store = CACHE_STORE

Pre-loaded or custom root resources

This client is designed to always navigate APIs starting from the root endpoint (the Hypermedia approach), but it's also possible to skip the root and start from a locally defined resource definition.

messaging_api = client.from_hash(
  "_links" => {
    "send_message" => {"href" => '', "method" => 'post'},
    "delete_message" => {"href" => '', "method" => 'delete', "templated" => true}

new_message = messaging_api.send_message(title: 'This is a new message')


It's also possibe to load a root resource directly from a URL:

messaging_api_root = client.from_url("")
messaging_api.do_something(foo: "bar") # etc


  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request


Bump version.rb and

bundle exec rake release

Update, commit and push changelog:

github_changelog_generator -u bootic -p bootic_client.rb