APOD Ingestion Timing
Nobody has claimed this yet.
- Dominant language
- SCSS
- Stars
- 555
- Forks
- 140
- Avg merge
- 2h 30m
- Merged PRs (30d)
- 3
Description
After playing around with the API for a bit, it appears that today's APOD details are not available through the API.
For context, I am based in Europe. When I start my workday I check APOD and can see the images. I want to integrate an API call into a self-hosted dashboard to see the APOD as a part of that dashboard. It appears the details have not been ingested into the API database alongside the apod.nasa.gov update.
To avoid web-scraping I would appreciate pushing an update to align with midnight UTC, or at least midnight EST.
Here is an example for today's curl request:
$ date
Fri Sep 11 12:59:00 PM CEST 2026
$ curl -s "https://api.nasa.gov/planetary/apod?api_key=${NASA_API_KEY}&date=2026-09-11"
{"code":404,"msg":"No data available for date: 2026-09-11","service_version":"v1"}
Please let me know if I can contribute in any way.
Best,
Daniel
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the missing-date response from the APOD endpoint with the curl request shown, comparing the API result with the APOD website for the same date. Trace the ingestion schedule and timing that populate this endpoint. Done means the current APOD is available through the API by the agreed UTC or EST cutoff, with the behavior verified for a newly published date.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100