How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Relm Connections API

The Connections API from Relm — 2 operation(s) for connections.

Relm Connections API is one of 16 APIs that Relm publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Connections. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and rate-limit docs.

This API exposes 3 operations across 2 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 0.17.1.

Requests are made against a single base URL, https://api.relmcrm.com/v1.

3 operations 2 paths 2 schemas 1 DELETE1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.17.1
Base URL
https://api.relmcrm.com/v1
Authentication
HTTP Bearer, OAuth 2.0
Contact
License
Proprietary
Resource Areas
1

Authentication & Security 2

Relm Connections API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 1 scope. By default, every request must be authenticated.

  • bearerAuth — Workspace-scoped API key. relmlive... (live) or relmtest... (free, isolated test mode). Mint at https://app.relmcrm.com/.
  • oauth2 — OAuth 2.1 with PKCE (S256) and dynamic client registration (RFC 7591). Live mode only; test mode is API-key only. Discovery: /.well-known/oauth-authorization-s…

Paths & Operations 3

Across 2 paths, the API surfaces 3 operations — 1 DELETE, 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Connections 3
GET
/connections
List connected messaging channels (never returns the secret)
listConnections → 200default
POST
/connections
Connect a BYO channel (e.g. email/Resend). Key encrypted at rest
createConnection body → 201default
DELETE
/connections/{id}
Delete a connection
deleteConnection 1 param → 200default

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are Problem (9 properties), Deleted (3 properties). Each schema is shown below with its type and property counts.

Problem
object
RFC-9457 error. Closed-set rejections carry validoptions + suggestion so an agent self-corrects.
9 properties
Deleted
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

relmcrm-com-connections-api-openapi.yml Raw ↑

Other APIs Relm publishes across the network.

Relm MCP Server
Relm A2A Agent
Relm Activities API
Relm Automations API
Relm Batch API
Relm Companies API
Relm Contacts API
Relm Deals API
Relm Discovery API
Relm Pipelines API
Relm Registry API
Relm Search API
Where this information came from

This is an independent, third-party profile of Relm Connections API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.