Managing Oracle Learning Catalog Administration Profiles with REST APIs

A validated approach for creating profiles and maintaining individual contributors

Catalog Administration Profiles help organizations divide responsibility for Oracle Learning catalog content among authorized administrators. This article explains the capability, summarizes the learningCatalogProfiles REST resource, and documents a tested pattern for creating a profile and adding individual contributors. The examples use placeholders so they can be adapted safely to another environment.

The REST behavior described here was validated in an Oracle Learning Cloud 26C test environment on October 2, 2026. Oracle had not exposed the complete resource in its public REST reference at the time of testing (its part of 27A release notes), so implementers should review their own environment’s REST describe metadata and retest after quarterly updates.

Catalog Administration Profiles

A Catalog Administration Profile controls which learning administrators can manage designated catalog content. A profile defines its visibility and contributors, and learning items can then reference that profile. This supports decentralized catalog administration while preserving controlled access.

How organizations can use the capability

· Separate catalog-management responsibility by business unit, geography, training program, or another operating model.

· Allow named contributors to manage learning content associated with a profile.

· Use the Everyone visibility option when all catalog administrators may see the profile, while contributors retain the intended management responsibility.

· Maintain a stable profile number for integrations and learning-item associations after Oracle generates the number during creation.

Security remains part of the design

The REST API does not replace Oracle security configuration. The integration account still requires the applicable REST privilege, the Manage Catalog Administration Profile privilege, and appropriate data access. A successful payload in one environment does not prove that another integration account has the same authorization.

REST resource overview

Use the following base path, replacing the host with the target Fusion environment:

https://<fusion-host>/hcmRestApi/resources/11.13.18.05/learningCatalogProfiles

Understanding the describe metadata

The environment’s describe output identifies attributes, finders, child resources, supported actions, and lookup references. It is useful for discovering capabilities, but the working request remains the final validation. Two differences emerged during testing.

1. The describe output marked learningCatalogProfileNumber as input-required, but the working create request omitted it. Oracle generated the value using the OLC number sequence.

2. The describe text listed ORA_OPEN and ORA_PRIVATE for visibility, while the live profile and successful create request used ORA_EVERYONE for the Everyone option.

These differences matter. Treat describe metadata as environment-specific technical guidance, then validate the request in a nonproduction environment before including it in an integration.

The profile-status lookup can be inspected through the common lookup resource:

GET https://<fusion-host>/hcmRestApi/resources/11.13.18.05/commonLookupsLOV
    ?finder=LookupTypeFinder%3BLookupType%3DORA_WLF_LEARN_CAP_STATUS

The describe metadata did not expose a lookup resource for contributor source types. The value ORA_PERSON was obtained from an existing individual contributor and validated in successful create requests.

Create a Catalog Administration Profile

The create request can add the profile and its initial contributor criterion in one transaction. In the nested payload, contributorCriteria is a collection and must therefore be represented as an array.

Payload
POST https://<fusion-host>/hcmRestApi/resources/11.13.18.05/learningCatalogProfiles

Header
Content-Type: application/json
Accept: application/json
REST-Framework-Version: 4

Body
{
  "name": "<PROFILE_NAME>",
  "status": "ORA_ACTIVE",
  "visibility": "ORA_EVERYONE",
  "contributorCriteria": [
    {
      "sourceId": <PERSON_ID>,
      "sourceType": "ORA_PERSON"
    }
  ]
}

Important points for profile creation

· Omit learningCatalogProfileNumber. Oracle generated a number such as OLC482943 in the validated test.

· Use camel-case field names. Oracle treated PascalCase names as unknown and reported that name was null.

Get Ritwick Chatterjee’s stories in your inbox

Join Medium for free to get updates from this writer.

Remember me for faster sign in

· Represent contributorCriteria as an array, even when adding only one criterion.

· Use the Oracle person ID in sourceId. Do not substitute the employee or person number.

· Do not send creationDate, lastModifiedDate, createdByPersonId, or other system-generated audit values.

· A successful response returns HTTP 201 Created. Save the generated profile number and the self link from that response.

Find a profile by its generated profile number

Oracle returns a serialized hash key in the item self link. Do not build the item URL from an effective date and profile number. First query the collection by profile number, then reuse the links Oracle returns.

Payload
GET https://<fusion-host>/hcmRestApi/resources/11.13.18.05/learningCatalogProfiles
    ?finder=findByLearningCatalogProfileNumber%3BlearningCatalogProfileNumber%3D<PROFILE_NUMBER>

Header
Accept: application/json
REST-Framework-Version: 4

Confirm that the response count is one and that learningCatalogProfileNumber matches the requested value. Copy the self link or the contributorCriteria child link from the returned links array.

Add a person to an existing profile

Adding an individual contributor requires three verified values: the person’s Oracle person ID, the target profile number, and the target profile’s contributorCriteria child URL.

Step 1 Find the Oracle person ID

Use an approved HCM person-search API, secured report, or administrative page to resolve the employee’s person number to the Oracle person ID. The value required by contributorCriteria is the numeric person ID. Confirm the person’s name and person number before using the ID; names are not unique.

Step 2 Find the target profile and its child link

GET https://<fusion-host>/hcmRestApi/resources/11.13.18.05/learningCatalogProfiles
    ?finder=findByLearningCatalogProfileNumber%3BlearningCatalogProfileNumber%3D<PROFILE_NUMBER>

This request lists configured contributor criteria. Check whether a row already has sourceType ORA_PERSON and the intended sourceId before posting a new row. This prevents duplicate contributor criteria.

Step 3 Review current contributor criteria

Payload
GET <CONTRIBUTOR_CRITERIA_CHILD_URL>
Resposnse
{
  "items": [
    {
      "criteriaId": <CRITERIA_ID>,
      "sourceId": <PERSON_ID>,
      "sourceType": "ORA_PERSON",
      "sourceTypeMeaning": "Person",
      "sourceDisplayName": "<DISPLAY_NAME>",
      "sourceNumber": "<PERSON_NUMBER>"
    }
  ],
  "count": 1,
  "hasMore": false
}

Step 4 Add the new person

Payload
POST <CONTRIBUTOR_CRITERIA_CHILD_URL>
Header
Content-Type: application/json
Accept: application/json
REST-Framework-Version: 4
Body
{
  "sourceId": <PERSON_ID>,
  "sourceType": "ORA_PERSON"
}

The validated request returned HTTP 201 Created and generated a new criteriaId. Creating a child criterion does not require an Effective-Of header.

Important points to remember

· Use the versioned HCM REST base path, including /hcmRestApi/resources/11.13.18.05.

· Use the finder to locate a profile by its generated profile number.

· Always follow Oracle’s returned self and child links. Do not construct or shorten the serialized key.

· Use contributorCriteria to configure a contributor. contributorPersonList may be empty even when the UI shows a contributor because it represents resolved relationships after processing.

· Use POST on the child collection to add a criterion. Use PATCH only on an existing criterion item.

· Check for an existing sourceId and sourceType pair before adding another row.

· Treat person IDs and profile identifiers as sensitive implementation data. Do not publish real tenant URLs or employee identifiers.

· Retest after quarterly updates and compare the REST describe output with actual behavior in a nonproduction environment.

Summary

Oracle Learning Catalog Administration Profiles can be created and maintained through the learningCatalogProfiles REST resource. A profile can be created with an initial individual contributor by posting a nested contributorCriteria array. Oracle generates the profile number and supplies serialized links for subsequent operations. To add another contributor, find the profile by number, follow the returned contributorCriteria link, confirm the person ID, and post a new ORA_PERSON criterion.

The central implementation lesson is to rely on returned links and validated behavior. The describe metadata is valuable for discovering resource structure and lookup references, but it may not fully reflect working create requirements.