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

Paedae Communications API

The Communications API from Paedae — 16 operation(s) for communications.

Paedae Communications API is one of 5 APIs that Paedae publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Communications. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

This API exposes 16 operations across 7 paths. It is described by OpenAPI 3.1.0, at version v2.

Requests are made against a single base URL, https://manager.gimbal.com/api.

16 operations 7 paths 0 schemas 4 DELETE5 GET6 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
v2
Base URL
https://manager.gimbal.com/api
Authentication
API Key, OAuth 2.0
License
Proprietary
Resource Areas
1

Authentication & Security 2

Paedae Communications API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (OrganizationServerApiKey). It supports OAuth 2.0 (ProximityOAuth2) using the authorizationCode flow. By default, every request must be authenticated.

  • OrganizationServerApiKey — Organization server API key passed as Authorization: Token token=myorganizationserverapikey.
  • ProximityOAuth2 — Some Proximity APIs require an OAuth 2.0 access token instead of the organization server API key.

Paths & Operations 16

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

Communications 16
GET
/communications
Get all communications
listCommunications → 200
POST
/communications
Create communication
createCommunication → 200422
GET
/communications/{id}
Get single communication
getCommunication 1 param → 200404
PUT
/communications/{id}
Update communication
updateCommunication 1 param → 200404
DELETE
/communications/{id}
Delete communication
deleteCommunication 1 param → 200404
POST
/communications/{id}/publish
Publish communication
publishCommunication 1 param → 200
POST
/communications/{id}/stop
Stop communication
stopCommunication 1 param → 200
GET
/communications/{id}/notification
Get notification
getCommunicationNotification 1 param → 200
POST
/communications/{id}/notification
Create notification
createCommunicationNotification 1 param → 200
DELETE
/communications/{id}/notification
Delete notification
deleteCommunicationNotification 1 param → 200
GET
/communications/{id}/geofence_targets
Get all geofence targets
getCommunicationGeofenceTargets 1 param → 200
POST
/communications/{id}/geofence_targets
Create geofence targets
createCommunicationGeofenceTargets 1 param → 200
DELETE
/communications/{id}/geofence_targets
Delete all geofence targets
deleteCommunicationGeofenceTargets 1 param → 200
GET
/communications/{id}/geofence_trigger
Get geofence trigger
getCommunicationGeofenceTrigger 1 param → 200
POST
/communications/{id}/geofence_trigger
Create geofence trigger
createCommunicationGeofenceTrigger 1 param → 200
DELETE
/communications/{id}/geofence_trigger
Delete geofence trigger
deleteCommunicationGeofenceTrigger 1 param → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

paedae-communications-api-openapi.yml Raw ↑

Other APIs Paedae publishes across the network.

Paedae Applications API
Paedae Beacon Configurations API
Paedae Beacons API
Paedae Places API
Where this information came from

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