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

Emotive Connections API

The Connections API from Emotive — 4 operation(s) for connections.

Emotive Connections API is one of 36 APIs that Emotive 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, authentication docs, and a getting-started guide.

This API exposes 6 operations across 4 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

Requests are made against a single base URL, https://api-gw.emotiveapp.co/helpdesk.

6 operations 4 paths 7 schemas 1 DELETE3 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://api.emotiveapp.co
Authentication
API Key, API Key, API Key, HTTP Bearer, API Key
License
Private
Resource Areas
1

Authentication & Security 5

Emotive Connections API declares 5 security schemes for authenticating requests. An API key is passed in the header as X-API-Key (AlloyKeyAuth). An API key is passed in the header as X-API-Key (ApiKeyAuth). An API key is passed in the header as X-API-Key (InternalApiKeyAuth). It accepts HTTP bearer tokens (JWT) (bearerAuth). An API key is passed in the cookie as access_token_cookie (cookieAuth).

Paths & Operations 6

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

Connections 6
GET
/connections/config
Get all helpdesk connections for a brand.
controllers.connections.get_brand_connections 3 params → 200400401
POST
/connections/config
Create helpdesk connection for a brand.
controllers.connections.post body → 200400401
DELETE
/connections/config/{connection_id}
Delete Helpdesk connection for a brand.
controllers.connections.delete 1 param → 204400401
GET
/connections/config/{connection_id}
Helpdesk connection details.
controllers.connections.get 1 param → 200401404
POST
/connections/internal
Create helpdesk connection for a brand using internal credentials.
controllers.connections.post_internal body → 200400401
GET
/connections/me
Checks validity of API Token for active connection.
controllers.connections.check_brand_connection → 200401

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are ConnectionSchema (6 properties), ConnectionInternalRequestSchema (5 properties), ConnectionRequestSchema (3 properties), TicketSystemTypeSchema (2 properties). Each schema is shown below with its type and property counts.

ConnectionInternalRequestSchema
object
5 properties
authType
string
JsonResponse
object
1 property
TicketSystemTypeSchema
object
2 properties
ConnectionListSchema
array
ConnectionRequestSchema
object
3 properties
ConnectionSchema
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

emotive-connections-api-openapi.yml Raw ↑

Other APIs Emotive publishes across the network.

Emotive Knowledge Base MCP Server
Emotive Admin API
Emotive Auth0 API
Emotive Authentication Source API
Emotive Brand API
Emotive Brands API
Emotive Bulk Subscriber API
Emotive Custom Events API
Emotive Experience API
Emotive Google API
Emotive Impersonate API
Emotive JWT API
Where this information came from

This is an independent, third-party profile of Emotive 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.