Confirm Lillio (formerly HiMama) has no public API and plan a manual export-based workflow instead
domain: support.lillio.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Check Lillio's support/help center and engineering job postings for any mention of a public developer API before assuming REST/GraphQL access
Contact Lillio support (support@lillio.com) to confirm current integration options, since HiMama-era naming and articles are still being migrated post-rebrand
For data portability needs, plan around manual exports or reports available in the Lillio/HiMama app rather than an API integration
Track the HiMama-to-Lillio rebrand (completed November 2023) when searching documentation, since older HiMama-branded articles may be outdated or redirected
Re-verify periodically, since Lillio's engineering team (Rails/React/GraphQL stack) could ship a public API without wide announcement
Known gotchas
Lillio's internal stack uses GraphQL, but that is their internal application architecture, not evidence of a published public API for third parties
Because the HiMama-to-Lillio rebrand is relatively recent, some support articles and contact addresses (himama.com vs. lillio.com) coexist, and only one may be current
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?