API design
Connect the useful ideas.

Design decisions connect every market on BidAPI.com. These articles examine capability maps, normalized data, source identity, authorization, and the boundary between observations and commands. The aim is to reuse useful infrastructure without erasing the rules of the underlying market.

Use this reading path when you are deciding how many objects an integration needs, what a state transition actually means, or which parts of a provider response should remain source-specific. Architecture, real-estate data, domain acquisitions, event handling, and cost planning approach those questions from different directions. Start with one concrete workflow and compare its requirements before introducing a universal abstraction. The documentation section provides small, labelled example objects that can support that process.