My company use different REST APIs from HERE, but on 23.March the Routing Matrix stopped working. Anyone else who experiences something similar?
We run a website on Episerver, and use Geocoder and Geocoder autocomplete to find the right position, and routing matrix to calculate det distance. Both the Geocoder and the autocomplete work fine, but the routing matrix returns the error:
"error": "Forbidden",
"error_description": "These credentials do not authorize access. Please contact your customer representative or submit a request here https://developer.here.com/contact-us to upgrade your account. You can also get valid credentials by registering for a free trial license on https://developer.here.com."
We have checked our payment, and have reached out to HERE, but can't get hold of it.
It can be that the number of allowed transactions have been reached. For any billing support questions, please email us at selfservesupport#here.com. They can have a look at your plan details.
Related
Currently working on building an address validator for a project I am working on, currently using a HERE account with a credit card attached for usage with the HERE Geocoding and Search API.
A minimal example to get started, a request to https://geocode.search.hereapi.com/v1/geocode?q=eiffel+tower&apiKey={{apikey}} is returning the following;
{
"error": "Forbidden",
"error_description": "These credentials do not authorize access"
}
I've confirmed the API key to be functional, as a request to the older API, like so https://geocoder.ls.hereapi.com/search/6.2/geocode.json?searchtext=eiffel+tower&apiKey={{apikey}} does work and returns expected results.
I'd like to use this API specifically, as it will be interfacing with a system that uses this version of the HERE API, and would like to maintain parity.
The documentation states that either API Key or OAuth are acceptable to use, and according to the linked identity & access management guide, this is done by simply adding the apikey query parameter, as seen in the working 6.2 example.
Other questions on the matter state that this code is returned when the endpoint is not usable on a base plan, however the pricing page indicates this should be usable on a free account up to 5000 requests.
You have linked your app_id, which are using is linked to as specific project.Because of this you are not able to use this app_id in the geocode service.
Please make sure that the app is linked to No project in the access manager as shown in the below screen.
Using the Here.com Freemium account, previously I was using the example here with my own API Key and some modifications to get the 7 day forecast. Based on this command, I had some code running in my back-end server every 2h collecting data, which ran for about a week without problems. I have not touched the code since then.
After a week, it stopped working.
Now, even when I generate a new API key, and use the same command, I get the following return data in Postman:
{
"error": "Forbidden",
"error_description": "These credentials do not authorize access"
}
Is my account restricted? It doesn't say anything about it in my Project page:
Without doing anything, suddenly it started working again, and on Oct. 1st.
I suspected I was being throttled, but when I tried using the service on a separate account, that also didn't work. So it seems likely the service was down. I wish there was some news page that posted what the status was?...
On developer.here.com you can look up the status of the services. I did this and don't see a reported problem for the Weather API for the last days.
My suggestion is that you missed to verify your email address after registering for your account. You still can do this at any time through clicking on the link that you received in an email from developer portal after your registration.
I am trying to integrate Authorize.Net in WooCommerce, using the following plugin for it: https://wordpress.org/plugins/yith-woocommerce-authorizenet-payment-gateway/
I set all user IdTransaction Key md5 Hash, but it gives me error 87, I don't understand where I need to put x_market_type as per the support document said.
This is the error I am getting:
From the Authorize.Net documentation about error code 87:
Response Reason Code: 87
Response Reason Text: Transactions of this market type cannot be
processed on this system.
Notes: The server is not configured to process the product type
derived from the market type of this transaction.
This can happen for four reasons:
You are attempting to process a type of transaction that your account
is not designed to process. For example, you attempt to use a card
swipe machine with an account that is enabled for Card Not Present
transactions.
Your software integration is passing an incorrect value
for the field x_market_type. If you are using a Retail account,
x_market_type should be set to a value of "2". The integration guide
for Card Present transactions can be found at
http://www.authorize.net/support/CP_guide.pdf.
Your Merchant Service
Provider may be incorrectly set up for this account.
The product type
(SIC code) is incorrect for this account.
It is recommended to check
the posting URL that is being used for your integration. Please
consult the guide for the integration method you are using to verify
the correct posting URL.
To help troubleshoot this issue, you can confirm the Product Type for
your account using the following steps:
Log in to your account at https://account.authorize.net.
Click Account from the main toolbar.
Click Merchant Profile.
Refer to the Product Type listed under Business Information.
I inherited a program that was written with the old LinkedIn API, and I'm trying to migrate it to the new API. When I try to get the r_basicprofile permission, my oauth token works. However, when I try r_network or rw_nus, I get a response
invalid scope -- your application has not been authorized for
r_network.
Yet, when I go to www.linkedin.com/developer/apps/xxxx/auth, the boxes for r_network and rw_nus are checked.
I.e., A request to
https://www.linkedin.com/uas/oauth2/authorization?response_type=code&client_id=xxxxxx&scope=r_basicprofile&state=yyyy&redirect_uri=http%3A%2F%2Fkalatublog.com%2Fwp-content%2Fmu-plugins%2Fimb-en%2Fhelpers%2Fsocial-connect%2Fapi%2Ffinalize.php%3Fapi%3Dlinkedin%26ch%zzzzz
works, but a request to
https://www.linkedin.com/uas/oauth2/authorization?response_type=code&client_id=xxxxxx&scope=r_network&state=yyyy&redirect_uri=http%3A%2F%2Fkalatublog.com%2Fwp-content%2Fmu-plugins%2Fimb-en%2Fhelpers%2Fsocial-connect%2Fapi%2Ffinalize.php%3Fapi%3Dlinkedin%26ch%zzzzz
gives that error. What am I doing wrong?
As of May 15,
After the grace period expires, several REST API endpoints will no longer be available for general use. The following endpoints are the only ones that will remain available for use:
Profile API — /v1/people/~ `
Share API — /v1/people/~/shares
Companies API — /v1/companies/{id}
If your application is currently using any other API services (e.g. Connections, Groups, People Search, Invitation, Job Search, etc.) you will have to apply to become a member of a relevant Partner Program that provides the necessary API access to continue to leverage any of the endpoints that are not listed above.
It looks like linkedin no longer wants to share anything with their API. Creating a new app indicates that the only possible options are r_basicprofile, r_emailaddress, rw_company_admin, and w_share:
TLDR: they have locked down the API and restricted the usage to an extremely limited set of access points.
I did some more digging. The linkedin website is misleading. On my app linkedin page, it says that I'm approved for rw_nus and r_network, but on this page
https://developer.linkedin.com/support/developer-program-transition
it says those are no longer approved.
So the app home page in linkedin incorrectly said I had those permissions.
Heres the link if you want to Apply for Linkedin
https://help.linkedin.com/app/ask/path/api-dvr
I have successfully written a tool to display upcoming calendar events on a website using Google's calendar API (v2). I am using the username/password method outlined at https://developers.google.com/google-apps/calendar/v2/developers_guide_dotnet#AuthClientLogin. Today an instance of this code would not return data or a decent error message. I finally logged into the web server and browsed directly to http://calendar.google.com and logged in using the credentials. I was challenged by Google's captcha and then my code worked.
How do I get around API calls being blocked by Google's captcha security? I don't want to have to re-code for magic cookies but I will if I have to. I have read some about generating tokens but I dont know if that is something I have to do once or every time the code is called.
If your app is a service that is getting used by many people, you might be running into API call bandwidth limitation. That is, google is limiting the number of API requests per time interval.
If this IS getting used by many people, you may have to upgrade to a paid account.