We may provide a limited API service free of charge or at discounted rate to students and researchers to support their work. Each situation is unique, but there are some general guidelines and conditions that will apply to everyone:

• Purpose of the work must be specific and related to your studies or research.
  The API key will be granted for specific educational or non-profit research purposes only. Data obtained under this arrangement must not be used, either directly or indirectly, for any other private or business purposes, in part or in full.
  
• Student / Researcher plans will be time-framed (normally, from a week up to several months) and quotas will be tweaked according to the specific needs of your work.
  
• Credits to AeroDataBox API must be given clearly visible in your work: we may request a link to or a copy of your end work or publication to verify that.
  
• We reserve a right to request a confirmation of you working on a specified project and/or studying in a specified educational institution (this may be, but is not limited to: requesting a copy of your student ID, coming in contact with your tutor, etc.).
  
• General terms of use are still applicable to any student API key, unless contradicting to this page.

This list might seem a bit daunting, but all of these conditions are largely common sense. Obviously, we cannot enforce each one of these conditions. That is why every student plan is to be issued with a grain of trust that a key will be used responsibly!

What information do we need from you?

Do you want to request a custom free / discounted plan? Don’t hesitate to contact us. To expedite processing, make sure to include the following details in your initial request to us:

1. The name of your educational institution.
   💡It will be a great idea to contact us from the e-mail assigned to you by your education institution. E-mail domain of your institution will make your request more credible.
   💡Please ensure that the e-mail address you’re writing from is able to receive reply messages from outside the network of your educational institution, or provide us an alternative e-mail to reach out to you. Otherwise, we won’t be able to respond to you!
   You may as well include alternative e-mail address inside your message.
   
2. A brief description of the purpose or your project.
   The purpose must:
   – be specific (too vague or too general descriptions are generally not very trustworthy);
   – be academic (e.g., you’re doing a project for your school, university, or college);
   – not raise reasonable suspicion that a key will be used for business or non-academic purposes.
   General trial requests, requests for in-house corporate training, etc. won’t be accepted.
   
3. A list of API endpoints you want to use.
   💡Requests for using all endpoints at once are not likely to be accepted.
   
4. An (approximate) estimate of how many calls you expect to make for each endpoint in the list above.
   💡Estimates can be difficult, we know. But without this information, we won’t be technically able to assign you a custom student plan. We need to enter actual numbers into the setup form.
   💡Requests for unlimited or too intensive use won’t be accepted.
   
5. An estimate when and for how long you will need the custom plan (is it a week, a month, or a semester?). Please provide the date range (when you plan to start and end using the API).
   💡Requests for perpetual, unspecified or too lengthy periods of time won’t be accepted.
   
6. Your username on RapidAPI or API.Market
   💡 To invite you to a custom (free or discounted) plan, we need to know your username or email on the respective API Marketplace that you would like to use.
   Subject to technical requirements of a specific API Marketplace we may ask you to subscribe to our free plan first, before we will be able to send the invite, that’s why it will be a good idea if you subscribe to it beforehand.

Please note that custom plans for students & researchers is our voluntary initiative. No-one is automatically entitled to them. We may sometimes refuse issuing a key for any reason, which may be not necessarily related to your work (for instance: there are technical issues currently, the load on the API is at capacity, there are too many students or free API keys active at the moment, etc.).