Authenticate CleanCloud customers and handle password login from a custom pickup-and-delivery app.
domain: cleancloudapp.com · 4 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
POST customerEmail and customerPassword to https://cleancloudapp.com/api/loginCustomer to validate credentials and retrieve the customer's ID.
Only rely on loginCustomer if CleanCloud is managing the customer's password (set via customerPassword on addCustomer/updateCustomer).
Use the customerID returned by login to fetch that customer's subsequent order, card, or subscription data.
Build a corresponding password-reset flow for customers who forget their CleanCloud-managed credentials.
Known gotchas
customerPassword is only meaningful if CleanCloud itself is meant to manage login — if the client app owns authentication independently, this field isn't needed.
As with every CleanCloud endpoint, loginCustomer is a POST request, not a GET, despite being a read/verification action.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?