- User Authentication
- Discovery (used in Configure Selectable Reports / Advanced Mode)
- Process Data Examples
User Authentication
No Authentication
No code is required. But if you would like, you can make an API call to check the connection.Username and Password
Determine how your API endpoint needs to authenticate with the username and password. Most endpoints that use username and password will use the Basic Authentication standard. The username and password are stored in themetadata.account object.
Access the stored username and password
API Key
An API key is a token passed in as a header or a query parameter in an HTTP request. It uniquely identifies who is making the call and is often non-expiring. You will need to determine how the REST API you wish to call needs to send the API key. The API key is stored in themetadata.account object.
If your API endpoint requires it, the Connector Dev Studio includes functions for building a JSON Web Token (JWT).
Access the stored API key
OAuth 2.0
OAuth 2.0 is the industry-standard for secure authentication. If your cloud API endpoint uses OAuth 2.0, you are in luck: Domo has automated the processes of using your stored data to retrieve your access token. After you have filled in the appropriate fields and clicked Get Access Token, your access token and code are stored in themetadata.account object.
Access the stored access token and code
Dropdown
This example makes a call to the Facebook API to get all the pages controlled by this user. It inserts them as options into a discovery dropdown. This will allow a user to select just one Facebook page to run a report on. Dropdown methodsBasic Tree Menu
This example makes a call to the Facebook API to get all the pages controlled by this user. This will allow the user to select multiple Facebook pages to run a report on. To create a series of checkboxes, add each item as a leaf to the root node,discovery.tree. The results selected by the users are stored in a JavaScript array.
Access tree menu root node
Nested Tree Menu
You can nest checkboxes into categories by adding nodes to thediscovery.tree root. If a user checks a parent checkbox, all the checkboxes nested in it will be selected. This example nests countries in parent nodes that represent regions. The results selected by the users are stored in a JavaScript array.
Access tree menu root node
Process Data Examples
The Connector Dev Studio has a couple of example connectors provided to you: Sample CRM and USGS. The following examples of data processing blocks are pulled from these sample connectors.

Sample CRM
- Authentication type: Username and password
- Reports: Opportunities
- Parameters: None
- Endpoint data return format: CSV
Sample CRM using datagrid.magicParseCSV
- Authentication type: Username and password
- Reports: Opportunities
- Parameters: None
- Endpoint data return format: CSV
USGS
- Authentication type: None
- Reports: Past Hour, Past Day, Past 7 Days, Past 30 Days, Pull data from the last X day(s)
- Parameters: None
- Endpoint data return format: JSON