NAMES LEGAL for developers#
Build on NAMES LEGAL from your own application: read and write the content of a site, sell NAMES LEGAL to your users without them leaving your product, and keep their site filled with the data you already hold.
Three ways to integrate#
| You want to… | Use | Who sets it up |
|---|---|---|
| Read or write the content of one site (team, services, news…) from code | Site API | The site owner creates an API key in their console |
| Let your users buy a NAMES LEGAL site inside your application | Embedded purchase | NAMES LEGAL creates a sales channel for you; you paste one line |
| Fill and update a site from your own data (spreadsheet or API) | Data connector | The site owner connects your API in their console; you expose a feed |
All three can be combined. A typical platform integration looks like this:
- Your user clicks Create my website in your application: the embedded purchase frame opens, they choose a plan and pay.
- When the site is ready, your server receives a signed
site.readywebhook with the site address and your own reference for that user. - The site owner connects your application as a data source in their console. If your API follows the NAMES LEGAL feed format, every collection is linked automatically: teachers become the team, courses become services, news become blog posts.
- From then on, the site updates itself — every hour, every day, or instantly when you call its webhook address.
Key facts#
- Every site is independent. Each NAMES LEGAL site has its own address (
https://<site>.names.legalor its own domain), its own data and its own API keys. There is no global API that reaches every site. - Billing stays with NAMES LEGAL. A user who buys through your application becomes a NAMES LEGAL customer, billed by NAMES LEGAL. You never handle payments or card data.
- White-label by design. Visitors of a site never see NAMES LEGAL branding coming from these integrations.
- Six languages. The platform, the purchase frame and the content model support English, French, German, Italian, Spanish and Portuguese.
Conventions used in this documentation#
<site>is the address of one NAMES LEGAL site, for examplehttps://ecolehorizon.names.legal.- Dates follow ISO 8601:
2026-09-24or2026-09-24T14:02:11+02:00. - All requests and responses use UTF-8 JSON unless stated otherwise.