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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Rhombus Systems

Rhombus Systems Event Search Webservice API

The Event Search Webservice API from Rhombus Systems — 2 operation(s) for event search webservice.

Documentation Provider Profile APIs.io OpenAPI GitHub

Rhombus Systems Event Search Webservice API is one of 65 APIs that Rhombus Systems publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Event Search Webservice. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

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

Requests are made against a single base URL, https://api2.rhombussystems.com.

2 operations 2 paths 16 schemas 2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api2.rhombussystems.com/api
Authentication
API Key
Contact
developer@rhombussystems.com
Resource Areas
1

Authentication & Security 1

Rhombus Systems Event Search Webservice API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-auth-apikey (ApiKeyAuth). By default, every request must be authenticated.

  • ApiKeyAuth — Your Rhombus API key. Must be accompanied by the x-auth-scheme header set to api-token (or partner-api-token for partner endpoints).

Paths & Operations 2

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

Event Search Webservice 2
POST
/api/eventSearch/getCameraOrDoorbellCameraSeekpointsdeprecated
Get camera or doorbell camera seekpoints
getCameraOrDoorbellCameraSeekpoints 1 param body → 200
POST
/api/eventSearch/getEventSeekpointsdeprecated
Get normal seekpoint events and access control seekpoint events
getDeprecatedEventSeekpoints 1 param body → 200

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are Eventsearch_CombinedSeekPointType (18 properties), Eventsearch_GetEventSeekpointsWSRequest (10 properties), Eventsearch_VideoFootageWSRequest (6 properties), Common_devices_GetCameraOrDoorbellCameraSeekpointsWSRequest (6 properties). Each schema is shown below with its type and property counts.

Component_FindComponentSeekPointsByAccessControlledDoorsWSRequest
object
Component seekpoints search for access controlled doors
4 properties
Eventsearch_CombinedSeekPointType
object
Combined seekpoint type containing information from various event sources including timestamps, activities, and metadata.
18 properties
ActivityEnum
string
Eventsearch_GetEventSeekpointsWSRequest
object
Request object for retrieving event seekpoints with various search criteria and filtering options.
10 properties
ColorEnum
string
Set of colors to filter by
FootageSeekPointColorEnum
string
Event_SearchMotionGridWithActivitiesWSRequest
object
Request object for searching motion grid data with activity information.
4 properties 4 required
Event_FrontendCell
object
Represents a cell in the motion grid with column and row coordinates.
2 properties
Eventsearch_SearchClothingAndVehicleByColorWSRequest
object
Request object for searching clothing and vehicle events by color with time and device filtering.
5 properties
Common_devices_GetSeekpointsWSRequest
object
General seekpoints search request parameters
4 properties
Component_FindComponentSeekPointsByOwnerDeviceWSRequest
object
Component seekpoints search for owner device
3 properties
Eventsearch_GetEventSeekpointsWSResponse
object
Response object containing combined seekpoints from various event sources.
4 properties
Eventsearch_GetCameraOrDoorbellCameraSeekpointsWSResponse
object
Response object containing seekpoints from camera or doorbell camera events.
4 properties
Eventsearch_VideoFootageWSRequest
object
Request object for video footage search with camera selection and multi-camera options.
6 properties
Common_devices_GetCameraOrDoorbellCameraSeekpointsWSRequest
object
6 properties
Component_FindComponentSeekPointsByAccessControlledDoorWSRequest
object
Component seekpoints search for access controlled door
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

rhombus-systems-event-search-webservice-api-openapi.yml Raw ↑

Other APIs Rhombus Systems publishes across the network.

Rhombus Console WebSocket API
AE Profile APIs.io
Rhombus Systems Access Control Integrations Webservice API
AE Profile APIs.io
Rhombus Systems Access Control Webservice API
AE Profile APIs.io
Rhombus Systems Alarm Monitoring Keypad Webservice API
AE Profile APIs.io
Rhombus Systems Alert Monitoring Webservice API
AE Profile APIs.io
Rhombus Systems AudioGateway Webservice API
AE Profile APIs.io
Rhombus Systems AudioPlayback Webservice API
AE Profile APIs.io
Rhombus Systems Badge Reader Webservice API
AE Profile APIs.io
Rhombus Systems BLE Webservice API
AE Profile APIs.io
Rhombus Systems Button Webservice API
AE Profile APIs.io
Rhombus Systems Camera Webservice API
AE Profile APIs.io
Rhombus Systems ClaimKey Webservice API
AE Profile APIs.io
#Event Search Webservice
← Back to R APIs
API Details
ID
rhombus-systems:rhombus-systems-event-search-webservice-api
Base URL
https://api2.rhombussystems.com/api
Docs
https://api-docs.rhombus.community/
Provider
Rhombus Systems
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=rhombus-systems-event-search-webservice-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/rhombus-systems-event-search-webservice-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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

Where this information came from

This is an independent, third-party profile of Rhombus Systems Event Search Webservice 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.