Since you have mentioned "enterprise", I am assuming that you are referring to Alfresco Process Service (formerly known as Alfresco Activiti Enterprise). The REST API root of the enterprise product is "activiti-app/api/".

If you have an enterprise implementation, the usage of these APIs depends on your requirement.

For example: Implementation of identity is different in enterprise and hence the users and groups are stored differently. For the same reason, "activiti-app/api/identity" may not return the results you need. In this case, you will have to use an API under /enterprise.

Another example: if you want to get a list of executions, you will want to use the core engine API "runtime/executions".

I also noticed that you have "/app" in your question. Please note that those APIs are there mainly for the OOTB activiti-app UI use and is secured using the cookie approach based on the logged-in user, device etc. They are classified as "Internal" APIs and are subject to change in newer versions.

Since you have mentioned "enterprise", I am assuming that you are referring to Alfresco Process Service (formerly known as Alfresco Activiti Enterprise). The REST API root of the enterprise product is "activiti-app/api/".

If you have an enterprise implementation, the usage of these APIs depends on your requirement.

For example: Implementation of identity is different in enterprise and hence the users and groups are stored differently. For the same reason, "activiti-app/api/identity" may not return the results you need. In this case, you will have to use an API under /enterprise.

Another example: if you want to get a list of executions, you will want to use the core engine API "runtime/executions".

I also noticed that you have "/app" in your question. Please note that those APIs are there mainly for the OOTB activiti-app UI use and is secured using the cookie approach based on the logged-in user, device etc. They are classified as "Internal" APIs and are subject to change in newer versions.

/app - Queries only intended to be available to the internal functions of the Activiti.

/api - Queries intended to be open and available as REST endpoints for the user to hit.

/runtime - Queries for runtime data.

/history - Queries for historic data.

/repository - Queries pointing to the stored data pertaining to models/tasks/process-instances, etc. These URLs are typically returned in the 'contentURL' or 'url' portion of a successful response body.

/enterprise - Queries made available in a valid instance of Activiti enterprise.

Adding a little more colour commentary.The latest version of Alfresco process Services powered by Activiti (a mouthful for sure) includes Swagger documentation and test utilities over the /enterprise API.