26.4

Decommissioning legacy user authentication ingestion APIs

Our user authentication ingestion APIs are being updated to a newer, more reliable set of endpoints. This change helps keep your integrations more secure, stable, and easier to maintain over time.

What is changing

For customers who previously integrated with the legacy ingestion APIs, the following endpoints are changing. In the following examples, the actual host names are masked for security and may differ in your environment.

Base host change (applies to all endpoints): https://<legacy-host>.nspl.powerschool.com -> https://<new-api-host>.contentnav.powerschool.com

1. Token generation

   • Old URL path

     • /api/v1/auth/oauth/token

   • New URL path

     • /oauth2/token

2. Material ingestion

   • Old URL path

     • /api/content/v2/ingest

   • New URL path

     • /ingestion/material

   • Additional behavior

     • Invalid or expired tokens now return a standardized “unauthorized” error message.

     • Thumbnail and other URLs you send must start with http:// or https://.

3. Check ingestion status

   • Old URL path

     • /api/content/v2/{requestId}/details

   • New URL path

     • /ingestion/{requestId}/details

What this means for you

You will need to update your integrations to use the new host and paths.

Security enhancements

Addressed issues identified during internal security assessments to further strengthen ContentNav’s stability and overall security.

Streamlined Search experience:
Removal of Advertisement level filter

The Advertisement level filter has been removed from the Admin portal and ContentNav search. This simplifies your search and administration experience by reducing clutter and focusing on filters that districts actually rely on.

API credentials now managed in Ingestion Tools

API credential management has been simplified for ContentNav partners.

• The old Client ID and Secret section has been removed from the Partner Registry in the admin portal.

• Client credentials are now managed directly in the Ingestion experience via a new credentials popup.

• A message in the Technical client details area guides users to the new location: Client ID and Secret are now managed under Ingestion Tools → API → View Client ID/Secret.