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

The Locations API from 7SIGNAL — 4 operation(s) for locations.

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

Tagged areas include Location. 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 12 operations across 4 paths, and defines 17 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.

12 operations 4 paths 17 schemas 3 DELETE4 GET2 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://api-v2.7signal.com
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

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

Paths & Operations 12

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

Locations 12
GET
/locations/agents
List the Agent Locations
agent-locations-get 1 param → 200400404
POST
/locations/agents
Creates an Agent Location
agent-locations-post 1 param body → 201400
GET
/locations/agents/{locationId}
Fetch the specified Agent Location
agent-location-get 2 params → 200400404
PUT
/locations/agents/{locationId}
Replace the specified Agent Location with the details in the payload
agent-location-put 2 params body → 200400404
DELETE
/locations/agents/{locationId}
Delete the Agent Location specified by the UUID
agent-location-delete 2 params → 204404
GET
/locations/sensors
List the Sensor Locations
sensor-locations-get 1 param → 200400404
POST
/locations/sensors
Creates Sensor Locations
sensor-locations-post body → 201400
PUT
/locations/sensors
Updates Sensor Locations
sensor-locations-put body → 201400
DELETE
/locations/sensors
Deletes Sensor Locations
sensor-locations-delete 1 param → 204400
GET
/locations/sensors/{locationId}
Fetch the specified Sensor Location
sensor-location 1 param → 200400404
PUT
/locations/sensors/{locationId}
Update the specified Sensor Location
sensor-location-put 1 param body → 200400404
DELETE
/locations/sensors/{locationId}
Delete the specified Sensor Location
sensor-location-delete 1 param → 204400

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are locations.SensorLocation (9 properties), service-areas.AgentServiceArea (6 properties), locations.GetAgentLocationResponse (6 properties), locations.SensorCreateLocationRequest (6 properties). Each schema is shown below with its type and property counts.

locations.AgentLocationResponse
object
4 properties
locations.SensorLocation
object
9 properties
locations.GetSensorLocationResponse
locations.GetAgentLocationResponse
object
6 properties
locations.SensorUpdateLocationRequest
object
6 properties
locations.AgentLocationRequest
object
2 properties
locations.PutSensorLocationsRequest
object
1 property
locations.CountryCodeName
string
A CountryCode enum constant name. The ISO 3166-1 alpha-2 code (e.g. "US") is also accepted on write, case-insensitively, but is not reflected in this enum list
common.ResponseStatusException
object
6 properties 5 required
service-areas.AgentServiceArea
object
6 properties
locations.TimeZoneId
string
A valid TimeZone identifier
locations.PostSensorLocationsRequest
object
1 property
locations.SensorSingleUpdateLocationRequest
object
5 properties
locations.SensorCreateLocationRequest
object
6 properties
locations.GetAgentLocationsResponse
object
2 properties
locations.GetSensorLocationsResponse
object
2 properties
common.Pagination
object
4 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

7signalsolutions-locations-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 Locations 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.