Tenancy and request scope
Every site is a separate tenant. Its data, users, and apps are stored apart from every other site's, and a request can only reach the site it was sent to.
How a request finds its site and app#
- The address selects the site. Send requests to your site's address,
TARUVI_SITE_URL. TaruviBase uses it to route the request to that site's data. - The app slug selects the app. App-scoped routes include the app slug in
the path, for example
/api/apps/APP_SLUG/datatables/. The SDKs add it for you from theappSlugorapp_slugyou configure. - The credential identifies the caller. TaruviBase checks that the caller belongs to the site and is allowed to perform the action. See Authentication and authorization.
Copy TARUVI_SITE_URL, TARUVI_APP_SLUG, and any API key from the same app's
Settings → Connect page. An API key issued on one site doesn't work on
another.
Site addresses#
A site is reachable at its own domain, which the Console shows as
TARUVI_SITE_URL. TaruviBase also accepts the path-style address
https://api.taruvi.cloud/sites/SITE_SLUG, which routes to the same site.
Use one form consistently within an application.
Keep environments apart#
Use separate sites for development and production. Because each site has its own users, data, and API keys, work on a development site never touches production data. Promote changes by recreating them on the production site or by exporting and importing the app.