I am trying to hit SAP HANA's rest APIs but unable to get started because i didn't get any proper document that specifies the steps that i can use to hit APIs through POSTMAN(or any other rest client). Do i need to install anything before using the resp APIs or are they available to be used directly? Also what all are the parameters that i need to mention while hitting the API and what is the base URL that is to be used?
Ok, the HANA XS API is documented: SAP HANA XS JavaScript API Reference
For the error: most likely, you're not using any authentication in Postman. When you e.g. switch to "Basic Auth" and key in your HANA username and password, something like this
https://<hostname>:43<instance no>/sap/hana/xs/dt/base/info
should work.
Below is sample Request in to Hit REST API Using Postman :
1. http://localhost:8080/my-rest-api/progress-report?name=shekhar®ion=east&address=India
Add Headers Info if any : like
accept : application/json;v=1
contentType : application/json;v=1
Related
I'm trying to sign in to HP ALM via its Rest API using Postman.
Following the reference for 12.50 version (https://almsyngenta.saas.hpe.com/qcbin/Help/doc_library/api_refs/REST/webframe.htm#sign_in.htm), I'm sending a POST request to:
https://almalm1250saastrial.saas.hpe.com/qcbin/api/authentication/sign-in
Using the header:
Authorization: Basic <Base64-encoded username:password>
And the response i'm getting is:
HTTP Error 403 - Problem accessing /qcbin/api/authentication/sign-in. Reason: Forbidden
Does anyone know what's wrong with my request? I'm just following the reference I linked above.
NOTE: The account used for the sign in process is a trial account and I can sign in with any problems from a browser.
Thanks, This looks to be an issue with the backend. I tried to hit the URL from your image and I got the same error ( 403 )
whereas on the other hand, if the URL was to accept API requests and if the user details are incorrect the below would be the response
Below is my analysis on REST API call to ALM . Go through here
You can request for ALM database API and use the same API to report UiPath results. It will go directly into ALM server. But you need to work with ALM server admins in your organization for this.
You need ALM server side customization is required.Please find out ALM APIs which will accept data from other sources. use those APIs in UiPath and you can integrate both.
HP ALM Supports Rest API’s So you can also give it a try with HTTP REquest Activity.
From https://{host}/qcbin/authentication-point/authenticate
In Postman enter the URL
Add below Headers(for instance, using JSON): "Key":"Content-Type", "Value":"application/json"
Select the desired method i.e. POST
Click on Body, choose raw and provide following data in body of request
{
"username": "value",
"password": "value"
}
Click Send button to hit the API.
Make sure status returns 200/OK response
If there is a functionality for token, the response body must contains Token
Hope my answers will helps you.
See also the following references:
AMD help
Youtube
Bolte 1
Bolte 2
Quora
Host
Test Guild
Imgur
Guru99
I am trying to call REST API related to Azure Search through postman.
Here is the API link: (Check Step 1: Create a data source)
https://learn.microsoft.com/en-us/azure/search/search-howto-indexing-azure-blob-storage
Have sent parameter api-key: [admin key] in form-data and other through jSON object.
I am getting 403 error.
Whats the correct way to get required output?
Update :
Changed position of api-key. Still getting the error as :
Is there any additional setting for postman to work with Azure's REST APIs?
Please make sure that you pass api-key in Headers instead of form-data and also all the headers should be selected. Once you do that, things should work just fine.
In API connect, I was working with one of the 'path' in API which requires file upload using multipart/form-data (POST request). I was not able to find out any support for it though.
While adding parameter there is no support for 'file' type (located-in: form-data). Is there something which I am missing in my setup? Is there any other way to attach file in request via API connect ?
I am using API Connect "Essentials" plan.
Thanks
I think that you can just leave the type blank:
I'm trying to use the QBO v3 API object update function described here. The API explorer shows a different uri.
I'm trying to update an account with Id 42. Both of the following URIs get me a 401:
As the documentation would suggest:
https://quickbooks.api.intuit.com/v3/company/0123456789/account?requestid=42
(the above at least gives me a json blob with the 401)
As the api explorer would suggest:
https://qb.sbfinance.intuit.com/v3/company/0123456789/account?operation=update
(here I don't even get the json, just a plain 401)
My request body is successful when I use the api explorer, so I don't believe that's the problem. I also don't believe authentication is the problem, because I can successfully create objects and also make queries with the same headers.
What might I be missing?
Don't put the Account object's ID into the URL. The [?requestid=] from the documentation you mentioned apparently refers to an id related to the request (not the object in question). The API Explorer's URI appears to simply mislead (although I could certainly be missing something here).
In your example, just use this:
https://quickbooks.api.intuit.com/v3/company/0123456789/account
Let the headers and request body do the rest.
Correct BASE URI: https://quickbooks.api.intuit.com/v3/company/
you can refer example request/response section of any entity doc.
Ref -https://developer.intuit.com/docs/0025_quickbooksapi/0050_data_services/030_entity_services_reference/bill
To debug(401 authentication issue), you can use any standard RestClient.
In the following thread, I've explained how to use RestClinet plugin of Mozilla to test any QBO V3 endpoint.
InvalidTokenException: Unauthorized-401
You can download IPP's devkit and using that devkit you can call any endpoints easily.
https://developer.intuit.com/docs/0025_quickbooksapi/0055_devkits
Hope it will be useful.
Thanks
I am using wso2 API manager 1.6.0 and would like to create an API which accepts any POST
on /users resource followed by any query parameter such as "clientid" (as described below)
restserver.com:8280/context/1/users?clientid=333
I have created an API in API publisher as follow :
URL Prefix URL Pattern HTTP Verb
/context/1 /users/* POST
Any POST on /users is accepted but as sson as I add a query paramter /users?clientid=333 , the request is rejected by the API Manager gateway with 403 error.
Could someone advice me on this and what should be the correct url-mapping format ?
The resulting url-mapping in synapse config file is as follow : (synapse-configs/default/api/)
Thanks a lot.
JS
For this you need to define uri-template instead of uri-mapping. This blog post explains more about this.
For your case I got it working as following.
Open your API configuration source which can be found at AM_HOME\repository\deployment\server\synapse-configs\default\api folder.
In the resource tag change url-mapping="/users/*" attribute to uri-template="/users/*"
But you will have to invoke the API as follows with additional context because when you say /users/* it means anything can come after users/. So you need to have a / after users context.
restserver.com:8280/context/1/users/usr?clientid=333