No unconfirmed endpoint publication
Bundle IDs may still appear in license/configuration metadata, but the legacy utility endpoint requires separate contract confirmation.
The current V1.2 TOC does not publish a standalone Bundle ID endpoint; does not present the legacy endpoint as current.
Bundle IDs may still appear in license/configuration metadata, but the legacy utility endpoint requires separate contract confirmation.
Not publicly specified
The baseline ZIP does not contain an authoritative contract sufficient to implement this operation.
authoritative endpoint/schema and platform binding rules
Do not invent endpoints, fields, retry policies or sample JSON.
Developers require the partner/API specification before production integration.