I am trying to send a request to the Bing Local Business Search API using Postman.
It's giving a 404 status.
If I use the default URL not the regional one that matches my key it will return invalid key which makes sense, sounds like it's connecting properly.
But if I use the regional southcentral endpoint from my dashboard it returns a 404.
I signed up for the free plan and generated a key that I am using.
Here are my settings in postman. Thanks in advance.
I think you'll need to go into the Azure Portal. Under Cognitive Services create a new service with Bing Search v7 under the free tier. It should give you a global location. After it's created you'll get your keys. At least that worked for me. Their initial "Welcome page" keys did not work for me either, I don't understand why.
Then you'll be able to call - https://api.cognitive.microsoft.com/bing/v7.0/localbusinesses/search?q=chicago+restaurants&mkt=en-US
I think you need to URL encode the search params, the space after q=chicago should be %20.
Related
I can not get response from skyscanner api. Did I write something wrong?
https://skyscanner-skyscanner-flight-search-v1.p.rapidapi.com/apiservices/referral/v1.0/UK/GBP/en-GB/EDI/LHR/2021-05-26/2021-05-26?shortapikey=ra66933236979928&apiKey={shortapikey}
The endpoint you're trying to access doesn't exist. That's why it's returning 404.
Visit the homepage of Skyscanner API on RapidAPI Hub and take a look at the different endpoints it supports.
I believe you want an endpoint that return fligh information. Check out the endpoints available in the Browse Flight Prices category and pick a best one for you according to your needs.
I need to export a list of groups in G Suite to compare with the source from a recent migration from another mail provider. I'm stuck, trying to get Postman desktop client to connect via api to the Directory API of our g suite instance.
Basically I'm an API noob and have no idea how to get the two to talk. I've setup an OAuth2 client ID and Secret, but not sure of what settings to use in Postman to get authentication up and running. Using Authorization code or Client ID as the option for "Grant Type", either way I get a 401 error.
The only field I haven't entered anything in is the "Callback URL" not sure where to get it from. Seeing mixed info in Google's documentation. Do I need a service account or just the OAuth ID and secret?
Closest I've gotten is: "Invalid parameter value for redirect_uri: Missing scheme: /" using the Authentication code grant type. Left blank but I'm almost sure that is referring to the callback url.
What am I missing here? Or where do I find the callback URL if that is all?
Here is a script that should handle authorization and export a CSV of all your groups.
https://github.com/jmathai-google/all-groups-in-customer
I'm trying to use WSO2 API Manager 1.10.0 on an existent micro-services project with REST APIs following WSO2 tutorial.
I have installed it on my computer as well as a copy of my application and configured AM to manage requests (GET, POST and DELETE) to my resource but I always obtain a "Response code 0" with Response Header
{
"error": "no response from server"
}
Trying to contact my application using Advanced REST Client I obtain 200 with the correct result.
My APIs use a token inside the header to authenticate the user passed so I have implemented a dummy API without authentication but I still have the same issue.
I have tried also the Cloud version with our test server but still obtaining the same result.
I found this guide http://wso2.com/blogs/cloud/video-setting-up-custom-url-for-api-store-and-gateway/ but I don't know if this can be a solution for the problem in localhost.
Setting up the custom url in WSO2 API Cloud wont help. Thats there for a different purpose. There are two things you can do.
If you are interested in going ahead with the cloud version, you can get help from them. You can send a support request and the cloud team will help.
You can troubleshoot your local instance. When doing so, first, try to invoke your api via curl and see whether it gets a response. Sometime, your api can work fine, but due to some reasons, the result might not reach the api console.
If the curl works fine or not, you can check the logs to see whether there are any errors printed. Some more questions:
Is your backend service exposed via http or https?
If it is https, then if its certificate is not a CA signed one, API Manager will fail during the handshake. If so, you will have to add the cert to api managers client-truststore.jks
In the cloud scenario, your backend should be accessible from internet and the certificate story is valid for cloud too.
Are you trying to access the api using swagger console (or any web application). There are couple of reasons you could encounter this issue. one could be certificate not installed in the browser.
If this happens you should see some error log in the api manager console (something related to CA not found). for that first you can copy the backend url (swagger console shows the url it used to send the request) and paste it on a new browser window and install the certificate to the browser.
also you can get an idea about the issue by using a tool like firebug and check the request. (it will show the error for not connecting the AM)
Finally I have found the issue: the API Manager does not accept plain text response, responding using a JSON solves the problem.
Using other mediatype such as XML or TEXT/HTML it reports 406, with text plain it returns Error 0.
I've been trying to test Google Glass Mirror API but I guess it's dead since they've quit its development.
Requests are made to this url (https://www.googleapis.com/mirror/v1,), but it states "Not found". Playground itself is open, but doesn't send anything to the device.
Does anyone know if there's a way of overcoming this? Or if they changed the server location?
Sincerely,
Apidcloud
If you are trying to access the exact URL you specified (https://www.googleapis.com/mirror/v1), it won't work. That isn't a valid endpoint itself for the API. All of the API calls are to URLs that start with that prefix. For example, once authorized, the URL https://www.googleapis.com/mirror/v1/timeline should get the timeline items for the authenticated user. Other paths either retrieve or take action.
If the playground is not sending anything to the device, that is usually an indication that you didn't auth the playground and the device against the same Google account. Make sure you follow the auth directions listed on the Playground page.
Brand new, checking out wso2 API manager 1.8.0. I work for a corp with multiple organizations/teams, so setting up multi-tenancy seems like the logical choice.
Following the quick start guide, I first created a new tenant, gave it a domain of "dev.api.myorg.company.net", added some users to it, and I can log in. I added one API.
I am able to hit the endpoint using the URL listed in the store:
http ://wso2server.company.net:8280/t/dev.api.myorg.company.net/apiname/v1/endpoint
But my expectation was that configuring this tenant with a domain would allow me to hit:
http ://dev.api.myorg.company.net:8280/apiame/v1/endpoint
I have pointed the dev domain to the wso2server IP, but when I try to access using the dev api I get:
http://pastebin.com/VNXjEv3y
Am I just missing something completely obvious? Is there extra work to make wso2 allow tenants to point their domains at it?
I have spent the last hour and a half googling and searching through tagged wso2 here, but google mostly points to the wso2 multi-tenant docs page, which is like a single page without any details.
Any pointers to better docs or suggestions for better search terms? Ive tried combinations of:
wso2 multi tenant tenancy domains hosts how to access
when you create an api in a tenant it will get the following url pattern
http ://**<IP-where apimanger is hosted>**:8280/t/<tenantdomain>/<apiname>/<version>/
where 't' denotes this api url is specific to tenant and tenantdomain denotes which denant
but for super tenant url will be as following
http ://<IP-where apimanger is hosted>:8280/<apiname>/<version>/
For tenanants, domain is just a name (not having mapping to ip).So APIM will not work as you expect.Because you need to specify the IP(or domain) where APIM is hosted in the url.