HTTP 500 INTERNAL_ERROR on every request, including the documentation portal — new Personal account

FlightAware AeroAPI
1

Every request my account makes to AeroAPI returns the same error, regardless of endpoint or parameters:

{“title”:“Internal error”,“reason”:“INTERNAL_ERROR”,“detail”:“Internal error has occurred”,“status”:500}

What I’ve verified:

  • It happens on ALL endpoints I’ve tried, not just one (e.g., /schedules/{date_start}/{date_end}, /airports/{id})
  • It happens in the documentation portal’s TRY feature while logged in — even with the endpoint’s own default parameter values
  • Same result via the API directly with the x-apikey header
  • Generating a brand-new API key did not help
  • A payment method is on file
  • Tried multiple parameter variations (IATA and ICAO airport codes, near-term and future date ranges, with and without filters) — identical error every time

Account details:

  • Personal tier, newly created on [date]
  • Username: [your username]
  • [I did / did not] change my username after signing up
  • API key ends in: [last 4 characters]
  • Failing request timestamps: [date, time, timezone]

This looks like the same account-provisioning issue described in these earlier threads, where every request 500s and the fix was made on FlightAware’s side:

  • “500 Internal Server Error Test API” (Jul 2025) — resolved by staff, attributed to a username update
  • “500 Internal server error on every query” (Apr 2025)
  • “All tests on the testing env. responds with: INTERNAL ERROR” (Feb 2024)

Could someone take a look at my account’s provisioning? I’m mid-evaluation of the /schedules endpoint for a larger route-verification project that would run on the Standard tier, so I’d love to get unblocked.

Thanks!

2

Hello,

You should be good to give it another try.

3

Hi — following up on the account fix you made for me (thank you — the HTTP 500 INTERNAL_ERROR responses stopped). Unfortunately the account now has a different problem: every request, on every endpoint, including the TRY feature in the documentation portal while logged in, returns:

{“title”:“Unauthorized user”,“reason”:“UNAUTHORIZED_USER”,“detail”:“User is not currently subscribed to AeroAPI”,“status”:403}

A handful of calls succeeded briefly right after your fix, then everything switched to this 403. Payment method is on file. I am still on the Basic plan, I need to see this working at least briefly before subscribing to the paid plan.

If this is on your end, can you restore the subscription linkage on the account?

Thanks again for the help on the last issue.

4

Try one more time for me, sorry about the delay.

5

It’s working now, thanks.

6

But now I’m trying to upgrade from Personal to Standard and it tells me:

Something went wrong and we are unable to process your request at this time.

7

I am still getting that message when I try to upgrade to the Standard plan. Please help me give you my money. :slight_smile: