We now return a helpful error if you provide an invalid pagination cursor to our "list" APIs

For our list APIs (e.g. "List airports"), we split all of the records into multiple pages rather than return a huge response with thousands of airports. You can paginate through those records using the before and after query string parameters.

Previously, if you provided an invalid before or after value, sometimes we'd return a 500 Internal Server Error error. We've fixed that, so now you'll get a more helpful error.