Gmelius API

Name: Gmelius API
Brand: Gmelius API
Availability: InStock

✓ Official Vendor SpecProductivityCollaborationbearer, basic36 EndpointsREST

For Agents

Manage Gmelius shared-inbox boards, cards, conversations, sequences, and webhooks alongside a Gmail-native collaboration workspace.

Install Jentic One Beta

Connect the Gmelius API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Gmelius API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Gmelius API.

Create a Gmelius board with named columns to drive a kanban view of shared-inbox work

Move a card between columns or assign tags via PATCH /auth/boards/cards/{id}

List boards, columns, and the cards inside a column to power a custom workspace dashboard

GET STARTED

Start building with Gmelius API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Gmelius API for, with concrete tasks.

★ Shared-Inbox Kanban Automation

Support and ops teams using Gmelius for shared inboxes can drive their kanban workflow through the API: incoming conversations create cards in a Triage column via POST /auth/boards/columns/{id}/cards, automations move cards to In-Progress on first reply, and Done columns archive resolved work. The API exposes both boards and columns so the layout can be programmed rather than configured manually. Setup is typically half a day.

POST /auth/boards/columns/{id}/cards with a title and conversationId, then PATCH /auth/boards/cards/{id} when the conversation status changes.

Cross-Team Reporting Dashboard

Managers want a single dashboard that summarises board activity across the company: open cards per column, average time-in-stage, and tag distribution. Listing /auth/boards, then /auth/boards/{id}/columns, then /auth/boards/columns/{id}/cards yields the data, and a daily aggregation feeds a BI tool. The data shape is stable enough to support trending without needing scraping.

Loop over /auth/boards, then for each board read /auth/boards/{id}/columns and /auth/boards/columns/{id}/cards, and aggregate counts per column.

Webhook-Driven Downstream Notifications

Teams that already run an internal Slack or queue can register a Gmelius webhook to mirror card and conversation changes outbound. The /auth/webhooks endpoints (covered in the Webhooks tag) let an integration subscribe to events, then transform and forward them to other tools without polling the API. This avoids missing changes when teams are heads-down.

Register a webhook against the Gmelius API with the destination URL, then transform inbound payloads to the downstream Slack message format.

AI Triage Across Shared Inboxes

An AI assistant reading shared-inbox conversations through Jentic can categorise incoming threads and create or move Gmelius cards accordingly. With a single Jentic search the agent can load the right card-creation schema and avoid writing direct HTTP code against the 36-endpoint Gmelius surface.

Search Jentic for 'create gmelius card', load the schema for POST /auth/boards/columns/{id}/cards, and create a card in the Triage column.

Key Endpoints

36 endpoints — gmelius layers shared inboxes, trello-style boards, email sequences, and team collaboration on top of gmail.

METHOD

PATH

DESCRIPTION

GET

/auth/boards

List boards

POST

/auth/boards

Create a board

GET

/auth/boards/{id}/columns

List columns in a board

POST

/auth/boards/columns/{id}/cards

Create a card in a column

PATCH

/auth/boards/cards/{id}

Update a card

DELETE

/auth/boards/cards/{id}

Delete a card

POST

/token

Exchange authorization code for tokens

GET

/auth/boards

List boards

POST

/auth/boards

Create a board

GET

/auth/boards/{id}/columns

List columns in a board

POST

/auth/boards/columns/{id}/cards

Create a card in a column

PATCH

/auth/boards/cards/{id}

Update a card

DELETE

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Gmelius OAuth client secrets and bearer tokens are stored encrypted in the Jentic vault. Agents receive a scoped credential reference and the Authorization header is injected at execution time, so the raw secrets never enter the agent's prompt.

Intent-based discovery

Agents search Jentic by intent ('create gmelius card', 'list boards') and Jentic returns the matching Gmelius operation with its JSON schema, so the agent navigates the 36-endpoint surface without reading developers.gmelius.com.

Time to first call

Direct Gmelius integration: 1-2 days for OAuth code exchange, board-id navigation, and webhook setup. Through Jentic: under an hour - search, load, execute.

FAQs

Specific to using Gmelius API through Jentic.

What authentication does the Gmelius API use?

Gmelius uses OAuth-issued bearer tokens for most endpoints (Authorization: Bearer {token}) plus HTTP basic auth on the POST /token endpoint that exchanges an authorization code for tokens. Through Jentic both credentials sit in the vault and are injected per call.

Can I create and update kanban cards through the Gmelius API?

Yes. POST /auth/boards/columns/{id}/cards creates a card in a column and PATCH /auth/boards/cards/{id} updates it. Cards can carry tags via POST /auth/boards/cards/{id}/tags and be deleted via DELETE /auth/boards/cards/{id}.

What are the rate limits for the Gmelius API?

Gmelius does not publish a fixed per-second rate limit in the OpenAPI spec; back off on HTTP 429 responses. Webhooks (registered via the /auth/webhooks endpoints) are the recommended pattern for high-frequency change tracking instead of polling.

How do I list a board's columns and cards through Jentic?

Search Jentic for 'list gmelius columns' and 'list gmelius cards', load the schemas for GET /auth/boards/{id}/columns and GET /auth/boards/columns/{id}/cards, and execute them in sequence. Run pip install jentic first.

Does Gmelius support webhooks for card events?

Yes. The Webhooks tag in the OpenAPI spec covers webhook registration so external systems are notified when cards or conversations change, replacing the need to poll /auth/boards/columns/{id}/cards.

Is the Gmelius API free to use?

API access typically follows the Gmelius workspace plan rather than being billed per call. Check your team's Gmelius subscription tier - higher tiers expose more board, sequence, and webhook quotas.

Gmelius API

Connect the Gmelius API to your agent

Capabilities

Start building with Gmelius API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs