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

7SIGNAL Service Areas API

The Service Areas API from 7SIGNAL — 6 operation(s) for service areas.

7SIGNAL Service Areas API is one of 33 APIs that 7SIGNAL publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Service Areas. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and rate-limit docs.

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

Requests are made against a single base URL, https://api-v2.7signal.com.

15 operations 6 paths 16 schemas 4 DELETE4 GET4 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.21.1
Base URL
https://mcp-v2.7signal.com/mcp
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

7SIGNAL Service Areas API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oauth2) using the clientCredentials flow.

Paths & Operations 15

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

Service Areas 15
GET
/service-areas/agents
List the Agent Service Areas
agent-service-areas-get 8 params → 200400404
POST
/service-areas/agents
Creates Agent Service Areas
agent-service-areas-post 1 param body → 201400
PUT
/service-areas/agents
Updates Agent Service Areas
agent-service-areas-put 1 param body → 201400
DELETE
/service-areas/agents
Deletes Agent Service Areas
agent-service-areas-delete 2 params → 204400
GET
/service-areas/agents/{serviceAreaId}
Fetch the specified Agent Service Area
agent-service-area-get 2 params → 200400404
PUT
/service-areas/agents/{serviceAreaId}
Update the specified Agent Service Area
agent-service-area-put 2 params body → 200400404
DELETE
/service-areas/agents/{serviceAreaId}
Delete the specified Agent Service Area
agent-service-area-delete 2 params → 204400
GET
/service-areas/sensors
List the Sensor Service Areas
sensor-service-areas 2 params → 200400404
POST
/service-areas/sensors
Creates a Sensor Service Area
sensor-service-areas-post body → 201400
GET
/service-areas/sensors/{serviceAreaId}
Fetch the specified Service Area
sensor-service-area 1 param → 200400404
PUT
/service-areas/sensors/{serviceAreaId}
Update the specified Sensor Service Area
sensor-service-area-put 1 param body → 200400404
DELETE
/service-areas/sensors/{serviceAreaId}
Delete the specified Sensor Service Area
sensor-service-area-delete 1 param → 204400
POST
/service-areas/sensors/{serviceAreaId}/eyes
Add Eyes to a service area
sensor-service-area-add-eyes 1 param body → 200400404
POST
/service-areas/sensors/{serviceAreaId}/networks/{networkId}
Bind a wireless network to a service area
sensor-service-area-bind-network 2 params → 200400404
DELETE
/service-areas/sensors/{serviceAreaId}/networks/{networkId}
Unbind a wireless network from a service area
sensor-service-area-unbind-network 2 params → 200400404

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are service-areas.SensorServiceArea (9 properties), service-areas.AgentServiceArea (6 properties), service-areas.PutSensorServiceAreaRequest (6 properties), common.ResponseStatusException (6 properties). Each schema is shown below with its type and property counts.

service-areas.PostSensorServiceAreaSensorsRequest
object
1 property
service-areas.GetSensorServiceAreasResponse
object
2 properties
service-areas.PostAgentServiceAreasRequest
object
1 property
service-areas.AgentSingleUpdateServiceAreaRequest
object
2 properties
service-areas.GetSensorServiceAreaResponse
common.ResponseStatusException
object
6 properties 5 required
service-areas.AgentServiceArea
object
6 properties
service-areas.GetAgentServiceAreaResponse
service-areas.GetAgentServiceAreasResponse
object
2 properties
service-areas.AgentUpdateServiceAreaRequest
object
3 properties
service-areas.PutAgentServiceAreasRequest
object
1 property
service-areas.PostSensorServiceAreaRequest
object
5 properties
service-areas.AgentCreateServiceAreaRequest
object
2 properties
service-areas.PutSensorServiceAreaRequest
object
6 properties
service-areas.SensorServiceArea
object
9 properties
common.Pagination
object
4 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

7signalsolutions-service-areas-api-openapi.yml Raw ↑

Other APIs 7SIGNAL publishes across the network.

7SIGNAL MCP Server
7SIGNAL Access API
7SIGNAL Adapter Driver Report API
7SIGNAL Alert Rules API
7SIGNAL API Keys API
7SIGNAL Audit API
7SIGNAL Authentication API
7SIGNAL Clients API
7SIGNAL Default Configurations API
7SIGNAL Eyeris API
7SIGNAL Eyes API
7SIGNAL Groups API
Where this information came from

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