The same operation id is listed for two different endpoints. See below:
|
operationId: patchPotentialRole |
|
operationId: patchPotentialRole |
Because of this, a doc page is only generated for the /role-mining-sessions/{sessionId}/potential-role-summaries/{potentialRoleId} endpoint and the doc page for /role-mining-potential-roles/{potentialRoleId} is ignored/overwritten. As you can see, developer.sailpoint.com does show menu elements for both pages, but they go to the same destination URL (https://developer.sailpoint.com/docs/api/v2025/patch-potential-role/):

The same operation id is listed for two different endpoints. See below:
developer.sailpoint.com/static/api-specs/idn/v2025/paths/role-mining-potential-role.yaml
Line 45 in 28196ef
developer.sailpoint.com/static/api-specs/idn/v2025/paths/role-mining-session-potential-role-summary.yaml
Line 51 in 28196ef
Because of this, a doc page is only generated for the /role-mining-sessions/{sessionId}/potential-role-summaries/{potentialRoleId} endpoint and the doc page for /role-mining-potential-roles/{potentialRoleId} is ignored/overwritten. As you can see, developer.sailpoint.com does show menu elements for both pages, but they go to the same destination URL (https://developer.sailpoint.com/docs/api/v2025/patch-potential-role/):