If you want JSON data, it does not exist natively. But you can request the RSS feed version:
https://www.jetphotos.com/search?q=Boeing+777&format=rss
This returns clean XML/RSS. For most developers, parsing this RSS feed is the closest thing to an official JetPhotos API.
What the RSS feed gives you:
Limitations:
Spotters use apps to verify if an aircraft has been previously photographed. With an API, you could submit a registration (N27291) and receive a boolean response: "exists": true plus the most recent photo date.
GET /v2/aircraft
curl -X GET "https://api.jetphotos.com/v2/aircraft?search=747" \
-H "X-API-Key: YOUR_API_KEY"
JetPhotos prioritizes stability for its paying partners. While specific limits vary by contract, standard expectations are:
Best Practice: Implement Caching Do not request the same registration every second. Use Redis or Memcached to store API responses for 24–48 hours. Since aircraft registrations rarely change overnight, caching reduces your quota usage and improves your app’s speed.
| Code | Meaning | |------|---------| | 401 | Invalid or missing API key | | 429 | Rate limit exceeded | | 404 | Photo or endpoint not found | | 422 | Invalid parameters | jetphotos api
The standard search URL is: https://www.jetphotos.com/search
By appending query parameters, you can generate specific data sets.
Key Parameters:
Since JetPhotos does not publicly publish API docs, you must:
https://api.jetphotos.com/v1