How to Connect to with OAuth 2.0

Document created by brian_otoole Employee on Oct 13, 2016Last modified by Adam Arrowsmith on Jun 13, 2017
Version 6Show Document
  • View in full screen mode

This article describes how to connect to using HTTP Client Connector with OAuth 2.0 authentication.



Use Case

Provide the ability to connect AtomSphere with the REST API using the OAuth 2.0 protocol for authentication.



The approach will use the AtomSphere HTTP Client Connector to interact with the REST API and retrieve a list of user accounts. While doing so we will configure the necessary OAuth 2.0 settings in accordance with’s implementation of OAuth 2.0.


The approach consists of the following steps:

  1. Use the AtomSphere HTTP Connector to initiate and execute REST based requests against
  2. Configure a sample application and authorize the respective Boomi AtomSphere process.
  3. Configure the required authentication settings within the HTTP Client Connector in accordance with OAuth 2.0 parameters.
  4. Perform a simple request to retrieve user accounts



The following steps detail how to deploy a process using the AtomSphere HTTP Client Connector when connecting to’s REST API:


  1. Create Application
  2. Record the OAuth 2.0 Parameters for reference later
  3. Design a Boomi AtomSphere Process using the HTTP Client Connector
  4. Configure HTTP Client Connector with the respective OAuth 2.0 parameters recorded previously
  5. Specify the proper resource path for the REST API Endpoint to retrieve users.


1. Create Application

Navigate to and follow the instructions to create a new Box Application:



2. Specify OAuth 2.0 Parameters



Note the following parameters to use later when configuring the HTTP Client Connector: OAuth 2.0 ParameterValue
client_idml0yrwnjsv7ywyvjct4op3eq1afgksos - [sample ID]
client_secretv5u0Ha0ig05OrFfPQjC1afO1dztp0bOp - [sample secret]


3. Start to Build a Sample AtomSphere Process

Design a simple integration process to validate your connection. Bypass the HTTP Client Connection and Operation until the next step:



4. Configure your HTTP Client Connection and Operation


1. Configure the HTTP Client Connection with the following parameters:


Authentication TypeOAuth 2.0
Grant TypeAuthorization Code
Client IDml0yrwnjsv7ywyvjct4op3eq1afgksos - [sample ID]
Client Secretv5u0Ha0ig05OrFfPQjC1afO1dztp0bOp - [sample secret]
Authorization Token URL 

Scope<Intentionally left blank for this example>

Authorization Parameters

(Name | Value)

Authentication Parameters

(Name | Value)

None (leave blank)
Access Token URL


2. After defining the parameters, click the “Regenerate” button to regenerate the Access Token. This token will be saved and used for future requests against



5. Configure the HTTP Client Connector Operation

Since we are performing a simple GET request there is no need for a request profile, however there is a JSON response profile specified. A sample of the JSON response is provided below in addition to this screenshot of the operation:



6. Validation

With a simple test run of the process, the HTTP Client should be able to make a successful connection to and retrieve a complete JSON response provide detailed below.




Sample JSON Response:

  "total_count": 1,
  "entries": [
      "type": "user",
      "id": "341312345",
      "name": "Test Account1",
      "login": "",
      "created_at": "2016-09-12T09:52:19-07:00",
      "modified_at": "2016-09-12T09:52:19-07:00",
      "language": "en",
      "timezone": "America/Los_Angeles",
      "space_amount": 10737418240,
      "space_used": 0,
      "max_upload_size": 2147483648,
      "status": "active",
      "job_title": "",
      "phone": "",
      "address": "",
      "avatar_url": ""
  "limit": 100,
  "offset": 0
3 people found this helpful