I can't use API's start_date: when I set the minimal date to a few years ago, I'm getting this message:

An error occurred in the application and your page could not be served. If you are the application owner, check your logs for details.

I can't even set the start_date to 2017-01-01 😞

RE: #34 but unrelated to that pr

There are some issues with \r \n popping up with Credit or Credit and Copyright in the title fields...

e.g.
https://api.nasa.gov/planetary/apod?api_key=ENTER_YOUR_DEV_API_KEY&date=1996-09-25
"title": "Bright Stars and Dark Clouds\nCredit:",

https://api.nasa.gov/planetary/apod?api_key=ENTER_YOUR_DEV_API_KEY&date=1996-09-26
"title": "Tonight: A Total Lunar Eclipse \r\nCredit and Copyright:",

Requests made to the API with the data parameter set for July 25, 2010 fail with an internal server error.

Request:
https://api.nasa.gov/planetary/apod?date=2010-07-25&api_key=DEMO_KEY

Response:

{
  "code": 500, 
  "msg": "Internal Service Error", 
  "service_version": "v1"
}

The date's APOD is valid and available though as it can be viewed at https://apod.nasa.gov/apod/ap100725.html

Presumably the underlying issue could affect other dates but this is the only one that I have surfaced so far and I'm unable to identify a potential cause to test further. For example, though the media type for this date is a video, other dates for which the content is a video do not share the problem.

While calling the api it is giving a sever application error message.Even the DEMO_KEY is not working.
Please respond soon.

These APODs are returning 'media_type' as 'other' but without any image/video content. The json response does not include a 'url' field, although some return a 'digg_url' field. I tested these through the https://apod.nasa.gov/ site as well and it seems these links may have broken content. Here is the complete list:

5/29/2006 - https://api.nasa.gov/planetary/apod?date=2006-5-29&api_key=DEMO_KEY | https://apod.nasa.gov/apod/ap060529.html - No digg_url - No image/video content at apod.nasa.gov
5/22/2007 - https://api.nasa.gov/planetary/apod?date=2007-5-22&api_key=DEMO_KEY | https://apod.nasa.gov/apod/ap070522.html - No digg_url - Flash content at apod.nasa.gov not working
12/31/2008 - https://api.nasa.gov/planetary/apod?date=2008-12-31&api_key=DEMO_KEY | https://apod.nasa.gov/apod/ap081231.html - Has digg_url - No image/video content at apod.nasa.gov
4/5/2009 - https://api.nasa.gov/planetary/apod?date=2009-4-5&api_key=DEMO_KEY | https://apod.nasa.gov/apod/ap090405.html - Has digg_url - Flash content at apod.nasa.gov not working
6/29/2009 - https://api.nasa.gov/planetary/apod?date=2009-6-29&api_key=DEMO_KEY | https://apod.nasa.gov/apod/ap090629.html - No digg_url - Youtube embedded content not working
5/10/2010 - https://api.nasa.gov/planetary/apod?date=2010-5-10&api_key=DEMO_KEY | https://apod.nasa.gov/apod/ap100510.html - No digg_url - Youtube embedded content not working
6/8/2010 - https://api.nasa.gov/planetary/apod?date=2010-6-8&api_key=DEMO_KEY | https://apod.nasa.gov/apod/ap100608.html - No digg_url - Youtube embedded content not working
8/25/2010 - https://api.nasa.gov/planetary/apod?date=2010-8-25&api_key=DEMO_KEY | https://apod.nasa.gov/apod/ap100825.html - No digg_url
12/15/2010 - https://api.nasa.gov/planetary/apod?date=2010-12-15&api_key=DEMO_KEY | https://apod.nasa.gov/apod/ap101215.html - No digg_url
1/23/2011 - https://api.nasa.gov/planetary/apod?date=2011-1-23&api_key=DEMO_KEY | https://apod.nasa.gov/apod/ap110123.html - No digg_url
2/1/2011 - https://api.nasa.gov/planetary/apod?date=2011-2-1&api_key=DEMO_KEY | https://apod.nasa.gov/apod/ap110201.html - No digg_url
2/22/2011 - https://api.nasa.gov/planetary/apod?date=2011-2-22&api_key=DEMO_KEY | https://apod.nasa.gov/apod/ap110222.html - No digg_url
3/7/2011 - https://api.nasa.gov/planetary/apod?date=2011-3-7&api_key=DEMO_KEY | https://apod.nasa.gov/apod/ap110307.html - No digg_url - Youtube embedded content at apod.nasa.gov not working

Also, these APODs return 'media_type' as 'other' but the content at apod.nasa.gov is to Youtube embedded videos. In consideration to consistency, is it possible to change these to 'media_type' 'video' and then include a 'url' field to the youtube url?

For example, APOD 7/1/2020 - https://api.nasa.gov/planetary/apod?date=2020-7-1&api_key=DEMO_KEY returns video and the URL to the Youtube content. While these do not:

8/10/2009 - API: https://api.nasa.gov/planetary/apod?date=2009-8-10&api_key=DEMO_KEY | https://apod.nasa.gov/apod/ap090810.html - Has digg_url
1/20/2010 - API: https://api.nasa.gov/planetary/apod?date=2010-1-20&api_key=DEMO_KEY | https://apod.nasa.gov/apod/ap100120.html - Has digg_url
1/24/2010 - API: https://api.nasa.gov/planetary/apod?date=2010-1-24&api_key=DEMO_KEY | https://apod.nasa.gov/apod/ap100124.html - Has digg_url
5/26/2010 - https://api.nasa.gov/planetary/apod?date=2010-5-26&api_key=DEMO_KEY | https://apod.nasa.gov/apod/ap100526.html - No digg_url
7/25/2010 - https://api.nasa.gov/planetary/apod?date=2010-7-25&api_key=DEMO_KEY | https://apod.nasa.gov/apod/ap100725.html No digg_url
8/25/2010 - https://api.nasa.gov/planetary/apod?date=2010-8-25&api_key=DEMO_KEY | https://apod.nasa.gov/apod/ap100825.html - No digg_url
12/15/2010 - https://api.nasa.gov/planetary/apod?date=2010-12-15&api_key=DEMO_KEY | https://apod.nasa.gov/apod/ap101215.html - No digg_url

Lastly, these are not issues but they feature Flash content. I wonder if it's possible to get only the flash embedded video?

4/13/2009 - API: https://api.nasa.gov/planetary/apod?date=2009-4-13&api_key=DEMO_KEY | https://apod.nasa.gov/apod/ap090413.html - Has digg_url

Thank you!!

There can be huge number of developers using APOD api for displaying every day APODs in a way that they want to. However, except image, when there'll be a video APOD, it's not easy to showcase a preview of the thumbnail.

In my current research- I have found that there can be videos from the following sources: YouTube, Vimeo and other. However, I have never came across the last type i.e. Other.

For YouTube it's little easy to create a thumbnail out of the video URL. But for Vimeo it's not easy at all. Vimeo requires you to make another API call to their server and from there you will get a thumbnail.

Can we do this on APOD server and provide a thumbnail in the same url and hdurl parameters?

If you will provide this it will be much much easy for we developers.

Is there are any plan for CI like github action and unit test for flask api ?

Change documentation on api.nasa.gov to make it clear whether or not rate limits with a key apply per IP address or to any combination of API addresses. This is relevant to people who are developing Apps that might one day have thousands of users.

This issues requires checking the rate limits across a couple APIs on different IPs with the same key then submitting change to the documentation, just don't have the time to do it right now.

Hello,

I'm getting this message on the concepts key.
concept_tags search param is set to True.

There is a way to turn on the functionality?

Example URL

https://api.nasa.gov/planetary/apod?api_key=DEMO_KEY&date=2014-10-01&concept_tags=True

Response

{"concepts":"concept_tags functionality turned off in current service","copyright":"Francesco Antonucci","date":"2014-10-01","explanation":"The bright clusters and nebulae of planet Earth's night sky are often named for flowers or insects. Though its wingspan covers over 3 light-years, NGC 6302 is no exception. With an estimated surface temperature of about 250,000 degrees C, the dying central star of this particular planetary nebula has become exceptionally hot, shining brightly in ultraviolet light but hidden from direct view by a dense torus of dust.  This sharp close-up of the dying star's nebula was recorded in 2009 by the Hubble Space Telescope's Wide Field Camera 3, and is presented here in reprocessed colors.  Cutting across a bright cavity of ionized gas, the dust torus surrounding the central star is near the center of this view, almost edge-on to the line-of-sight. Molecular hydrogen has been detected in the hot star's dusty cosmic shroud. NGC 6302 lies about 4,000 light-years away in the arachnologically correct constellation of the Scorpion (Scorpius).    APOD Wall Calendar: Nebulas and Star Clusters","hdurl":"https://apod.nasa.gov/apod/image/1410/butterflyblue_hst_3919.jpg","media_type":"image","service_version":"v1","title":"The Butterfly Nebula from Hubble","url":"https://apod.nasa.gov/apod/image/1410/butterflyblue_hst_960.jpg"}

Throughout the day, the API has been down and returns an error 503 response.

Visiting the provided test url https://api.nasa.gov/planetary/apod?api_key=DEMO_KEY leads to an "Application error" on the Heroku service.

Testing with my own application key (That had worked prior & intermittently) also resulted in the same error.

Hi, my app received in the last couple of days placeholder image instead of the real image trhought the API with the text:

This is a fallback image used in the case where there is a missing/corrupted asset on apod.nasa.gov. Image source: https://en.wikipedia.org/wiki/File:Black_Hole_in_the_universe.jpg

Wondering is this just a temporary glitch, is it possible to detect these temporary placeholders somehow in my app, or not return these placeholders by the API at all? Thanks.

Hello, in the APOD for 2020/06/04 is showing the yesterday´s picture:

{"date":"2020-06-03", "explanation":"very time Venus passes the Earth, it shows the same face. This remarkable fact has been known for only about 50 years, ever since radio telescopes have been able to peer beneath Venus' thick clouds and track its slowly rotating surface. This inferior conjunction -- when Venus and Earth are the closest -- occurs today. The featured animation shows the positions of the Sun, Venus and Earth between 2010-2023 based on NASA-downloaded data, while a mock yellow 'arm' has been fixed to the ground on Venus to indicate rotation. The reason for this unusual 1.6-year resonance is the gravitational influence that Earth has on Venus, which surprisingly dominates the Sun's tidal effect. If Venus could be seen through the Sun's glare today, it would show just a very slight sliver of a crescent. Although previously visible in the evening sky, starting tomorrow, Venus will appear in the morning sky -- on the other side of the Sun as viewed from Earth. Experts Debate: How will humanity first discover extraterrestrial life?", "media_type":"video", "service_version":"v1", "title":"The Dance of Venus and Earth", "url":"https://www.youtube.com/embed/Cd5a5KdPxQc?rel=0"}

https://api.nasa.gov/planetary/apod?api_key=DEMO_KEY&date=2018-10-07

Getting below error:

{"code":500,"msg":"Internal Service Error","service_version":"v1"}

because of this, I can't even use the API request with start_date and end_date contains above date.

For example this API calls will also not work:

https://api.nasa.gov/planetary/apod?api_key=DEMO_KEY&start_date=2018-10-07&end_date=2018-10-08

https://api.nasa.gov/planetary/apod?api_key=DEMO_KEY&start_date=2018-10-01&end_date=2018-10-08

Please fix 7th October. Looking forward to hearing back from you.

If you visit this URL, it will show you an APOD from 27th May 1999, cool, right? But what will happens in 2099? Again a Y2k problem?

https://apod.nasa.gov/apod/ap990527.html

When reading through the docs and looking at the examples, it seems like the copyright field isn't listed as something that can be returned? Are there any more fields that haven't been added?

Another short question, is this the API that is being served currently from https://api.nasa.gov/planetary/apod? If yes, then how come many of the fields aren't documented on https://api.nasa.gov/?

What is the span of time on which the X-RateLimit-Limit server response is determined? I think it's per hour, but I'm not 100% sure.

As per title, when the change in what day is "today" happens?
Looking at the code, it seems that datetime.today().date() returns the local datetime, so what local is that?

Don't take it as sarcasm. However since the API returns both images and videos it would be more semantic to rename it as Astronomy Picture or Video of the Day.

~/Documents/workspace/apod-api$ python setup.py install
Traceback (most recent call last):
  File "setup.py", line 39, in <module>
    scripts = [os.path.join("bin", file) for file in os.listdir("bin")]
FileNotFoundError: [Errno 2] No such file or directory: 'bin'

This is because the setup.py file is trying to list every file in the bin directory which does not exist:
https://github.com/nasa/apod-api/blob/master/setup.py#L39

My api key is getting a 403 error, which is strange because it worked fine last night when I went to bed. Is the API down or something?

Is there any way I can pay for unlimited/really high usage rates? I have a cool iOS app and want it to be fully funcitonal

I testing API-NASA-APOD by what is written on the site https://api.nasa.gov

Precondition: Query parameter 'date' need contain date which received response JSON with key 'media_type: image'

Actual result: received response with key 'hd' in JSON
{"date":"2014-05-05","explanation":"How do you calibrate a huge gravitational lens? In this case the lens is the galaxy cluster Abell 383, a massive conglomeration of galaxies, hot gas, and dark matter that lies about 2.5 billion light years away (redshift z=0.187). What needs calibrating is the mass of the cluster, in particular the amount and distribution of dark matter. A new calibration technique has been tested recently that consists of waiting for supernovas of a very specific type to occur behind a galaxy cluster, and then figuring out how much the cluster must have magnified these supernovas through gravitational lensing. This technique complements other measures including computing the dark matter needed to contain internal galaxy motions, to confine cluster hot gas, and to create the gravitational lens image distortions. Pictured above from the Hubble Space Telescope, galaxy cluster A383 shows its gravitational lens capabilities on the right by highly distorting background galaxies behind the cluster center. On the left is a distant galaxy shown both before and after a recent revealing supernova. To date, calibration-quality supernovas of Type Ia have been found behind two other galaxy clusters by the Cluster Lensing And Supernova survey with Hubble (CLASH) project. Follow APOD on: Facebook, Google Plus, or Twitter","hdurl":"https://apod.nasa.gov/apod/image/1405/abell383sn_hubble_1200.jpg","media_type":"image","service_version":"v1","title":"Galaxy Cluster Magnifies Distant Supernova","url":"https://apod.nasa.gov/apod/image/1405/abell383sn_hubble_960.jpg"}

Expected result: received response without key 'hd' in JSON

cURL Request: curl --request GET 'https://api.nasa.gov/planetary/apod?api_key=DEMO_KEY&hd=false&date=2014-05-05' --data-raw ''

When I make an API call to https://api.nasa.gov/planetary/apod?api_key=DEMO_KEY right now (Thu, 01 Oct 2020 01:30:49 GMT) I get a 404:

{
  "code": 404,
  "msg": "No data available for date: 2020-10-01",
  "service_version": "v1"
}

It’s currently Sep 30 in my time zone, not Oct 1. I understand if the server wants to give me Oct 1’s image after midnight UTC, but if so it shouldn’t give me a 404.

I suspect that's because the "current date" default sometimes changes before the image is actually made available (due to time zone differences, maybe?):

However it looks like there is already some code to handle this. So I guess that's not working properly:

https://earthobservatory.nasa.gov/about

Wonder if it is possible to have an earth-api using Earth Observatory - Anyone want to investigate how possible this might be?

Hello, there's a wrong image link when I'm requesting 2018-08-06 APOD: https://apod.nasa.gov/apod/http://nusoft.fnal.gov/nova/public/img/FD-evt-echo.gif

Should be http://nusoft.fnal.gov/nova/public/img/FD-evt-echo.gif

We dont need to supply instructions for deployment.

There seems to be a block of dates that the api returns a title of "tomorrow's picture" instead of the correct title.
There also seems to be an issue with other dates returning "information" https://github.com/nasa/apod-api/issues/23

Since the video URL is a YouTube video i've to embed It using iframe.
Is possibile to use <video> so can customize my video player?

Providers

• YouTube
• Vimeo

APIs

• https://developers.google.com/youtube/player_parameters
• https://developer.vimeo.com/player/sdk

See also

• https://developer.mozilla.org/en-US/docs/Web/Guide/Audio_and_video_delivery/Video_player_styling_basics

First noticed with the APOD from April 22, 2021: the APOD's file extension is all upper case (.JPG): https://apod.nasa.gov/apod/image/2104/ISS002-E-7377c.JPG

Is this to be an expected behaviour, also for other APOD images (in the future)? Or is this an issue with this individual provisioned APOD image file?

Asking because my case-sensitive apache2 complained about this one image - whereas this has not happened on any images within the last couple of months or even years, to my knowledge. Wondering if I should update my code, or if it should be given that the APOD usually is continued to be provided in all lowercase.

The APOD for this day returns Luk\u00e1\u009a Vesel\u00fd as the copyright field.

This \u009a character does not represent š. According to the Unicode Latin-1 supplement, \u009a is Single Character Introducer, which can't be displayed graphically. š should instead be \u0161.

The copyright should therefore be Luk\u00e1\u0161 Vesel\u00fd

This was initially raised on the JSON parsing library GSON, where there's a little more info.

The coverage can't run since code re-organization because module was changed.
And I'm trying fix it.

There is a number of JSON responses that have "Information:" in the title field. This is an example:
https://api.nasa.gov/planetary/apod?api_key=uBHdRJkKAl917xAmxxaAqtRig5PtTzotpfw5v9v4&date=1996-09-21

So I'm developing an async python wrapper for the NASA APIs as a side project. As I worked on the APOD part I noticed some things. I also, since finding this repository, have thought of some questions about design decisions made with regard to this API.

1. The date parameter defaults to "today", which I figured out means "today UTC" because starting at exactly midnight UTC the API throws a 404 until that day's page is uploaded. Was this intentional? It seems like it would make more sense to, when no date parameters are passed, default to the most recent valid date.

2. I noticed this API is literally just pulling the data from the APOD website directly. Is there a reason you're not using a cache system or a database of any kind? It seems like this wouldn't be difficult to implement but would make maintaining the API significantly easier.

Hello,

i used the APOD API in my first app which i built to learn using the Ionic Framework. The app is free/ad-free and i published it in the play store some days ago.

Some months ago i contacted NASA through various e-mail addresses i found in the API and contact pages (such as this one https://data.nasa.gov/Space-Science/Astronomy-Picture-of-the-Day-API/ez2w-t8ua) but still no response. I fear my limit will be exceeded quickly as soon as some people download and start using the app.

As stated in the website:

For each API key, these limits are applied across all api.nasa.gov API requests. Exceeding these limits will lead to your API key being temporarily blocked from making further requests. The block will automatically be lifted by waiting an hour. If you need higher rate limits, contact us.

But i can't manage to contact them :(

What can i do? Thanks.

I've followed all the steps in README, from setup to running the project. But when I try to run it through dev_appserver.py ., it raises the following exception:

google.appengine.tools.devappserver2.errors.AppConfigNotFoundError: "." is a directory but does not contain app.yaml or app.yml

I couldn't find this file inside the project (sorry, I'm not so experienced in GAE). Should I create my own app.yml file? Or is something missing?

The following request is producing an Internal Server Error:

Request:
https://api.nasa.gov/planetary/apod?thumbs=true&date=2020-09-12&api_key=DEMO_KEY

Result:
{"code":500,"msg":"Internal Service Error","service_version":"v1"}

Removing the 'thumbs=true' query parameter solves it, so it probably has something to do with getting the video thumbnail. In this case it is a Vimeo video. Getting a range of pictures with 2020-09-12 included will also result in the same error.

Today's JSON explanation var content:
"The Crab Nebula is cataloged as M1, the first on Charles Messier's famous lis"

The original text is much longer...

Can we, like the rest of the inhabitants of the planet Earth, who love science, astronomy and space, to absorb them in universities in order to serve the interest of mankind and discover broader horizons in development and knowledge .. ??

This is perhaps a duplicate of (also raised by me!) #18.

2020-10-25 returns a copyright of Tom AbelRalf KaehlerKIPACSLACAMNH, whereas on the APOD site it is Tom Abel & Ralf Kaehler (KIPAC, SLAC), AMNH.

Looks like commas, ampersands, and parentheses still aren't parsed correctly!

Today's request returns a 400 error when using the thumbs parameter:

https://api.nasa.gov/planetary/apod?api_key={api_key}&date=2020-01-21&hd=true&thumbs=true

Full Message:

{"code":400,"msg":"Bad Request: incorrect field passed. Allowed request fields for apod method are 'concept_tags', 'date', 'hd', 'count', 'start_date', 'end_date'","service_version":"v1"}

The documentation says the parameter is ignored if not a video. This is a video, but I'm guessing the way the url was entered as an embed (https://www.youtube.com/embed/hgzGET6owYk?rel=0) caused the thumbnail creation to break?

My app which does use this feature of your API just does not work as consequence :(

end_date=2020-06-9:

end_date=2020-06-10

The following request is producing an Internal Server Error:

Request:
https://api.nasa.gov/planetary/apod?api_key=[APY_KEY]&start_date=2020-09-12&end_date=2020-09-21&thumbs=true

Response:

{
  "code": 500,
  "msg": "Internal Service Error",
  "service_version": "v1"
}

Removing the 'thumbs=true' query parameter solves it

The API returns a copyright of NASAESAHubbleSubaru TelescopeW. CramerYaleet al.M. YagiJ. DePasquale.

It should be NASA, ESA, Hubble, Subaru Telescope, W. Cramer (Yale) et al., M. Yagi, J. DePasquale.

Can You please add this http header?

Access-Control-Expose-Headers: X-RateLimit-Limit, X-RateLimit-Remaining

I wanted to display the data in the footer of my app.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Expose-Headers

Example (actually null):

const a = response.headers.get("X-RateLimit-Limit");

Note:
Since I'm using different endpoints from https://api.nasa.gov/, if this is a solution, a good feature, I'm looking to spread the change request across multiple endpoints.

Regards
Mattia

I ran into 500 errors attempting to view data on prod for certain dates using my dev api key...

https://api.nasa.gov/planetary/apod?api_key=ENTER_API_KEY&date=1995-06-16 is successful
https://api.nasa.gov/planetary/apod?api_key=ENTER_API_KEY&date=1995-06-17 => 500 error
https://api.nasa.gov/planetary/apod?api_key=ENTER_API_KEY&date=1995-06-18 => 500 error
https://api.nasa.gov/planetary/apod?api_key=ENTER_API_KEY&date=1995-06-19 => 500 error
https://api.nasa.gov/planetary/apod?api_key=ENTER_API_KEY&date=1995-06-20 is successful

I don't know how to express this concept but I think it would be right that the query parameters are not interdependent, that is to say that they return a bad request in the event that some are used simultaneously with others. It is reasonable that there are limits for the single parameter as for the date of tomorrow however in my case where I am trying to map with a web form, this API forces me to show or not some controls programmatically to avoid bad requests.

Use case (could updades)

https://asteroids-nasa.herokuapp.com/apod.html

screenshot

I think it would be interesting to have an option to choose a specific media_type.
A lot of developers only want pictures, not youtube links (Astronomy Picture of the Day). This way we wouldn't have to check every time we make a request.

Currently we're forced to set our api keys in the api_key URL parameter. It would be extremely useful if we could set it in an Authorization header of some sort. It is also recommended to do it like this.