Application registration

Every application that calls Enlitt is registered first, on the business dashboard at Apps → New application (/dashboard/business/apps), never through the SDK itself. Registration is what gives an application:

• an application identity shown to the end user on the authorization consent screen (name, icon, description, and the owning business's display name),
• an environment — test or live — which determines whether calls made under it spend real credit against a real user's account. A test application still spends real credit; there is no simulated or free mode, in either environment.
• the redirect URIs and allowed origins Enlitt's login and authorization flows are permitted to return to.

What registration does not do

Registering an application does not, by itself, produce anything an SDK call needs. There is no application ID or secret to copy into enlitt() calls at this step — the SDK never takes an application identifier as an argument. An application's identity, on Enlitt's side, is established by the credential that authenticates each request:

• a personal user's own login session, resolved through ambient middleware context (see Personal login), identifies which user a standard or premium call is on behalf of;
• a business's own API key (see API keys), scoped to one application, identifies which application and which business a business.info() reporting call is reading.

Registration and credential issuance are two separate steps: register the application first, then issue it a key with the scope that step actually needs.