canonical: https://jentic.com/apis/glynk.com/glynk

# Glynk API

Glynk is a communication and collaboration platform that combines a contact directory, direct messaging, and meeting scheduling behind a single bearer-authenticated API. Through this API, applications and AI agents can manage contact records, send and read messages, schedule and cancel meetings, and configure third-party integrations - the surface needed to drive Glynk programmatically rather than through its UI. The shape is deliberately small (17 endpoints) so it fits inside an agent tool list without overwhelming model context.

## For AI agents

Send messages, manage contacts, schedule meetings, and configure integrations on the Glynk collaboration platform.

## Scope

Does not provide voice or video calls, file storage, or pipeline-style CRM features - use for contacts, direct messages, and meetings on the Glynk platform only.

## Capabilities

- Send a direct message via POST /messages and read it back by message ID
- Create or update a Glynk contact, including external IDs for cross-system mapping
- Schedule a meeting with attendees and a time window via POST /meetings
- Cancel a previously scheduled meeting through DELETE `/meetings/{meetingId}`
- List active third-party integrations attached to the workspace
- Add or remove an integration to enable downstream automations

## Use cases

### Customer Outreach Automation

Customer success teams running Glynk for client communications can drive routine outreach through the API: list contacts via /contacts, send templated messages via POST /messages, and follow up by scheduling a meeting via POST /meetings - all without opening the Glynk UI. This collapses what is normally a multi-tab workflow into a single automation. Setup is typically a few hours.

Example prompt: POST /messages with the contact ID and templated body, then POST /meetings with the same contact and a 30-minute slot if the message is acknowledged.

### Cross-System Contact Sync

Operations teams want their Glynk contact directory to reflect the source of truth in their CRM. A scheduled job pulls CRM contacts and upserts each one via POST /contacts (or PUT `/contacts/{contactId}` if the ID is already known), keeping Glynk in lockstep with the CRM. Deletes propagate via DELETE `/contacts/{contactId}` when records are archived upstream.

Example prompt: For each CRM contact, PUT `/contacts/{contactId}` with the latest email and phone, then capture the response to confirm the update.

### AI Scheduling Assistant

An AI assistant connected through Jentic can take a natural-language request like "book a 30-minute call with Sara next Tuesday" and turn it into POST /meetings against Glynk, after first resolving the contact via GET /contacts. Because the surface is small, the agent can work end-to-end with a single Jentic search per intent.

Example prompt: Search Jentic for 'create glynk meeting', load the schema for POST /meetings, and submit with attendeeId, start, end, and a generated subject.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/messages` | Send a direct message |
| GET | `/contacts` | List contacts |
| POST | `/contacts` | Create a contact |
| PUT | `/contacts/{contactId}` | Update a contact |
| POST | `/meetings` | Schedule a meeting |
| DELETE | `/meetings/{meetingId}` | Cancel a meeting |
| GET | `/integrations` | List active integrations |

## Key resources

- **Contacts** — CRUD on Glynk contact records.
- **Messages** — Send, list, fetch, and delete direct messages.
- **Meetings** — Schedule, update, fetch, and cancel meetings.
- **Integrations** — Add, list, and remove third-party integrations on the workspace.

## Why Jentic

- **Setup:** Wiring Glynk by hand means learning its bearer auth and mapping its 17-endpoint surface across contacts, messages, and meetings yourself. Through Jentic you install once, import the Glynk API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Glynk takes the message target in the request body, so scope the agent to the operations it needs, such as sending a message and creating a contact. You choose that operation set, so destructive ones like deleting a meeting are not included unless you add them.
- **Credential handling:** Your Glynk bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'send a Glynk message' or 'schedule a Glynk meeting', and Jentic returns the matching Glynk operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Slack API** — Mainstream team chat with a much larger surface versus Glynk's compact 17-endpoint offering.
- **Discord API** — Community-focused chat platform with channels, voice, and roles.
- **Intercom API** — Customer messaging often paired with Glynk for external customer threads.

## FAQ

### What authentication does the Glynk API use?

Glynk uses HTTP bearer token authentication. Generate the token in your Glynk workspace settings and send it as Authorization: Bearer {token} on each request. Through Jentic the token sits in the vault and never appears in the agent's prompt.

### Can I send messages with the Glynk API?

Yes. POST /messages accepts a recipient and message body, and returns the created message ID. GET `/messages/{messageId}` reads the same message back, and DELETE `/messages/{messageId}` removes it from the workspace.

### What are the rate limits for the Glynk API?

The OpenAPI spec does not document a fixed rate limit. Treat the API as a normal SaaS endpoint - back off on HTTP 429 responses and avoid tight loops over /contacts when populating large directories.

### How do I schedule a Glynk meeting through Jentic?

Search Jentic for 'create glynk meeting', load the schema for POST /meetings, and execute with attendeeIds, start, end, and a subject. Run pip install jentic to install the SDK first.

### Can I manage third-party integrations through the API?

Yes. GET /integrations lists active integrations on the workspace, POST /integrations adds a new one, and DELETE `/integrations/{integrationId}` removes it. This is enough to provision and tear down integrations as part of a workspace setup script.

### Is the Glynk API free to use?

Glynk does not publish per-call API pricing. API access typically follows the workspace plan, so check your subscription tier on glynk.com before building a high-volume integration.

### Can I limit what my agent is allowed to do with the Glynk API?

Yes. Because you run Jentic One yourself, you decide which Glynk operations your agent can call and which credentials it uses. You can allow only the endpoints a task needs, such as POST /messages to send a message and POST /contacts to create a contact, while leaving out destructive operations like DELETE `/meetings/{meetingId}` unless you explicitly add them. Your Glynk bearer token stays with your own instance and is injected at execution time, so the agent acts only within the operation set and access you have granted.