Categories
- All Categories
- 75 Oracle Analytics News
- 7 Oracle Analytics Videos
- 14K Oracle Analytics Forums
- 5.2K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 40 Oracle Analytics Trainings
- 59 Oracle Analytics Data Visualizations
- 2 Oracle Analytics Data Visualizations Challenge
- 3 Oracle Analytics Career
- 4 Oracle Analytics Industry
- Find Partners
- For Partners
oracle rest api connector - Please help me to add "body"(data) to endpoint request.
Hi I am struggling to find documentation on how to add body to json file for oracle analytics cloud dv rest api connector. I was able to successfully retrieve data for basic api which requires no body to the request. I would like to someone help to understand where to add the body.
Postman version:
OAC DV connection:
DV connection JSON file for above connection which is working with no body requires for this request.
Best Answer
-
If your API always requires a body, then you should consider posting an idea requesting the feature (or upvote an existing one if already there).
The REST API source is quite “new”, added only recently (1 year maybe as preview first?). Therefore it is a simple one for now.
As workaround, in the meantime, can’t you use a database as intermediate layer? Many databases are able to execute advanced API calls, and save the results into tables. You then use the tables as sources.
0
Answers
-
Hi,
As far as I know, it is not possible.
The REST API connection doesn't expect any "body" content, just the URL of the REST APIs that you can retrieve, passing parameters in the URL itself at best.
Your endpoint isn't really a "static" API, it's a fully dynamic one where you can dynamically query various things passing the attributes you expect as result and the filters you want to use.
If you look at the various examples provided at
, they simply call "static" endpoints with parameters in the URL itself and that's it.The idea is to retrieve everything from the API, and then use the filters available in the various places in the product to query the pieces you want for your needs from the dataset (and not the API). The dataset acting as "cache" for your API, so that you don't query it all the time if you retrieve a full datasets and only need a subset of it to build your workbooks.
You could look if an idea already exist to extend the REST API connection to support a body content. If it does exist, you can upvote it. If it doesn't exist, you can create it in
.0 -
Thank you very much, I very much like to make basic API call, then use filters on dataset, but all of our application end points is designed to accept only with body.
0 -
i have never explored that option i will try now
0 -
Hi @Anudeep Desu,
FYI in case useful. Documentation for this feature is available here:
2