Mobile API
The first-party surface the Guiru app talks to. Documented so it is not a mystery, not so you build on it.
GET
/api/v1/mobile/homeauth ·
gat_… (mobile scope)The store home, resolved server-side: shelves, capsules and the call to action already decided, so a client never guesses where a transaction happens.
GET
/api/v1/mobile/search?q=&category=&platform=&page=auth ·
gat_…Capped page sizes. Rate limited at 120/minute.
GET
/api/v1/mobile/library?group=using|want_to_try|tried|stopped_using|entitledauth ·
gat_…What the person has, in the groups the app shows.
GET
/api/v1/mobile/products/<slug>auth ·
gat_…One product, with its offers and seals resolved.
GET
/api/v1/mobile/notificationsauth ·
gat_…POST to the same path marks read.
POST
/api/v1/mobile/devicesauth ·
gat_…Register for push. DELETE stops it. Revoking the token under Settings → Apps signs that device out.
Also here: /relationship and /interest (what somebody is using, wants, has stopped using) and /account. Payloads are bounded by design — there is no endpoint that returns the catalogue.