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 Beacons API

The Beacons API from Paedae — 9 operation(s) for beacons.

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

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

This API exposes 9 operations across 4 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.

9 operations 4 paths 0 schemas 2 DELETE4 GET2 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 Beacons 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 9

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

Beacons 9
GET
/beacons
Get all beacons (supports filtering and pagination)
listBeacons 3 params → 200401
POST
/beacons
Activate beacon
activateBeacon → 200422
GET
/beacons/{factoryId}
Get beacon by factory ID
getBeacon 1 param → 200404
PUT
/beacons/{factoryId}
Update beacon metadata
updateBeacon 1 param → 200404
DELETE
/beacons/{factoryId}
Deactivate beacon
deactivateBeacon 1 param → 200404
GET
/beacons/{factoryId}/configuration
Get beacon configuration
getBeaconConfiguration 1 param → 200404
GET
/beacons/{factoryId}/tags
Get beacon tags
getBeaconTags 1 param → 200
POST
/beacons/{factoryId}/tags
Create beacon tags
createBeaconTags 1 param → 200
DELETE
/beacons/{factoryId}/tags
Delete beacon tags
deleteBeaconTags 1 param → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

paedae-beacons-api-openapi.yml Raw ↑

Other APIs Paedae publishes across the network.

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

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