Conexus X developer docs

Two ways to build on Conexus X: call the REST API directly against your workspace data, or ship a custom view that runs inside a module — the way a monday.com module view works.

REST API

13 resources — workspaces, modules, records and everything they hold. List, create, update and delete over plain HTTP.

Extensions SDK

Build a view that runs in an iframe inside a module, talking to the host over one postMessage bridge. Framework-free core, React hooks on the side.

CLI & templates

npm create @conexus-x/app — scaffold a Next.js or React starter for a new view in one command.

Authentication

Every call — REST or SDK-proxied — runs as a real signed-in user, authenticated with a Personal Integration Token.

How the two fit together

The REST API is the full surface, authenticated with your own Personal Integration Token (PIT) — anything you could do signed in, a script can do too. The Extensions SDK is a narrower, sandboxed slice of that same API: a custom view never sees your PIT key, only the subset of endpoints its manifest declared and an admin approved, proxied through the host with the viewing user’s own session.

Building an internal script, a data sync, or a CI job against your own workspace? Start with Authentication and the REST API reference. Building something other people install into their own workspace? Start with the Extensions SDK and scaffold from the CLI.