Enterprise Apps and API Users in Momentus Connect

Momentus Connect and Applications require two special types of Enterprise API users:

• MOCO-SERV: The overall Momentus Connect API user. This is used for Enterprise calls to internal collaboration APIs.
• App-specific API users: Each Momentus Connect application that requires V1 API calls has a dedicated API user automatically created for that app instance on approval. 

These API users are hidden from customers and are only visible to Enterprise support users. These API users do not require any kind of API licensing or purchase.

For security reasons, the MOCO-SERV user must be created manually by support users. The credentials for this API user must be added during the first app approval; once the MOCO-SERV API user has been added to Connect during the first app approval, it does not need to be done again. 

Before creating the user, go to Enterprise API Users and search for “MOCO-SERV”. If found, copy the credentials (ID, secret and key) to the Momentus Connect API User prompt. If not, proceed with creating the MOCO-SERV user.

Create the MOCO-SERV API user following the instructions in API Users using these settings:

• Display Name: Momentus Connect
• Description: Internal Momentus Connect API User
• Organization: Use any organization.
• ID: MOCO-SERV
• Enforce Access Privileges: Unchecked
• Allow Proxy User: Unchecked
• Retire: Unchecked
• Internal: Checked
• License Special Access: Checked

If customer is not licensed for the API, enlist the help of the Licensing team:

1. Send a new email to [e-mail]:
   • Include the environment URL and serial number.
   • Request a temporary add of the Basic API module.
2. The Licensing Team (Sara N and Hope) will add the license and your ticket will be closed with public note to requester and followers, so you receive a notification.
3. Once you've added the API user, let the licensing team know to remove the license.

API Users when copying Prod to Test

When copying a production database to a test environment, both MOCO-SERV and App-specific API users may become invalid. When this happens, active integrations stop working and reconfiguration is required. Contact the Platform Team [who/how?] for assistance. The Platform team is working on a long-term solution to address this.