FTC API Not Returning RCMP Divisions

[NixFey]

Describe the bug
When GETing https://ftc-api.firstinspires.org/v2.0/2025/events?eventCode=USMICMP2WF, a 200 response is returned as {"events":[],"eventCount":0}, despite the event existing on the ftc.events site. This is inconsistent with a nonexistent event code, which returns a 404; and with divisions for last year, which return the data as expected.

To Reproduce
Steps to reproduce the behavior:

1. Call the events endpoint with the USMICMP2WF event code
2. Observe empty array returned

Expected behavior
Data for the divisions is returned, including the divisionCode pointing to the parent event.

Screenshots
N/A. See URL and response above

Device (please complete the following information):

• curl using a valid API key that successfully fetches information about other events

Additional context
These divisions were created several days ago by the lead FTA, so I wouldn't expect caching to be a factor after this much time has passed. Same behavior occurs for divisions under both of the FiM CMPs

[timtim17]

Maybe related, trying to view advancement for this event using the FTC-Events UI is giving me an HTTP 500
https://ftc-events.firstinspires.org/2025/USMICMP2WF/advancement

[NixFey]

Update: When teams got assigned to the events they started to be returned by the API. Not sure whether this is intentional as I would generally expect data in the API to match what is shown on the public site

[cmacfarl]

Update: When teams got assigned to the events they started to be returned by the API. Not sure whether this is intentional as I would generally expect data in the API to match what is shown on the public site

This is as designed. Divisions that are internally marked as unpublished, even though they appear on ftc-events, return an empty array from the API. This is likely why you thought this was a behavior change from last year. e.g. Last year you only executed this endpoint against published divisions.

A fix is in the pipeline for the HTTP 500 response. Thank you for reporting that @timtim17.