MOCO + API

Here you’ll find the MOCO API documentation for developers to integrate tools and systems:

To connect systems, you need what’s known as an API key. 

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

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

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).

In the settings, you have the following four options for your MOCO account:
a) Use personal API keys only
b) Use account API keys only
c) Use personal and account API keys
d) Disable API access completely

Custom Fields can be marked as "Only editable via the API" and then populated, for example, via a script with IDs from external systems.
This prevents users from accidentally overwriting them. If two (or more) systems need to be kept in sync, this removes the need to maintain mapping in the external system.

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

API-based automations can also be implemented with tools such as n8n or Make. Examples for n8n from Skripfabrik

»  How we extend MOCO to suit us perfectly – tools, Slack commands, chatbots