Public search visibility is controlled from the Mutasib dashboard. This guide focuses on the endpoints that read from the public marketplace.
Public search endpoints
All of the endpoints in this section are unauthenticated — no token required. They are intended for customer-facing surfaces such as storefronts, mobile apps, or embed widgets.Search across all shops
Use the main search endpoint to find products matching a query, optionally filtered by category, price range, or a specific shop.q returns all visible products (useful for browsing by category).
List all visible shops
Filter shops by category using the optionalcategory query parameter, or omit it to return every visible shop. The response is paginated.
Get a single shop’s details
List a shop’s public products
Usesearch to match against product names and category_id to filter by category — both parameters are optional.
is_public: true.
Nearby shop discovery
Customers can search for shops within a geographic radius using the nearby endpoint. This is useful for local discovery features in mobile apps or maps.
The response returns shops sorted by
distance_km in ascending order, so the closest shop appears first.
For your shop to appear in nearby results, it must have its latitude and longitude fields set.
Setting your shop’s location
Update your shop’s coordinates with aPATCH request. You only need to do this once (or whenever your shop moves).
Tips for better search visibility
Tips for better search visibility
- Write descriptive product names. The search index matches against product names and descriptions, so clear names like “Full-Fat Labneh 500g” rank better than “LBN-500”.
- Use consistent categories. Products grouped under recognised categories (e.g.
dairy,bakery,beverages) benefit from category-filtered searches. - Keep prices up to date. Customers often filter by price range — stale prices lead to confusion and abandoned visits.
- Add your location. Even if you don’t have a delivery service, appearing in nearby searches drives walk-in traffic.