EwityDevelopers
All recipes
📱

Custom branded mobile app

Ship a merchant-branded iOS/Android ordering app powered by their live POS.

1–2 weeks Agencies · chains wanting their own app

Same Ewity Platform API, native shell. Reuse the ordering flow but wrap it in push notifications, saved addresses and loyalty. The API is identical — you're just rendering it in React Native / Flutter / Swift.

The build, step by step

  1. 1

    Pair the merchant with Connect

    Same one-code Connect flow — merchants enable your app inside Ewity POS.

    • GET{your_connect_url}
    • POST{your_connect_url}
    Read the docs for this step
  2. 2

    Cache the catalogue for offline browse

    Pull the full catalogue, cache locally, refresh on CatalogueUpdated.

    • GET/stores
    • GET/locations/{locationId}/catalogue
    • POST/locations/{locationId}/catalogue/lookup
    Read the docs for this step
  3. 3

    Order + push notifications

    Validate, place the order, and turn webhook events into push.

    • POST/validate
    • POST/orders
    • POST{your_webhook_url}
    Read the docs for this step

…or hand it to an agent

This prompt briefs an AI coding agent to implement the entire recipe against the live docs — authentication, every endpoint, and webhooks.

Build it with AI

Copy this prompt into your coding agent.

Build a native-feeling branded ordering app on the Ewity Platform Orders API (https://api.ewitypos.com/platform-v1). Put the Bearer <EWITY_PLATFORM_TOKEN> and the Connect + webhook endpoints on a small backend-for-frontend; the app talks only to your BFF.

IMPORTANT — the docs are authoritative. Read https://ewity-api.readme.io/docs/getting-started first and open the exact reference page linked for each endpoint before implementing it; don't guess schemas — confirm every field against the docs.

1) Connect (docs: https://ewity-api.readme.io/docs/implementing-connect): implement GET/POST {connect_url} exactly as documented so merchants enable your app from Ewity POS.
2) Catalogue: GET /stores (ref: https://ewity-api.readme.io/reference/liststores) then GET /locations/{id}/catalogue (ref: https://ewity-api.readme.io/reference/getfullcatalogue); cache for offline; refresh on the CatalogueUpdated webhook (docs: https://ewity-api.readme.io/docs/webhooks) via POST /locations/{id}/catalogue/lookup (ref: https://ewity-api.readme.io/reference/lookupcatalogue). Prices are tax-inclusive; buyable = available && !out_of_stock per location.
3) Order: POST /validate (ref: https://ewity-api.readme.io/reference/validatecart) — block on data.errors / lines[].error — then POST /orders (ref: https://ewity-api.readme.io/reference/createorder) { online_location_id, fulfilment_type, customer:{mobile,...}, lines:[{variant_id,unit_quantity,modifiers[]}] }.
4) Realtime: receive OrderStatusChanged/OrderNotification on your BFF (Bearer + X-Event, dedupe, 2xx fast — docs: https://ewity-api.readme.io/docs/webhooks) and fan out as push notifications; record payment with POST /orders/{id}/payment (ref: https://ewity-api.readme.io/reference/addorderpayment) once status is "accepted".

Deliver saved addresses, order history (GET /orders/{id} — ref: https://ewity-api.readme.io/reference/getorder), and push for every status change. Whenever a detail is unclear, consult the linked ReadMe reference rather than assuming.

Ready to build custom branded mobile app?

Create an app to get your API key, then follow the steps above.

Start building Read the full API docs