API Docs¶
The support microsite public documentation hub links to generated protocol and API documentation. Those public pages are iframe shells, so the BFDev docs chatbot cannot index their content directly.
Use this section as the private, indexable entry point for those API documentation sets. Each page records the public documentation URL, source path, related BetterFleet services, and retrieval terms that help the chatbot find the right reference.
Public API Documentation Sets¶
| Documentation | Public docs | Source path | Main product area |
|---|---|---|---|
| OCPI | ocpi-integrator-587b19.gitlab.io | integrations/ocpi-integrator |
Roaming and shared charging |
| OCPP | evenergi.gitlab.io/vemo/packages/vemo-ocpp-core | packages/vemo-ocpp-core |
Charger control and charger protocol handling |
| OSCP | vemo-oscp-3d8b73.gitlab.io | integrations/vemo-oscp |
Energy flexibility and grid integration |
| VDV | vemo-vdv-6ec88d.gitlab.io | integrations/vemo-vdv |
Public transport schedule and vehicle data exchange |
| Yard State | vemo-yard-interface-c63737.gitlab.io | integrations/vemo-yard-interface |
Yard, vehicle, and depot-state integration |
Maintenance Notes¶
- Keep this section in sync with
bf-support-microsite/public/docs.htmland the iframe pages underbf-support-microsite/public/docs/. - Keep the public URL as a normal Markdown link so MkDocs search and the chatbot can cite it.
- Prefer adding stable summaries and domain terms here rather than copying large generated HTML output by hand.
- If generated API docs need full chatbot coverage, add a sync step that converts the source generated docs into Markdown under this section during the BFDev docs workflow.