bulk download endpoints

They are API surfaces designed to hand over everything, not one row. FMP's REIT financials documentation describes how its 'bulk endpoints paginate the full universe in parts' - you still call an API, but each call returns a chunk of the entire symbol list rather than a filtered slice.

Outside finance the same label marks plain file delivery: EIA's Commercial Buildings Energy Consumption Survey (CBECS 2018) records bulk delivery access with 'Free downloads without registration', and IBEF's India Industry Reports carry bulk delivery as their access method. The common thread is completeness per call, whether as JSON chunks or static files.

Universe completeness is the product feature. Screening or backtesting across every listed REIT fails if your vendor returns only queried symbols; FMP's paginated-universe design exists precisely so nothing is missed.

Practical checks follow: pagination means progress tracking and resumability belong in your client, since a failed late chunk forces retries; and 'free downloads without registration' - as CBECS documents - removes onboarding friction entirely, though it also signals no usage guarantees. Vendors mixing bulk endpoints with keyed endpoints usually meter only the latter, so confirm which category each call falls into before forecasting quota burn.

1. Verify universe coverage. Bulk endpoints exist to return everything - test that the last pagination page matches the advertised total.

1. Check gating honestly. CBECS offers free downloads without registration; FMP-style endpoints sit behind integration keys - know your cost model.

1. Build resumable clients. Paginated full-universe pulls need checkpointing to survive interruptions.

1. Compare against static alternatives. IBEF report files may satisfy research needs without API integration at all.

• api-key-authentication - the gate often attached to commercial bulk endpoints.

Sector hub: office-reits data.