A documented restaurant API
Review /v1 operations for menus, orders, riders, reservations, staff and customers in the Swagger documentation at api.rosuii.com/docs. Confirm the operation you need before implementation.
Connection boundaries
Know what connects to Rosuii before planning your integration
Rosuii offers a key-authenticated REST API on Growth and Pro and eligible bKash/Nagad checkout on Pro. Public product facts are available to agents without restaurant credentials. Foodpanda/Pathao order tagging is manual, not a marketplace API connection. This page helps owners and developers scope the work before buying.
Growth REST APIPro merchant gatewaysPublic agent facts
Connection boundaries
Who this feature is for
For owners and developers checking a proposed connection
- Restaurants connecting their own eligible merchant account
- Developers working with authenticated restaurant APIs
- Owners separating direct orders from manually recorded marketplace orders
Operational benefits
What this changes in daily service
Separate payment responsibilities
Restaurant checkout can use eligible bKash/Nagad credentials on Pro. EPS is used to pay Rosuii subscription invoices, not as evidence of restaurant card checkout.
Public facts, private operations
Agents can read the public product catalog and pricing without a key. Restaurant business data belongs behind authenticated, tenant-scoped application services.
How it works
The workflow, step by step
1. Name the operation
Write down whether you need restaurant data, customer checkout or public product facts. Check the relevant plan and documented endpoint.
2. Protect credentials
Keep restaurant API keys and merchant secrets server-side. Never put them in browser scripts, public Markdown or a shared demo recording.
3. Test the real boundary
Use your own test restaurant and approved sandbox settings. Check failures, permissions and recorded order status before enabling a live connection.
What is included
- Key-authenticated /v1 REST API and Swagger documentation
- Public agent product/pricing API and discovery
- Eligible Pro bKash/Nagad checkout
- EPS subscription-invoice payments
- Manual marketplace order tagging presets
- Storefront custom-domain configuration
Frequently asked questions
Where are the API docs?
Restaurant REST API documentation is at https://api.rosuii.com/docs. The public agent OpenAPI document is https://api.rosuii.com/api/agent/v1/openapi.yaml. They serve different purposes and do not grant access to private restaurant data.
Does Pro import Foodpanda or Pathao orders?
No. Staff record and tag marketplace orders manually. There is no production marketplace API connection for order import, menu sync or settlement reconciliation.
Are EPS payment logos restaurant checkout methods?
No. EPS handles Rosuii subscription invoices. Restaurant checkout capabilities must be checked separately; bKash/Nagad gateways require Pro and eligible merchant credentials.
See this workflow in your restaurant
Start on the Free plan or open the demo, then choose a plan only when you need higher limits or connected modules.