InfoLobby Public API

Building with an AI agent? Install the InfoLobby AI Agent Skill in one line and use this API conversationally from Claude Code, Cursor, Gemini CLI, and any other agent that supports the open Agent Skills format.

Use the InfoLobby Public API to read and write your workspace data from any external system — CRM tools, data pipelines, scripts, dashboards, or integration platforms like ProcFu.

Base URL

https://infolobby.com/api

Requests

Every parameter travels in a JSON request body, including on endpoints documented as GET. Query-string parameters are ignored — ?limit=2 has no effect, you want {"limit": 2} in the body. Send Content-Type: application/json.

State-changing endpoints (anything that creates, updates, deletes, subscribes, reorders, or otherwise writes) require POST; calling one with GET returns 405. Read endpoints accept either verb.

Because a GET request cannot carry a body on most platforms (the WHATWG Fetch spec prohibits it, as do Node fetch and Cloudflare Workers), use POST whenever you need to pass parameters — even for read endpoints. All read endpoints accept POST.

Successful responses are application/json. There is no version segment in the path.

What you can do

  • List, create, update, and delete workspaces (account keys with no workspace restriction only)
  • List, create, update, and delete tables
  • Create, update, and delete records
  • Query and filter records
  • Read and post comments on records
  • Upload, delete, and download file attachments on records
  • Subscribe to tables and records for change notifications
  • Read and author report tiles, and fetch their computed values
  • Access your notifications and tasks (personal API keys)

What the API does not cover

To keep the surface secure and simple, the public API deliberately excludes:

  • User, account, and billing management
  • Integration credentials
  • Web forms
  • CRM email (sending, signatures, SMTP options) — session-only
  • Creating, updating, or deleting saved views — session-only, though views are readable

These remain available only through the logged-in interface.

Automations (flows) are available, to account keys — see Flows.

Workspace membership is covered for account keys on workspaces in scope. Personal API keys cannot manage workspace membership.

Personal API keys (il_user_) are scoped to a single user's notifications, tasks, and data. They cannot create, update, or delete workspaces or tables — those operations require an account API key (il_live_) with no workspace restriction.

Two types of API keys

Account keys Personal keys
Prefix il_live_ il_user_
Identity Account owner Your user
Created by Account owner (Account settings) Any user (Profile page)
Notifications & tasks No Yes
Data access All account data (scoped by key) Data you have access to

Getting started

Account keys (data integrations)

  1. Go to Account → API Keys in your InfoLobby dashboard
  2. Click Create API Key
  3. Copy the generated secret — it is only shown once
  4. Send it as a Bearer token:
Authorization: Bearer il_live_<your_secret>

Personal keys (your notifications, tasks, and data)

  1. Go to Profile (click your name or avatar)
  2. Scroll to Personal API Keys
  3. Click Create Personal API Key
  4. Copy the generated secret
  5. Send it as a Bearer token:
Authorization: Bearer il_user_<your_secret>

Authentication

See Authentication for full details.

Rate limits

See Rate Limits. Limits scale with your plan.

Errors

See Errors for the response format and status codes.

Endpoints

  • Spaces — list workspaces
  • Tables — list tables, fetch schemas
  • Records — CRUD and querying
  • Comments — read and create record comments
  • Files — upload, delete, and download record attachments
  • Subscriptions — follow/unfollow tables and records
  • Reports — read, author, and fetch values of table report tiles
  • Tasks — create, update, and manage tasks
  • Notifications — list and manage notifications (personal keys)