HERE maps enterprise routing api with base licence - here-api

is enterprise-routing API supported with free base license if not are there some speed limits information accesible only with base licence? I could not find these information in their docs. Thank you

Speed Limit information can be obtained using the getLinkInfo endpoint as in this example:
https://route.st.nlp.nokia.com/routing/6.2/getlinkinfo.json?waypoint=52.5308,13.3846&app_id=XXX&app_code=YYY.
According to Available Features and Functionality page, the getLinkInfo endpoint is not checked as being allowed with "Limited Free Usage with Base Web Key". Hence you should probably enquire about an enterprise license using the get in touch button on the Getting Started page

Related

HERE: 403 These credentials do not authorize access

I'm trying to call https://tourplanning.hereapi.com/v2/problems API end-point. For this reason I'm obtaining Oauth2 token as it was described in this guide. I'm able to obtain a token, however, when using with the end-point above I'm getting 403: {"error":"Forbidden","error_description":"These credentials do not authorize access"}
Does anyone have an idea how to overcome it?
The following features are excluded or limited. Please contact us if you are interested in one or more of these:
Electronic Horizon in the HERE SDK (Premium Edition)
Geovisualization REST API (Geovisualization via JavaScript is
included)
Tracking REST API. For a free trial go to https://tracking.here.com
and select "Try our app"
Matrix Routing requests above 15x100 size in many-to-many matrices
and 100x1 size in many-to-one matrices are excluded (they are
included with the Pro Plan)
- Tour Planning
Live Sense SDK Beta
Geocoding and Search API Bring Your Own Data (for this a subscription
to HERE Workspace is required)
For more information you can go through the following link for plan details.
https://developer.here.com/plan-features

Google Map API - Plan selection

We are planning to develop a web based application for one of the Research Institute.
Overview of the application:
It is survey application
It requires login credentials for data-entry operator to open web-app for collecting participant’s information
It has fixed number of login credentials for data-entry operators (No user registration)
Google Maps APIs will be used in this application for locating and collecting participant’s address details (Places Search APIs and
Reverse Geo coding)
We have gone through the following links
https://developers.google.com/maps/pricing-and-plans/
https://developers.google.com/maps/terms
As this application will be used by Research Institute, We are not sure which plan (Standard/Premium) can be used for such type of application.
Also we are not able to connect with Sales team where we can evaluate the application for correct billing plan.
We need help on following items
Identifying correct plan/package for pricing and legal terms as the customer is a research institute
How can we connect to direct Googles' sales team for clarifying or identifying correct plan as there is no direct support available except for Premium plan?
After different searches (googling) and connects found below URL to connect with Google Support team for Map API queries
https://enterprise.google.com/intl/en_in/maps/contact-form/
Note: We got response from google support team after aprox. 7 days. So expect minimum 7 days for response.
Hope this would help to someone having similar query.
Thanks!

Is it possible to get my personal info from linkedin api without oauth?

I'm setting up a personal page, and I would like to display my past work experiences and other data I have on linked-in so it is automatically updated when I update my linked-in profile. Is this possible without having to do oauth? I just want my own data.
No.
As the company says on their REST API page:
In order for your applications to access LinkedIn member data and/or act on their behalf, they must be authenticated. LinkedIn relies on the industry standard OAuth 2.0 protocol for granting access, due to its simplicity and ease of implementation.
See also this previous SO question.
This doesn't mean, however, that OAuth can't be handled for you:
As a convenience, if you are developing a front-end JavaScript or
Android application, we provide SDKs to handle the authentication
process for you.
Additionally, there are several 3rd party libraries available in the
open source community that abstract the OAuth 2.0 authentication
process for you in every major programming language.
As for the major languages they support, LinkedIn provides walkthroughs in PHP, Python, and Java on their API Get Started page.

How to perform cross-domain SAML-based authentication/trust

I have a product which consists of internal ASP.NET/MVC web sites all using WIF to enable SSO through a custom STS/IdP service. We now have a new partner site hosted outside our network on another domain and would like to enable SSO for users as they navigate between the sites. The new site uses different technologies (e.g. python) but we assume we can create a trust relationship using SAML standards as the protocol.
With SAML as the underlying protocol we assume this can be achieved but we cannot find any guidance on patterns for implementation, best practice guidance, etc... Can some recommend some resources on how to establish this type of cross-domain trust?
Note: While other options like OAuth could address this, we would prefer to stick with a SAML-based solution
Does your custom STS/IdP service support SAML?
On the python side, they will need a SAML stack. There's a number around - refer Introduction to OneLogin's SAML Toolkits e.g. There's a good diagram there as well that shows the login flow.
Then you need to get the python SAML metadata and give them your custom STS/IdP SAML metadata.
Import on both sides, configure whatever assertions you need and you should be good to go.
You'll also need to sort out the signing certificates that go into the metadata.
Example of process using simpleSAMLPHP - Configuring the SP
Following provides excellent example of SAML implementation:
http://www.codeproject.com/Articles/56640/Performing-a-SAML-Post-with-C
We used it in our project and it worked fine.

Google Calendar API - Appropriate API Key Solution to Exceeded Quotas

I have a custom Windows service developed in C#.NET that synchronizes users' Google calendars with an internal calendar.
Per the Google Calendar API documentation, I'm using the below code. I believe this is referred to as the ClientLogin method which may or may not be advised (I've found conflicting information in the Google documentation).
CalendarService service = new CalendarService("Your app name");
service.setUserCredentials("username", "password");
This worked fine in testing. Now that things have moved to production, I'm receiving errors such as "The user has exceeded their quota, and cannot currently perform this operation" and "User has modified too many events today. Please try again tomorrow." This began more than a day ago and has remained as such.
I've researched this considerably and am still confused on a few points. Any help would be greatly appreciated.
What is the daily quota per user?
Are the (really low?) quotas there because an API key isn't being used by my application?
If I were to use an API key, which approach would I use for a Windows service in which I have the usernames and passwords for the Google users? - Simple API, OAuth2, Service Account, etc.
FYI: I am using the API .NET library provided by Google. If I should be using a particular authentication approach, I would appreciate a sample illustrating the implementation using the .NET library provided via Google.
First of all you definitely don't use the latest version of the library. You can download it from NuGet. You should download the following two packages:
https://www.nuget.org/packages/Google.Apis.Calendar.v3/
https://www.nuget.org/packages/Google.Apis.Authentication/ (be aware that in the next release we are going to improve the OAuth2 flows significantly, and support WP, Windows 8 application).
Regarding your questions:
1-2) Calendar API supports 100,000 requests/day. You can find that information in the Google API Console in the services tab.
3) Definitely OAuth2. Read more here and here.
You can find code samples with the current implementation of OAuth2 in our samples repository (https://code.google.com/p/google-api-dotnet-client/source/browse/?repo=samples)

Resources