Developer account
A developer account lets you build a LexOpti integration on your own: once LexOpti approves your access, you register your applications, try them in sandboxes, and ask for production access when they are ready. LexOpti reviews twice: each developer before they start, and each integration before it acts for a real organization (two reviews).
Account types
Section titled “Account types”LexOpti has two kinds of accounts. The server sets the type when the account is created, and nobody can change it afterwards.
| Professional account | Developer account | |
|---|---|---|
| Who | a member of a regulated organization (a law firm, a notarial office, an accounting firm, an estate agency…) | the developer of a partner integration |
| Organizations | its real organizations, and the sandboxes it is invited to | sandboxes only, never a real organization |
| Console | the LexOpti app | the developer console, plus the app inside its sandboxes |
The two are separate identities. If you already use LexOpti as a professional, create your developer account with another e-mail address: an address of one type is refused by the other. Each type also has its own sign-in: a developer account signs in from LexOpti Developers (/developer/login), a professional account from the app’s sign-in page (/login). Once your code is verified, each page sends an account of the other type to its own, with its e-mail address, where you request a new code.
Two reviews
Section titled “Two reviews”| Review | When | What LexOpti looks at | Answer |
|---|---|---|---|
| Access review | when you request your developer account | who you are and why: your company, its website, the planned integration | usually within one business day, by e-mail |
| Production review | when your integration is ready, from its application’s Production access | its readiness and the partner agreement: the company’s SIREN, the production redirect URIs, the security and personal data contacts, the API terms | usually within one business day, by e-mail |
Between the two, you build freely in your sandboxes. A partner LexOpti has already chosen skips the first review with an invitation (invited by LexOpti); the production review is the same for everyone.
Request a developer account
Section titled “Request a developer account”- Open Create a developer account (also at the top of every page) and enter your first name, last name and e-mail address and your company. Its website and a short description of the planned integration (what your software does, for which professionals) are optional, but help the review. Disposable addresses are refused.
- Enter the six-digit code LexOpti e-mails you: it verifies your address and signs you in. Later sign-ins use the same code by e-mail, from the LexOpti Developers sign-in (Sign in, at the top of every page), which opens the console.
- The LexOpti team reviews your request, usually within one business day. Until it is approved, the developer console shows its state and creates neither an application nor a sandbox. You receive the decision by e-mail; after a refusal, the console shows its reason and lets you send a new request.
- Once your access is approved, on your first visit the developer console opens the creation of your test application by itself: give it its exact redirect URIs. LexOpti never invents one, since the authorization codes would go to a host you do not own; your test application and its sandbox exist as soon as you give them. LexOpti creates its confidential OAuth client and its first sandbox at once, and shows its client secret once: keep it in your server’s secret store. For a mobile or desktop app, choose the native type: a public client, without a secret (mobile and native apps).
A team holds three applications at most, and each application five sandboxes at most. Account creations are limited per IP address and per mailbox: the aliases of one mailbox (name+tag@, and the dots of a Gmail address) are one developer account.
Invited by LexOpti
Section titled “Invited by LexOpti”When LexOpti has already chosen to work with you, the team sends you an invitation instead: an e-mail to your address with a personal link to the LexOpti Developers sign-in. Sign in with that same address: the code LexOpti e-mails you verifies it, and your developer access is approved at once, with no request to send and no wait. If the address had no account yet, the invitation prepared one. The console then opens the creation of your first application, as after an approved request, and your team is named after the company of the invitation.
The link works once, for 14 days, and for the invited address only. Signed in with another address, the console says so and approves nothing; an expired, used or withdrawn link says it no longer works. In every case you may still send a normal access request, or ask the team for a new invitation. Your applications go through the same production review as any other.
The developer console
Section titled “The developer console”For each application, the console shows and lets you change:
- its client id, its embedded UI id and, for a web application, its client secret, rotated with a 24-hour overlap or at once after a leak;
- its exact redirect URIs and the origins allowed to embed its components, checked as the server checks them: changed at once while the application is in its sandboxes, sent for review once it is in production (the LexOpti team applies the reviewed values, as for the production access);
- its sandboxes, which you open in LexOpti or manage from Manage sandboxes;
- the webhook endpoints your server registered in its sandboxes, with a test delivery;
- the embedded sessions of the last 24 hours in its sandboxes: when your server asked for one, for which member and page, and whether the iframe opened it;
- its production access.
Logs and webhooks
Section titled “Logs and webhooks”Two more tabs of each application show its traffic, in its sandboxes and, once approved, in the real organizations it works for, never another application’s.
| Tab | Shows | Filters |
|---|---|---|
| Logs | every /v1 request of the last 30 days made with one of its tokens: method, path, HTTP status, the problem’s code, duration, organization, sandbox or production, the caller’s network, date, and its Request-Id |
result (succeeded, failed), method, organization, part of the path, dates, an exact Request-Id |
| Webhooks | its endpoints in every organization, and each endpoint’s deliveries of the last 30 days: event type, status, attempts, the last answer’s HTTP status and duration; a delivery’s detail shows the body sent and every attempt, and Replay sends it again with the same webhook-id |
status, event type |
What the log keeps is chosen so it never holds what a request carried: no header (so no Authorization, no token), no query string, no request or response body, the caller’s address cut to its network (/24 for IPv4, /48 for IPv6). Entries are written after the answer, never slowing it, and deleted after 30 days. A request refused before its token is verified (missing or invalid token, 401) is not logged, having no application to show it to; past the rate limit, only the first 429 of each one-minute window is logged, not every refusal. A replay is refused at once while your application has no access to the organization or the endpoint is disabled. A replayed delivery leaves only while your application still has access to the organization, as every delivery; replays are limited to 30 every 10 minutes. Quote a Request-Id to LexOpti support: the team sees the same screens, read only.
Confined to its sandboxes
Section titled “Confined to its sandboxes”Until its production access is approved, an application acts for its own sandboxes only. The consent page offers no other organization, and /v1, the embedded components and the MCP server refuse any token for another organization, whatever its expiry. Sandboxes consult no real source, bill nothing and schedule no vigilance.
Request production access
Section titled “Request production access”When your integration is ready, send the request from the application’s Production access section. It asks for:
- your company and its SIREN, and its website;
- the use case: what the integration does, for which professionals, and the data it keeps;
- the exact production redirect URIs, five at most;
- a security contact and a personal data contact;
- your acceptance of the API terms, whose dated version is recorded with the request.
The form starts from your access request: your company, its website and the use case are prefilled, for you to check and complete; the SIREN, the production redirect URIs, the contacts and the terms are this review’s own.
One request per application is under review at a time. The LexOpti team approves or declines it, with a reason, usually within one business day, and you receive the decision by e-mail. An approval lifts the confinement and adds the production redirect URIs to the application; a declined application stays in its sandboxes, and you may send a new request. A partner contract, when there is one, is signed outside the console.
Your team
Section titled “Your team”A software vendor is a company, not one person: the developer console works like an office. The approval of your access opens your team, named after the company of your request, with you as its owner. From Team, an owner invites colleagues by e-mail, with a role (member, or owner so they invite in turn): the invitee receives an e-mail, signs in with that address (a developer account is created for them if they have none) and joins the team at their first code, without asking LexOpti anything. They reach the same applications at once (credentials, redirect URIs, origins, webhooks, logs, production access requests, partner statement) and the same sandboxes, which they own too, and can pick the team’s sandbox at consent.
An invitation is valid for seven days; a team holds ten seats at most (members and pending invitations) and three applications at most, however many members it has. A developer account belongs to one team only: a colleague already in theirs does not join yours. Renaming, resetting and deleting a sandbox stay with whoever created it.
Your data
Section titled “Your data”A developer account keeps your e-mail address, your name and what your access request says (your company, and its website and the planned integration if you gave them). An account without a sign-in for two years is deleted with its applications and sandboxes, after a warning e-mailed 30 days before; signing in once keeps it. An account with an application approved for production is never deleted automatically: real organizations may depend on it, and the LexOpti team decides with you. Production access requests, with their SIREN, terms version and decision, are kept after the account goes. To exercise your rights, write to contact@lexopti.com.