Plan
Take a few minutes to declare your application properly on the platform.
Academy path
1 · Plan
URL, DNS, profile — register in the Console.
2 · Lab
Try the reference web and mobile apps.
3 · Understand
Embed styles, sign-in flow, server checks.
4 · Implement
Starters, server routes, page stack, CSS.
Step-by-step checklist
-
Start with your application URL.
Decide the public address of your web application — for example
https://shop.example.com. This URL is stored in the Console and used for embed verification and links. -
Make sure you control the DNS zone of that URL.
This is mandatory. Kie.la verifies that you own the domain by asking you to publish a TXT record (
kpf.<uuid>.<domain>) in DNS. Without access to the zone (registrar, Cloudflare, Route 53, etc.), you cannot complete registration of the sign-in prompt securely. Full reference: DNS. -
Choose a unique application identifier (
name). 6–24 characters, must start with a letter, letters and digits only, case-sensitive (e.g.MyShop). You can check availability in the Console before the final registration step — two applications cannot share the same name. -
Choose public or private visibility.
- Public — listed in the platform catalogue; any Kie.la user can sign in (typical B2C).
- Private — not open to everyone; access is restricted to users you grant a role for (typical B2B / internal tools). Billing treats private apps differently.
What you should have before coding
- A reachable HTTPS URL and DNS control over its domain.
- Clear choices for name and visibility.
Try the lab apps before you integrate your own product.