API changes in the September 2026 release of Adobe Learning Manager

API for checking catalog access for learning objects

Determine whether the current learner has direct catalog access to one or more learning objects, independent of whether the learner reached that content through a learning path or certification.

Purpose of the API

When a learner opens a learning path or certification, they can browse the individual courses inside it, even if a specific course isn’t directly assigned to them through a catalog. This supports content discovery: learners can explore what a learning path contains before deciding whether to pursue it.

However, being able to view a course this way should not automatically mean the learner can enroll in it. Enrollment should depend on whether the learner has direct catalog access to that specific course, not just indirect access through a containing learning path.

This API lets you check, for a given learner, whether one or more learning objects are directly accessible through a catalog assigned to them. Use the result to control enrollment-related UI, for example, showing an Enroll option only when direct catalog access is confirmed, while keeping the course page itself viewable in both cases.

Endpoint

GET /primeapi/v2/learningObjects/isMemberOfVisibleCatalogs

Query parameters

Example request

GET /primeapi/v2/learningObjects/isMemberOfVisibleCatalogs?ids=course%3A2400159%2Ccourse%3A2400160%2Ccourse%3A2400161%2Ccourse%3A2400162
Accept: application/vnd.api+json
Authorization: oauth <access-token>

Example response - 200 OK

{
  "course:2400162": false,
  "course:2400161": false,
  "course:2400160": true,
  "course:2400159": true
}

Response codes

Example error response

{
  "status": "BAD_REQUEST",
  "title": "Bad request. Check url, params and headers",
  "source": {
    "info": "Either LO id is blank or not as per public api specification"
  }
}

Use this API in your integration

A common use case is a course page that a learner reaches by navigating from a learning path. You want the course page itself to remain accessible for discovery, while showing the Enroll action only if the learner has direct catalog access to that course.

Job API for Admin Audit Trail Report apiaudittrailreport

Purpose of the API

The Administrator Audit Trail Report lists the configuration changes made to an
Adobe Learning Manager account. For example, changes to Basics, Integrations, or
Advanced account settings over a given date range. Generating the Audit Trail report requires querying and aggregating configuration change records across the requested date range and setting types. Depending on the size of the range and the volume of changes, this can exceed the time limits of a synchronous HTTP request, which risks client or gateway timeouts.

To avoid this, the report is generated asynchronously through the generic Job API:

Base URL and conventions

IDs

The job id returned when a job is created is an opaque string (for example,
4593). Always pass back the exact id value you received from the create
response when polling for status. Never construct or parse it.

Authentication scopes

Each endpoint requires an OAuth token carrying the following scope, and the
calling user must hold the account admin role:

Requests made by a caller who does not hold ROLE_ADMIN on the account are
rejected; see Error handling

Endpoints

Create an Audit Trail Report job

POST /primeapi/v2/jobs

Creates an asynchronous job that generates a Config Change Audit Trail report
for the given date range and setting types. The response returns immediately
with a job resource in QUEUED state; the report itself is produced in the
background.

Scope: admin:write

Sample request body

{
  "data": {
    "type": "job",
    "attributes": {
      "jobType": "generateConfigChangeAuditReport",
      "payload": {
        "fromDate": "2026-09-15T00:00:00.000+05:30",
        "toDate": "2026-09-23T23:59:59.000+05:30",
        "settingTypes": ["Basics", "Integrations", "Advanced"]
      }
    }
  }
}

Response: 202 Created. The response body is the job resource in its initial
QUEUED state.

{
  "data": {
    "id": "4593",
    "type": "job",
    "attributes": {
      "jobType": "generateConfigChangeAuditReport",
      "status": "QUEUED",
      "dateCreated": "2026-09-23T18:12:04.000+05:30"
    }
  }
}

Get the status of an Audit Trail Report job

GET /primeapi/v2/jobs/{id}

Returns the current status of a previously created job. While the job is
still running, attributes.status is QUEUED or IN_PROGRESS and
attributes.result is absent. Once the job finishes, attributes.status is
either COMPLETED, with the report location in attributes.result, or
FAILED, with failure details in attributes.error.

Scope: admin:read

Sample response while the job is still running

{
  "data": {
    "id": "4593",
    "type": "job",
    "attributes": {
      "jobType": "generateConfigChangeAuditReport",
      "status": "IN_PROGRESS",
      "dateCreated": "2026-09-23T18:12:04.000+05:30"
    }
  }
}

Sample response once the job has completed

{
  "data": {
    "id": "4593",
    "type": "job",
    "attributes": {
      "jobType": "generateConfigChangeAuditReport",
      "status": "COMPLETED",
      "dateCreated": "2026-09-23T18:12:04.000+05:30",
      "dateCompleted": "2026-09-23T18:12:41.000+05:30",
      "result": {
        "downloadUrl": "https://learningmanager.adobe.com/primeapi/v2/jobs/4593/download",
        "expiresAt": "2026-09-24T18:12:41.000+05:30"
      }
    }
  }
}

Resource schema

Job attributes

Payload (embedded, inside the create request)

Result (embedded, inside a completed job)

Error handling audit-trail-report-error-handling

The following codes apply to these endpoints:

Example error response

{
  "status": "BAD_REQUEST",
  "title": "Bad request. Check url, params and headers",
  "source": {
    "info": "toDate must be on or after fromDate"
  }
}

Use this API in your integration

A common use case is an admin-facing “Download audit trail” action in the
account settings screen.