I’m working with the Banno API and specifically testing the Plugin Management API documented here:
https://jackhenry.dev/open-api-docs/admin-api/api-reference/v0/plugin-management/details/#/

So far, I can successfully manage custom plugin cards that we develop internally. These appear as expected both:

• In the Dashboard → Plugin Cards section

• Via API calls using organizationId and the /plugincards endpoints

However, the API seems to only expose custom applications/plugins that we create ourselves. Banno/Jack Henry–managed plugins, including built‑in Banno cards or Custom SSO configurations, do not appear in the list of manageable plugins via the API. Because of that:

• They cannot be retrieved through /plugincards

• They cannot be updated or configured via the Plugin Management API

What I’ve tested

• Queried the /organizations/{organizationId}/plugincardclients endpoint → Only custom internal plugins and external applications are returned.

• Queried /plugincards details directly by ID (when known) → Only our created plugin cards show up; Banno‑developed plugins (e.g., marketing cards, transactions, etc.) are not returned.

• Checked the Banno Dashboard under Plugin Cards and External Applications → I can see all available plugins/cards there and can toggle them on/off. But when I compare those entries to what the Plugin Management API returns, the API only includes our custom in‑house plugins, not the full set shown in the UI.

My question

Is there any supported way via the API to manage Banno‑provided plugins or Custom SSO entries?
Or are these intentionally excluded from the Plugin Management API and only configurable within the Banno Dashboard / by Jack Henry?

If there is a supported method, I’d appreciate guidance or a reference to the correct endpoint or documentation. I’ve searched through the JackHenry.dev site and haven’t found anything addressing this.