I am trying to use HERE api to get some charging station data. I signed up for a freemium account and verified my email address and added credit card information. I am using Postman to send requests but unfortunately I get the error " These credentials do not authorize access". I am not sure why I am getting this error. I got my API key.
Getting response as below:
"error": "Forbidden",
"error_description": "These credentials do not authorize access"
EV Charging Station API is not supported with our Lite & Explore SDK edition (refer screenshot atttached). Please review our plan vs feature dashboard at https://developer.here.com/plan-features. Do let us know if you are trying to use the API with REST, JavaScript or Premium SDK - share the AppID details to investigate further.
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.
I'm having intermittent issues with signing in to LinkedIn with the LinkedIn Sign In API.
By intermittent I mean, I have two LinkedIn accounts, and as of this week one of them is unable to use the API to sign in to external services, such as the LinkedIn application I develop.
I'm authenticating via Auth0, whose engineers have confirmed there is an issue:
Over the last few weeks, the current version of the LinkedIn API for
sign-in has been intermittently failing when fetching the user
profile, causing a small number of users to fail to log in. The cause
of this issue is currently unknown, and is coming from LinkedIn
directly.
https://community.auth0.com/t/linkedin-connection-deprecated/20484/18
The Auth0 response i'm getting is the following (I've replaced senstivie response values with 'XX'):
{"name":"a0.response.invalid","message":"unknown error","json":{"error":"invalid_request","error_description":"InternalOAuthError: failed to fetch user profile (status: 500 data: {\n \"errorCode\": 0,\n \"message\": \"Internal API server error\",\n \"requestId\": \"XX\",\n \"status\": 500,\n \"timestamp\": 1550474289966\n})","state":"XX"},"status":0}
I know this API is being depreciated in March, but it's imperative that this API continues to work until the decommission date. I'm wondering if anyone has found a work around or solution to this issue, as it's impacting my ability to run real-world trials of my application scheduled in this week.
I've contacted LinkedIn support who directed me here.
Auth0 recently released a change to LinkedIn social connection, allowing you to use the new LinkedIn API (Version 2). You can change this by going to Connections-->Social-->LinkedIn-->Strategy Version dropdown and select Version 2. This should fix most of the login issues with the old deprecated version of LinkedIn API. More information post.
While using Share Api i got response as follows
{
"serviceErrorCode": 100,
"message": "Not enough permissions to access: POST /shares",
"status": 403
}
this is due to the fact that for the linkedin V2 API you need to become an linkedin partner. this can take up to a month befor you get a response.
Partnering with LinkedIn provides you with additional API functionality & data access, increased call limits & dedicated support. Read more about our various Partner Programs and use cases and see if one is a match for your app. Applications are only accepted when we feel that they're providing value to members, developers and LinkedIn.
for more information see this link :
https://developer.linkedin.com/partner-programs
I want to build a travel portal using sabre soap api. But soap api credential is not found in my account section of developer site(https://developer.sabre.com). I have submitted contact us page several times to get the credential. But there is no reply from sabre. Can anyone please help me to get the credential of sabre soap api?
The setup process usually goes getting access to the Sabre GUI (Sabre Red Workspace) and then getting access to the APIs. So i would try this route.
Other way to go is to contact your (future) ticket issuer/consolidator if you are not an IATA Office/number holder yourself.
I am interested in seeing if Sabre's FareNabber is an API that works for an application I am building.
The documentation here https://developer.sabre.com/docs/read/rest_apis/air/search/fare_nabber does not explain where/how the notifications get posted to after a subscription made. All I see is the following:
FareNabber nabs the itinerary options and pushes the results to the customer for a purchase decision.
Is this an email to the customer? Is this an HTTP POST with a JSON payload to a server I provide so I can handle the actual email transmission? Where is this documented?
Re Endpoint you set this up during activation:
Note: This service requires activation, please contact your Sabre Account Representative for assistance.
Actually yes you get a JSON - its specified here: http://files.developer.sabre.com/doc/providerdoc/STPS/fare_nabber/v100/FNB_LowFareNotification.json