OneCloud - DOMO REST API
I am trying to configure a connection between the application OneCloud and DOMO. OneCloud has a built in DOMO connector but the connection is still not working.
It only asks for client ID and client secret. I have seen a ton of posts about a token but I can't figure out how to get one or if I need one.
Any help would be greatly appreciated.
Answers
-
So there's the steps outlined in the OneCloud BizApp article requiring client ID and secret from the setup to be completed on the OneCloud end. But in order to leverage the APIs in Domo (in this case, importing in data), it will require you to obtain an access token. You can learn more about the steps to do on Domo end here: https://domohelp.domo.com/hc/en-us/articles/360042934494-Managing-Access-Tokens & https://developer.domo.com/docs/authentication/quickstart-5
9 -
You'll need a client ID and client secret which you generate from https://developer.domo.com/manage-clients. You'll define the specific scopes needed when creating your client. Once you have those you can then pass those to OneCloud to finish your connection
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**0 -
so I have completed the client ID and secret but in reading the instructions and I set up an access token but I don't understand where I am supposed to copy the token.
The set up in OneCloud only shows that it needs Client ID and secret. When I set up the access token I linked it to our service user account. I named it OneCloud but there was really no information that ties them together, except the Client ID and secret.
There are no notes to explain this process.
0 -
so reading more and more, let me be clearer the screen shot below is where I don't know what to do
I thought I needed to type the request in the cmd prompt on my c drive? but I am not getting the expected return response pictured below
Also for the request I made the following updates to the command line
- removed the beginning $ sign
- XXs are Client ID and Secret (removed for post)
- scope of this connection is just data
curl -v -u XXXXXX:XXXXXX "https://XXX.domo.com/oauth/token?grant_type=client_credentials&scope=data"
The return response from the knowledge page for what I am supposed to get back is here but see below, I copied my actual return response in notepad and blurred out confidential info but I'm not getting anything that resembles the example
Where do I go from here
0 -
it appears you only need the client id and secret. Just put those into your connector and it should handle the part about generating an access token
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**0 -
this is still not working, part of config is Host Domain
do I include https://company.domo.com
or just
company.domo.com
honestly I have tried both and had a call with DOMO to review config and this is still not working
0 -
Because it's using a client ID and Secret and using the public API endpoints you'll likely need to set host domain to be
api.domo.com
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**0
Categories
- All Categories
- 1.8K Product Ideas
- 1.8K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 300 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.9K Transform
- 100 SQL DataFlows
- 616 Datasets
- 2.2K Magic ETL
- 3.9K Visualize
- 2.5K Charting
- 738 Beast Mode
- 57 App Studio
- 40 Variables
- 685 Automate
- 176 Apps
- 452 APIs & Domo Developer
- 47 Workflows
- 10 DomoAI
- 36 Predict
- 15 Jupyter Workspaces
- 21 R & Python Tiles
- 394 Distribute
- 113 Domo Everywhere
- 275 Scheduled Reports
- 6 Software Integrations
- 124 Manage
- 121 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 10 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 108 Community Announcements
- 4.8K Archive