DEVELOPERS Open ALOCA

API & MCP · PREVIEW

Your workspace.
Your tools.

Connect projects and tasks to the tools you work with.

Documentation preview · API access is not available yet

This page describes the planned integration. API tokens, resource endpoints and MCP sign-in are not implemented. The routes below cannot read or change records yet.

Planned REST base URLhttps://api.aloca.io/v1

Endpoints

ALL PLANNED

Project items are tasks inside a project. Standalone tasks are linked to contacts and use separate identifiers.

Projects

GET/v1/projects
List accessible projects. Planned filters: search, status and tag.
GET/v1/projects/{id}
Read one accessible project.
POST/v1/projects
Create a project in the authorized workspace.
PATCH/v1/projects/{id}
Edit permitted project fields.

Project items

GET/v1/projects/{id}/items
List permitted items in a project.
GET/v1/project-items/{id}
Read one permitted project item.
POST/v1/projects/{id}/items
Create an item in a project.
PATCH/v1/project-items/{id}
Edit an item or change its state, within your role.

Standalone tasks

GET/v1/tasks
List accessible contact tasks.
GET/v1/tasks/{id}
Read one accessible task.
POST/v1/tasks
Create a task linked to a contact in the same workspace.
PATCH/v1/tasks/{id}
Edit permitted task fields.

Request fields, limits and working examples will be published with the implementation. The OpenAPI contract at /openapi.json is also pending.

PLANNED AUTHORIZATION

Private by workspace.

Each connection will belong to one user and one workspace, with explicitly selected resources and permissions.

Scripts & integrations

Create an expiring API token in Settings, choose its access and revoke it when needed. Tokens will use the Authorization header.

Your existing permissions

Viewers will remain read-only. Editors can change permitted records. Task workers can update the state of their permitted tasks.

Updates will check the current record revision. Repeated writes will use an idempotency key to prevent duplicate changes.

This release plan does not include email sending, campaigns, account administration or deletion through the public API.

PLANNED · CHATGPT FIRST

Bring your workspace to AI.

MCP connects AI applications to your tools. The planned connection will let ChatGPT read projects and update permitted tasks after your approval.

Planned MCP URLhttps://api.aloca.io/mcp
  1. Connect the MCP URL in your AI application.
  2. Sign in on aloca.io and select a workspace.
  3. Review the requested access and approve the connection.

This connection is not ready to add yet. OAuth sign-in and client verification must be completed first. A separate MCP domain is not required.