Environments & Base URLs

API base URL

The Platform API is reached at the tenant-facing host, under /api/trpc:

https://manage.inklura.fr/api/trpc/<router>.<procedure>

manage.inklura.fr is a single, truly multi-tenant endpoint: your tenant travels in your Bearer token, so the same URL serves every tenant — the server reads tenantId/siteId straight from the signed token. A given tenant may also reach the API through its own domain, where the Host identifies the tenant for cookie-session requests. See Tenancy.

Environment	API base
Production	`https://manage.inklura.fr/api/trpc`
Local dev (company-manager)	`http://localhost:3060/api/trpc`

Note

There is an internal, loopback-only high-throughput copy of the same router (the "lean" server) that the console uses at http://127.0.0.1:4000/api/trpc. It is not reachable off-host and is not a public endpoint — always call the public host from your own code.

The `/api/v1` REST bridge

A REST/OpenAPI bridge exists at /api/v1/<router>/<procedure>, generated from the tRPC routers. Today it is only partially wired — a procedure appears under /api/v1 only if it has been explicitly annotated with OpenAPI metadata, which currently covers a small number of users/products operations. Treat REST as experimental; for anything beyond those, use tRPC. See REST Endpoints.

Platform apps

Inklura is a family of apps sharing one login. The developer-relevant ones:

App	Host	What it is
Console	`manage.inklura.fr`	The admin app + the Platform API
SMS Designer	`smsdesigner.inklura.fr`	SMS campaign composer & reports
SEO	`seo.inklura.fr`	SEO audits and client reports
Mail	`mail.inklura.fr`	Email/MJML composer
Wiki	`wiki.inklura.fr`	Gated guide library
Identity provider	`auth.1clic.pro`	OIDC / SSO

Every *.inklura.fr host resolves to the same edge and shares the session cookie, so a user who logs in once is authenticated across all of them. See SSO.

TLS & DNS

*.inklura.fr resolves to the platform edge. Each host is served over HTTPS with a per-domain certificate that the platform provisions and renews automatically (ACME HTTP-01). Adding a new subdomain does not require any DNS change on your side — see Provisioning Subdomains.