Paedae

Paedae Beacon Configurations API

The Beacon Configurations API from Paedae — 5 operation(s) for beacon configurations.

Documentation GitHub OpenAPI

Operations 5

GET /beacon_configurations Get all configurations #

POST /beacon_configurations Create configuration #

GET /beacon_configurations/{configurationId} Get specific configuration #

PUT /beacon_configurations/{configurationId} Update configuration #

DELETE /beacon_configurations/{configurationId} Delete configuration #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/paedae:paedae-beacon-configurations-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  title: Gimbal REST Beacon Configurations API
  version: v2
  description: 'The Gimbal REST API manages proximity and location assets for the Gimbal platform operated by Paedae/Infillion: applications, places (geofences and beacons), beacons and their configurations, and communications (notifications and triggers). All requests and responses use JSON.'
  contact:
    name: Gimbal Support
    url: https://support.gimbal.com/hc/en-us/
  license:
    name: Proprietary
servers:
- url: https://manager.gimbal.com/api
  description: Gimbal Manager API
security:
- OrganizationServerApiKey: []
tags:
- name: Beacon Configurations
paths:
  /beacon_configurations:
    get:
      tags:
      - Beacon Configurations
      operationId: listBeaconConfigurations
      summary: Get all configurations
      responses:
        '200':
          description: Success
    post:
      tags:
      - Beacon Configurations
      operationId: createBeaconConfiguration
      summary: Create configuration
      responses:
        '200':
          description: Success
        '422':
          $ref: '#/components/responses/Unprocessable'
  /beacon_configurations/{configurationId}:
    parameters:
    - name: configurationId
      in: path
      required: true
      schema:
        type: string
    get:
      tags:
      - Beacon Configurations
      operationId: getBeaconConfigurationById
      summary: Get specific configuration
      responses:
        '200':
          description: Success
        '404':
          $ref: '#/components/responses/NotFound'
    put:
      tags:
      - Beacon Configurations
      operationId: updateBeaconConfiguration
      summary: Update configuration
      responses:
        '200':
          description: Success
        '404':
          $ref: '#/components/responses/NotFound'
    delete:
      tags:
      - Beacon Configurations
      operationId: deleteBeaconConfiguration
      summary: Delete configuration
      responses:
        '200':
          description: Success
        '404':
          $ref: '#/components/responses/NotFound'
components:
  responses:
    NotFound:
      description: Resource Not Found (404)
    Unprocessable:
      description: Unprocessable Entity (422)
  securitySchemes:
    OrganizationServerApiKey:
      type: apiKey
      in: header
      name: Authorization
      description: 'Organization server API key passed as `Authorization: Token token=my_organization_server_api_key`.'
    ProximityOAuth2:
      type: oauth2
      description: Some Proximity APIs require an OAuth 2.0 access token instead of the organization server API key.
      flows:
        authorizationCode:
          authorizationUrl: https://manager.gimbal.com/oauth/authorize
          tokenUrl: https://manager.gimbal.com/oauth/token
          scopes: {}