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

Base Operations Saved Location Charts API

The Saved Location Charts API from Base Operations — 10 operation(s) for saved location charts.

Base Operations Saved Location Charts API is one of 12 APIs that Base Operations publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Saved Location Charts. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 10 operations across 10 paths, and defines 13 schemas. It is described by OpenAPI 3.0.0, at version 1.0.

Requests are made against a single base URL, https://api.baseoperationsenterprise.com/.

10 operations 10 paths 13 schemas 10 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
1.0
Base URL
https://api.baseoperationsenterprise.com/
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Base Operations Saved Location Charts API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-API-KEY (ApiKey).

Paths & Operations 10

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

Saved Location Charts 10
GET
/v1/public/charts/{savedLocationId}/monthly-trend
Saved Location Monthly Time Series Analysis at City or District Level
PublicSavedLocationChartsController_getMonthlyTimeSeries_v1 10 params → 200401404422432500
GET
/v1/public/charts/{savedLocationId}/rolling-average
Saved Location 30-day Rolling Average at City or District Level
PublicSavedLocationChartsController_getRollingAverageTimeSeries_v1 10 params → 200401404422432500
GET
/v1/public/charts/{savedLocationId}/historical-monthly-trend
Saved Location Historical Monthly Trend Analysis at City or District Level
PublicSavedLocationChartsController_getMonthlyHistorical_v1 11 params → 200401404422432500
GET
/v1/public/charts/{savedLocationId}/historical-analysis/day-of-week
PublicSavedLocationChartsController_getAverageDayOfWeek_v1 10 params → 200401404432500
GET
/v1/public/charts/{savedLocationId}/historical-analysis/time-of-day
PublicSavedLocationChartsController_getAverageTimeOfDay_v1 10 params → 200401404432500
GET
/v1/public/charts/{savedLocationId}/severity-score
Saved Location Severity Score Trend Analysis at District Level
PublicSavedLocationChartsController_getSeverityScoreTrend_v1 9 params → 200401404422432500
GET
/v1/public/charts/{savedLocationId}/threat-quintiles
Saved Location Threat Quintile Analysis at District Level
PublicSavedLocationChartsController_getThreatQuintiles_v1 9 params → 200401404422432500
GET
/v1/public/charts/{savedLocationId}/threat-categories-trend
Get Threat Category Trend Chart
PublicSavedLocationChartsController_getThreatCategoryTrend_v1 10 params → 200401404432500
GET
/v1/public/charts/{savedLocationId}/source-categories-trend
Get Source Category Trend Chart
PublicSavedLocationChartsController_getSourceCategoryTrend_v1 10 params → 200401404432500
GET
/v1/public/charts/{savedLocationId}/event-breakdown
Get Event Breakdown
PublicSavedLocationChartsController_getEventBreakdown_v1 10 params → 200401404432500

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are CategoryTrendData (7 properties), HistoricalMonthlyData (4 properties), ThreatQuintilesDownloadData (4 properties), HistoricalMonthlyChartDto (4 properties). Each schema is shown below with its type and property counts.

TimeSeriesMonthlyChartData
object
3 properties 3 required
HistoricalMonthlyChartDto
object
4 properties 1 required
SankeyLink
object
3 properties 3 required
CategoryTrendData
object
7 properties 7 required
SeverityScoreData
object
3 properties 3 required
ThreatQuintilesDownloadData
object
4 properties 4 required
HistoricalMonthlyData
object
4 properties 3 required
TimeSeriesRollingChartData
object
2 properties 2 required
HistoricalTimeOfDaysData
object
3 properties 2 required
HistoricalDayOfWeekData
object
3 properties 2 required
SankeyData
object
2 properties 2 required
ChartDto
object
2 properties 1 required
SankeyNode
object
4 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

base-operations-saved-location-charts-api-openapi.yml Raw ↑

Other APIs Base Operations publishes across the network.

Base Operations Analytics API
Base Operations Base Score API
Base Operations Change Detection API
Base Operations Key Takeaways API
Base Operations Public Charts API
Base Operations Radius Charts API
Base Operations Saved Location Radius Charts API
Base Operations Saved Locations API
Base Operations Source Categories API
Base Operations Threat Categories API
Base Operations Threats API
Where this information came from

This is an independent, third-party profile of Base Operations Saved Location Charts 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.