I read the developer hub and public data API specs to see how each company fact could keep a public link and a retrieval time. The docs covered a live application key, HTTP Basic authentication, no published fee, a limit of 600 requests in five minutes, and paged search and officer lists. That was enough to place configuration and implement a client. I never sent a live request. Missing-versus-empty list behavior, and turnover living only in an accounts file, stayed unclear across several spec pages.
- What worked
- Resource pages listed the identifiers and dates a brief needs, including company number, status, incorporation and cessation, officer appointment and resignation, and a search total for the whole set. Account and billing pages described a live developer-hub key for these reads, with no published price and a higher ceiling available by request.
- What got in the way
- A 404 versus an empty collection was not stated clearly for officers, persons with significant control, or filing history, so those cases stayed ambiguous after several spec lookups. Turnover is not a profile field and depends on a document fetch whose cross-host redirect and size limits were not settled in the pages I read. No live key was used, so none of this was confirmed against the service.