What You Should Do

If your team manages a custom integration with the Skilljar API, we recommend checking with your developer or IT resource to confirm that your API requests use pagination correctly (i.e., fetching data page by page rather than relying on a single large response).

To verify:

1. Check your API code or integration settings for parameters like `page` or `page_size`
2. Confirm that your integration loops through pages of results rather than trying to pull all data at once.
3. If you’re unsure how your integration handles pagination, ask your developer, IT team, or system integrator to review it for you.

FAQs

What’s changing?

Skilljar be adjusting the number of results returned per API request to improve performance and reliability.

• The default page size will remain 100 items per page; except those pages that previously returned up to 1000 results will now return 250 by default
• The maximum page size for any API request will be 1,000 (down from 10,000).

Will this affect my Skilljar Academy?

For the vast majority of customers, no action is required. If you use Skilljar’s API in a standard way — or only through built-in integrations — your data and reporting will continue to work as expected.

How do I know if my API integration is affected?

You may want to review your API setup if:

• You have a custom integration built by your internal team or a third party.
• You’re making direct API calls to export data or sync with another system.

In those cases, check whether your integration:

• Uses the `page` and `page_size` parameters.
• Loops through all pages of results until no more data is returned.

If your integration already does this, you’re all set.

Who should check this for me?

If you’re unsure, ask your developer, IT resource, or system integrator to confirm that your integration handles pagination correctly.

What happens if I don’t make any changes?

If your integration already paginates correctly, it will continue working normally — you may just see slightly smaller batches of results and a few more API calls overall. If your integration assumes it can pull large batches in a single request, it may start returning fewer results than expected after the update.

What is pagination and how does it work, conceptually?

Think of your data like a long list of students, courses, or enrollments. The API can only show a certain number of items at a time — like a “page” of results in a book.

• Page size: How many items are shown on one page. After the update, you can request up to 1,000 items per page.
• Multiple pages: If there are more items than fit on one page, the API gives you the first page and lets you ask for the next page, then the next, until all data is retrieved.
• What happens with your integration:
  • If your integration already asks for one page, then automatically asks for the next until done, you don’t need to change anything.
  • If your integration tries to get all items in one request, it may now get fewer results than expected, and your developer or IT team would need to adjust it.
• What you can do:

• Simply check with your developer, IT team, or whoever manages your API integration. Ask them to confirm the integration “reads all pages” instead of assuming one request returns everything.

Why is Skilljar making this change?

This update improves API consistency, reduces response time for all customers, and helps ensure stable, predictable performance.

Will this API change impact the data connector or SSO?
No, this API change will not impact the data connector or SSO.