MOCO + API

Here you will find the MOCO API documentation for developers to connect tools and systems:

An API key is required to connect systems. 

In the user profile (click on the profile picture at the top right) > "Integrations", you can access your personal key. This allows access to data according to your personal access rights.

This MOCO API key is needed, for example, to activate the browser extension (tracking time on external tasks and quick browser access).

In addition to personal API keys, you can alternatively or additionally create up to three account API keys (settings under Extensions > API & Webhooks > API Keys).

You have the following 4 options for your MOCO account settings:
a) Use only personal API keys
b) Use only account API keys
c) Use both personal and account API keys
d) Completely disable API access

Custom fields can be declared as "API-only editable" and then populated via a script with IDs from external systems.
This prevents users from accidentally overwriting them. When two (or more systems) need to be kept in sync, this eliminates the need to maintain mapping on the external system.

MOCO also offers webhooks. Webhooks enable event-based communication between two applications via the API.
»  More about Webhooks in MOCO

Automations via API can also be implemented with tools like n8n or Make. Examples of n8n by Skripfabrik

»  How we optimally complement MOCO – Tools, Slack Commands, Chatbots