Outbound Apps: add a way to list AND read app-library templates (metadata/config) — companion to createApplicationByTemplate #744

[tarracharan-glitch]

Thanks for shipping createApplicationByTemplate (#744) — it works great. But
there's a discoverability gap: it takes a templateId, yet there's no way to
list which template IDs exist.

• The console has the outbound app-library picker, so the catalog is known
  server-side.
• SDK: management.outboundApplication has no listTemplates /
  getTemplates method (2.9.0).
• REST: I probed the obvious paths and all 404 —
  /v1/mgmt/outbound/app/templates, /v1/mgmt/outbound/templates,
  /v1/mgmt/outbound/apptemplates, … (E011006 "endpoint not found").

So a caller has to hardcode or guess slugs. I only found the ones we use by
trial-and-error against the create endpoint (hubspot, google, slack,
github, google-calendar all work — but nothing tells you that up front).

Use case

We register Outbound Apps programmatically from an internal admin UI. We want to
show admins a template picker populated from Descope's library, instead of a
free-text "type the slug" field or a hardcoded list that drifts from your
catalog.

Proposed

A management method (and underlying REST endpoint) to list templates, e.g.:

const { templates } = await client.management.outboundApplication.listTemplates();
// → [{ id: "hubspot", name: "HubSpot", logo?, defaultScopes?, ... }, ...]

Even an id+name list would be enough to build a picker.

Environment

• @descope/node-sdk@2.9.0
• Related: feat: create outbound app from template #744 (createApplicationByTemplate) — this is its natural companion.

[tarracharan-glitch]

Expanding the ask: beyond listing templates (id + name for a picker), we also need to read a template's full metadata/config so a UI can prefill a registration form when a template is selected — name, description, logo, authorizationUrl, tokenUrl, defaultScopes, pkce.

Today the only way to read that is a hack: createApplicationByTemplate → loadApplication → deleteApplication (create a throwaway app just to read it back, then delete). That's literally how we captured our hardcoded template list — there's no side-effect-free way to read a template's config.

Proposed, alongside the list method:

const tpl = await client.management.outboundApplication.getTemplate("hubspot");
// → { id, name, description, logo, authorizationUrl, tokenUrl, defaultScopes, pkce, ... }

…or have listTemplates() return full metadata per template, so one call can both populate the picker and prefill the form.

Environment: @descope/node-sdk@2.9.0.