Technology · Integrations
An API buys
the right to connect.
Buyers often ask whether a platform 'has an API' as if the answer proves two systems already work together. It does not. An API is an option to build that connection, and the quality of the option determines whether it is worth paying for.
The reframe
Availability is not usefulness.
A list of endpoints can still leave a parking operator unable to identify the right property, subscribe to a vehicle-ready event, retry a failed write, or test without touching production data.
The buyer should evaluate the future job: who will build the connection, which system owns each fact, how failures surface, and whether access can be limited to one partner and one purpose.
The option
What makes an API operationally valuable
Five qualities that survive the demo
Identity
Stable objects
Sessions, vehicles, properties, and people need durable identifiers so two systems can discuss the same thing.
Change
Events, not constant polling
A webhook or event feed tells the property when something changed instead of making it repeatedly ask.
Recovery
Safe retries
A timeout leaves uncertainty. Idempotent writes let a client retry without creating the same action twice.
Boundaries
Scoped credentials
Access should be limited to the company, property, data, and actions the integration actually needs.
Practice
A nonproduction environment
Builders need realistic objects and failures before a live guest or payment is involved.
Separate product truth from preview language
A vendor can responsibly open a design partnership before it offers a public, supported interface. The buyer only needs the status stated plainly.
Public API
PRODUCT- Documented access and support terms
- Versioning and change expectations
- A surface buyers can independently evaluate
Private preview
PARTNERSHIP- Use cases shape the early contract
- Capabilities may not be finished endpoints
- Access and timelines are negotiated
→Valletto's own API page says private preview and explicitly says there is no public endpoint yet. That is the current product boundary.
Price the whole connection
The endpoint is rarely the expensive part. Ownership and operations determine the lasting cost.
Build
Initial implementation
Mapping, authentication, error handling, testing, and launch coordination belong in the estimate.
Run
Ongoing monitoring
Someone must notice delayed events, rejected records, expired credentials, and upstream changes.
Change
Contract evolution
Versioning and deprecation policy decide whether today's integration becomes tomorrow's emergency.
Exit
Data portability
The option has value only if the operator can retrieve the records needed to move or build elsewhere.
The buyer's test
Bring one real workflow, including its failure.
Ask the vendor to trace a vehicle request from creation through an event, a timeout, a retry, and a permission refusal. A useful API conversation becomes clearer under failure, not vaguer.
The takeaway: an API buys leverage only when its objects, events, boundaries, and recovery rules are real enough to build on.
