Integrations Guide

App Registrations Reference

Defines the field schema, lifecycle, and expiration-notification timing for App registrations under Admin Center > Site Settings > IAM > App registrations.

Fields

Field Type Values Default Description
Name String Free text — Identifier shown in the registrations grid and in API client alert banners. Required.
Expiration date Date Calendar date — Date after which the registration stops authenticating. Required. Drives the expiration notifications and the persistent red banner.
Enabled Boolean Yes / No Yes When No, the registration cannot authenticate even if not yet expired.
Client ID String System-generated, 20 characters Issued at creation Public identifier of the registration. Visible in the grid and on the detail view.
Client secret String System-generated Issued at creation Secret credential the client presents to the API. Shown only at the moment of creation.
Registration date Date System-set Set at creation Read-only column in the grid.
Last used Date System-set Updated by API traffic Read-only column in the grid.
Expires String In N days / Expired Derived Read-only column in the grid, derived from Expiration date.

Grid columns

The App registrations grid shows: Name (link, sorted), Client ID, Registration date, Enabled, Last used, Expires.

Lifecycle states

State Trigger What you see
Active Created with a future Expiration date Registration authenticates normally.
Expiring (30 days) 30 days before Expiration date Administrative notification template App registration expires in 30 days fires; banner surfaces per template configuration.
Expiring (7 days) 7 days before Expiration date Administrative notification template App registration expires in 7 days fires.
Expired Expiration timestamp passed Administrative notification template App registration has expired fires; persistent red API client alert banner appears at the top of every page; Expires column reads Expired. Authentication stops working.
Disabled Administrator toggles Enabled off Registration cannot authenticate even before its Expiration date.

Expiration notification timing

Expiration drives the Administrative notification category. Templates fire at three points relative to the Expiration date:

  • 30 days before expiration — App registration expires in 30 days.
  • 7 days before expiration — App registration expires in 7 days.
  • At and after expiration — App registration has expired. Expired registrations also surface as a persistent red API client alert banner on every page until the registration is renewed.

You manage the templates under Admin Center > Site Settings > Notifications > Notification templates and the per-user delivery under Admin Center > Site Settings > Notifications > Subscriptions.

Constraints

  • The Client secret is generated by the system and displayed exactly once, at the time of registration creation. The stored secret is write-only — there is no API or UI path to reveal it after the initial display. If lost, the registration must be rotated.
  • Each App registration is scoped to a single site. Cross-site access requires a separate registration per site.
  • An expired registration produces a persistent red banner per registration. With multiple expired registrations, the banners stack at the top of the dashboard and pages.