I am currently developing a web app using self-service Amadeus API in a production environment, I have questions related to the static data, kindly reply.
Questions:
1. Is there any static data available related to flights schedule or any other detail which we can store on our end and get it synced in some scheduled manner, in place of fetching all data every time using APIs.
2. In case we have static data then what will be the ideal time duration to refresh data.
3. Are we allowed to store real-time data on our end temporarily? If yes then for what duration we can keep a copy of same.
4. Is there any API where we will send a list of Flight/Segment Id and get details only of those selected records. What I mean is we like to know details of 10 specific flights/segments. So can we get the information related to those 10 flights/segments whose id we will pass to API?
5. What's the response time of search API and API which returns details of the flight.
6. What all filters available in search API to filter data.
As of today, ee do not provide static data for flights schedule
/
You are allowed to store the data coming from the flight search API as long as you do not resell it in any way. Keep in mind that this data changes a lot (price/availability)
You can use the Flight Offers Price API for this. Flight Offers Price takes a list of flight-offers (that you get by using the Flight Offers Search API). For those flights-offers the API revalidates the price and the availability.
It depends on where you are based, which API you use and how you use it (filters), you can try our APIs for free in our test environment. Keep in mind that the test environment is limited in terms of the number of API calls, data and has a slower response time than the production environment
Our catalog is fully open (no need to register) you can find the Flight Offers Search reference documentation here listing all the parameters available. The Flight Offers Search API has 2 endpoints:
GET a simpler version of the search, easy and fast to implement but offering less filtering
POST offering a full access to all the functionalities of the flight search
Related
I would like to know if there is an API that gives freely the flight paths of all aircraft currently flying or that had flight some days ago over the world. It could be in any projection and any format. I imagine that it would be most likely a table with each row being an aircraft/flight and the correspondent geopath in one column.
Thanks.
I was looking around for the same topic.
The terms and conditions for getting data from Flightradar24 are shown there
https://www.flightradar24.com/terms-and-conditions
... they talk only about getting data after a business contract on the kind of data (e.g. flights with a specific filtering) and on the format (JSON, CSV, ?). With the contract one may download the data, maybe via an API.
My conclusion: Flightradar24 does not share its full set of data, only a limited set with payment.
Searching for "Flightradar24 API" you will find some sites offering Flightradar24 data via their own API primarily requiring payment, a few for free at a very low level.
You will also find some software projects for accessing and processing data from the Flightradar24 sites with a focus on Python. But these software packages build on tracking the access of the Flightradar24 site from a mobile app or the desktop browser. Result: a few accesses of an endpoint may work then comes the stop sign: Flightradar requires an authenticated access.
I am trying to play around with FedEx APIs: https://developer.fedex.com/api/en-us/home.html
and actually I would like to know, is it possible to track new created Shipment via Ship API on sandbox/test environment?
Actually I've tried to create multiple different types of Shipments validate them, and received 200 Ok response, however I wasn't able to track it by tracking number returned in response, so the question is it possible at all on API sandbox environment to create Shipment and find it by tracking number on FedEx site or using Track API's Track by Number Endpoint.
Cannot find such limitations in documentation, so will be very appreciated if someone can shed light on this.
I think it's not possible to track with the tracking IDs which you get from ship API.
But you can track the orders with the mock tracking numbers from here.
It's really very irritating because when we get the tracking IDs in the test environment, we should be able to track the orders by using them in the test environment. FedEx should have to focus on this.
I am getting repeated and limited result for flight and hotels search listing in Amadeus self service api. Also search flights data is repeating more than one time. What is the reason? Am I doing any mistake or self service apis only give limited data?
Can you please share your code so we can understand what you are trying to do?
Note that if you are getting limited results it might be because you are using the API in the test environment. Our test environment is based on a subset of the production data. In case you want to see what our test data includes, please refer to our test data collection on GitHub.
If you are done prototyping your application and want to access to live production data, we recommend you follow our "Moving to production guide", it offers easy to follow instructions on how to move to production. Please keep in mind we also provide with free monthly quotas in the production environment, to allow you to explore the data available
I have been looking online and saw many similar/same posts but all were extremely old (latest I found was from 2011) so since technology changes, I thought I ask too.
I wonder how a flight comparison website (where you cannot book flights and can only be redirected to other websites) get their data.
Is it all by now through api's or is it throgh scrapping data (which would be not so reliable)? Ive been reading online, trying to find out if thats the case but it doesnt really seem that EVERY airline and EVERY flight search website (with booking option) provides an api. So I wonder how sites like Kayak get their data if not every airline/every flight booking website provides an api?
Also, I came across some api's like
QPX Express API
skyscanner travel api (which I checked out on some website which is using it and it does seem that data is quite limited ?!)
Travelport api
Amadeus API
Sabre travel api
Wego Affiliate Network (which seems really great but search takes super long)
I wonder if anyone has experience with the mentioned api's and how good their are /if using them is 'the way' of doing it or if its actually much more realiable to request data directly from each airline and booking website (if thats possible)?
Thanks a lot!
If we take Kayak as the example, as that is who you mentioned, they approach the data in two forms.
They have API PULL connections to GDS companies (i.e. Sabre), some airlines and large online travel companies such as Expedia etc.
Smaller airlines in particular PUSH their inventory and fares from their inventory to companies such as Kayak.
Aggregation companies generally provide PUSH access though companies who want to PUSH their data have to comply with the aggregators requirements/standards.
It is a supply and demand service. Aggregation companies will generally request access to large established companies, however, will also allow companies to push their data to them if they wish.
The data is not normally scrapped, it is through API and web service platforms.
I am working on one product which is fetching all the organization/workspace and app details of the customer. The customer can refresh them any time.
So let’s say I have one customer who has 100 applications across multiple workspaces so around it is making around 110 calls to get each application detail, workspace details and organizations.
Now if that customer refreshed the applications multiple times like 10 times in an hour so the action only for that is 1000 API calls. If I have 50 such users active and doing this thing then it will be something 50000.
AFAIK I can not make so many API calls in an hour so how to handle this scenario. I know a lot of applications are doing such things so want to understand how everyone is handling this.
If you need a higher rate limit, I would encourage you to contact Podio support and ask specifically for what you need. We have internal guidelines for evaluating these kinds of requests and may increase the limit for your user and client ID if appropriate.
In general, though, I would expect your app to implement some kind of batching, transient storage, and/or caching layers, especially if your customers are interacting with Podio exclusively or primarily through your system.
Please see our official statement here: https://developers.podio.com/index/limits
Summary:
The general limit is 5,000 API calls per hour, but if the API call is marked as "Rate limited" in the API reference the call is deemed resource intensive and a lower rate of 1000 calls per hour is enforced. If you hit the rate limits the API will begin returning 420 HTTP error codes for all API calls. Rate limits are per user per API key.
Contacting support:
If you have a project that requires a higher rate limit contact support#podio.com with a brief description of your project, your estimated usage and the client_id of the API key you are using.
Usage tips:
Tips for reducing API usage
Avoid making API requests inside loops. Instead of fetching individual objects inside a loop, fetch a collection of objects in one API operation. E.g. filter items
Cache results whenever possible. This is especially true when you are displaying data to the public (i.e. every sees the same output).
Don't poll for changes. Instead of polling Podio to see if your content has changed use webhooks or push to receive a notification. This might save you thousands of requests: https://developers.podio.com/doc/hooks
Use logging to see how many requests you're making
Bundle responses with "fields" parameter
You might want to build an API proxy app; you would need a messaging queue and a rate limiter. This would lets you keep track of the api calls consumptions across apps and users.
Also worth noting: some API routes are more expensive than others if they are more resource intensive on the Podio side… The term in use is rate-limited: rate limited api route are bound to 1k calls an hours, so in effect costs 5 times as much as regular routes.
Hope this helps!