Bike-sharing API: integration with hotel PMS, delivery platforms and internal systems

The mistake of having "isolated" bikes

Imagine a hotel with 8 CityFlow bikes in its lobby. They work, but every time a guest wants to use one, they have to go to reception to ask for the QR. Reception writes it down by hand. Zero data. Zero integration. That's the scenario you do NOT want.

What changes with a connected API

When CityFlow integrates via API with your hotel PMS (Mews, Cloudbeds, Apaleo, Opera) or with your building's app:

• The guest books the bike from the hotel's own app (without downloading another one).
• The charge goes straight onto their hotel bill.
• Usage data flows into your CRM (you know which guests use bikes the most).
• The branding is 100% the hotel's.

That small change turns the bike from "just another amenity" into "an integrated premium amenity".

CityFlow API — key capabilities

1. User provisioning

Create/delete users from your system. When you check a guest into the PMS, the CityFlow user is created automatically.

2. Trip data

Receive a webhook when a guest starts/ends a trip. Useful for billing, CRM and ESG reporting.

3. Fleet status

Query in real time which bikes are available, in use or in maintenance.

4. Dynamic pricing

Apply different rates by guest type (VIP, repeat, premium suite).

5. Branding

Configure the embedded app with your hotel's colours/logo.

Integration examples

Boutique hotel in Barcelona

Mews + CityFlow integration. The guest books from the hotel app, the charge goes on the bill, reception has full visibility. Bike adoption rose from 18% to 47% after integrating.

Be Casa building, Madrid

Integration with the building's internal app. The tenant has the bike "right there" without downloading another app. Bike amenity NPS: 9.1.

Bike-sharing operator in Seville

Fleet OS + Stripe + integration with the municipal identity-validation system. Launched in 60 days.

What working with our API is like

• REST + Webhooks: a modern standard, easy to integrate.
• Public documentation: Swagger/OpenAPI at docs.cityflow.app.
• Sandbox: a test environment so your dev team can experiment without touching production.
• Technical support: a CityFlow engineer assigned during the integration.

Conclusion

Standalone bikes are an amenity. Bikes integrated with your internal systems are a measurable competitive differentiator. CityFlow is one of the few B2B operators with a real, open API. If you're serious, integrating is the way.

Want to see the API or an integration case? Talk to sales.