Accessibility Agent3

Accessibility Checker4

Administration10

AI27

Announcements1

API Token7

Apps12

Authentication6

Browser Tree5

Bulk Upload1

Bundle16

Cache Management11

Categories10

Cluster Management5

Containers21

Content20

Content Analytics3

Content Delivery8

Content Import12

Content Report2

Content Type11

Content Type Field36

Data Integrity8

dotAuth15

Elasticsearch Content Search3

Environment11

Experiment18

File Assets5

Folders8

Forms1

getPagesContentTypes1

Health8

Internationalization14

JavaScript18

Job Queue14

Language2

License8

Maintenance26

Navigation2

Notifications5

OSGi Plugins15

Page18

Permissions11

Personalization4

Personas2

Portlets14

Publishing16

Relationships2

Roles19

Rules Engine26

SAML Authentication5

Search Index19

Site20

System10

System Configuration23

System Logging3

System Monitoring2

System Storage2

Tag (v1)10

Tags13

TailLog2

Template14

Templates18

Temporary Files2

Theme2

Usage1

Users13

Variants5

Web Assets9

Widgets1

Workflow57

Content Delivery

Changes to Check if a contentlet can be locked (deprecated)

put/api/content/canLock/{params}

Oct 30, 20264fd8e917d458 Revision changes
- breaking
  added the pattern .* to the path request parameter params
- info
  api operation id canLockContent removed and replaced with canLockContentLegacy
- info
  endpoint deprecated
- info
  added the non-success response with the status
- info
  added the non-success response with the status
- info
  added the non-success response with the status
- info
  added the success response with the status