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!
Related
For monitoring, we are using Application Insights.
Since we are advertising on multiple platforms, (Google, Facebook, LinkedIn, other 3rd party platforms) one of the business goals is to track which marketing dollars on which platform result in most subscriptions, and pour more money there.
To do that I need to know which platform did user originate from.
Where do I find, where the user originated from, in Azure Portal? (referer URL maybe),
If it is not supported "out of the box" I would have to guess I need to pass parameter in URL that would indicate the platform or something similar like grab a cookie, how does one track where the user originated from?
This is obviously a solved problem, but I am having a hard time finding any articles on how to do this the way Microsoft expects it.
Possibly a duplicate of Does Application Insights track referrer url?, which is more specific.
App insights itself is a broad set of APIs across various technologies. Not all of those things have referrer information available to them.
In general, wherever you collect information from, you'd send it as a custom property / custom dimension in the telemetry that you send.
Custom dimensions can be used for whatever purposes you want, so there's no standard of how Microsoft expects them to be used.
I have sent couple of emails to support team for become a sabre customer, I have submitted the application to get the access at following link.
https://www.sabretravelnetwork.com/home/solutions/travel_agency/contract_selector/without_arc2
Pls let us know if I am missing anything?
Thanks
Access to the PNR (Passenger Name Records) requires a contract with Sabre. They only give this access to travel agents or companies writing services for travel. There is also associated fees. Also you need to be aware there are costs for every PNR you create. So its not as easy as just getting access to the PNR.
I know this is not the answer you want but its how it works.
If your just trying to build out a small booking engine I would suggest getting into Expedia's API toolkit. Much easier and allot less expensive to get into.
Hoping for a bit of guidance / reassurance on air search and book flow in Sabre (SOAP API) which I'm integrating with for a client website project.
My client is planning to take payment separately via a 3rd party payment gateway and also have a 3rd party ticketing robot.
The details I have been given from the ticketing robot company is that we should create the PNR then queue transfer to "International/Domestic Agent Q50" (with their PCC).
I've got access to and have been reading the Sabre Dev Studio, have access to the Sabre SOAP API (I have my client's credentials and PCC) and have followed the "Low Far Search and Book" workflow here (https://developer.sabre.com/docs/read/workflows/Low_Fare_Search_and_Book) exchanging EnhancedAirBookRQ and PassengerDetailsRQ for CreatePassengerNameRecordRQ as advised on that page and inserting payment before, my proposed work flow is:
Create a token with TokenCreateRQ
Use token to perform a search with BargainFinderMaxRQ
Display results to customer, customer picks an itinerary / flight segments
Collect customer details from customer
External payment gateway take payment for amount returned in BarginFinderMaxRQ
Book the desired flight segments using the orchestrated API CreatePassengerNameRecordRQ, including:
Adding passenger details and flight segments
Specifying that the payment was in cash
Performing the queue transfer?
I've got BargainFinderMaxRQ coded up and working.
I'm starting the integration with CreatePassengerNameRecordRQ and have noticed the price returned can be different to the price returned from BargainFinderMaxRQ. Which makes me question the above work flow. I selected it due to the easier integration (I can use tokens rather than manage a session and it's just one API call).
So, my questions:
Is my understanding correct, is this the correct work flow for the project? Given that my client is taking payment via an external payment gateway and want to display the final figure to the customer before they pay.
I'm struggling to understand how the ticketing robot fits into the process. Hoping for a steer on how that affects the PNR call(s). Do I still set the ticket type to "7TAW" and queue place onto their PCC + queue number?
Thank you for any help, greatly appreciated.
1) Yes, the process is correct, but there are scenarios in which airlines change fares or where the airline does not confirm the availability immediately, so when you price you are actually pricing an IATA fare, which is usually more expensive. For particular scenarios, I recommend you to contact the API support.
2) The "7TAW", which is the ticketing time limit, is meant to have the limit set by the airline until when you can issue the ticket without having the possibility of losing the given price. Some airlines require that to be done on the same day of the booking (which is what you are setting with the 7TAW). Some airlines give you some days and some others can give you just 30 minutes after booking. It is almost impossible for us to respond on how would the robot require this to be provided, so for you to be sure, I would recommend you checking with the owners of that robot and ask them how would they want it, maybe they don't even care.
Was wondering if anyone knew of an existing solution for browsing the Face API data I set listing and viewing the person-group hierarchy, persisted faces and person-faces, etc. Of course my own app persists the data that has been sent/received to the API but I'm looking to browse the server side.
Thanks
So got an official answer from MSFT Cognitive Services support (real quick turnaround!):
"We currently do not have a console app that provides the capabilities that you are seeking. The current avaialble method to retrieve this lit is done through Person Group - List Person Groups and Person - List Persons in a Person Group."
Guess its code then.
In my application , I use the following APIs of the companies API,
https://api.linkedin.com/v1/companies/id={id}
and
https://api.linkedin.com/v1/companies/{id}/updates?event-type=status-update
With the new API program, do I need to change my existing application ? I find the description on the linkedin developer website regarding the same as not comprehensive enough. If I need to continue with the app, do I really need to get into a partnership program with linkedin or can I continue like I do currently.
We recently contacted the LinkedIn Support regarding the changes.
So first endpoint will be available to you without getting into PartnerShip program. 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}
The second Endpoint will require Partner Ship program with LinkedIn you can apply here
But it will not involve code changes because they will give privileged access to your App. At the time of applying for partnership program they will ask for LINKEDIN_APP_KEY and LINKEDIN_APP_SECRET. They will provide access to these KEY and SECRET.