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

Urban Observatory API (Urban Sciences Building) — Timeseries

There may be more than one timeseries associated with a feed. Ordinarily there will be a plain timeseries representing raw data from the device; in some cases there may be additional timeseries representing converted, corrected or temporally aggregated values.

Urban Observatory API (Urban Sciences Building) — Timeseries is one of 8 APIs that Newcastle University publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 2 JSON Schema definitions.

Tagged areas include Time Series, Smart Cities, and Open Data. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 2 JSON Schemas.

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

Requests are made against a single base URL, https://api.usb.urbanobservatory.ac.uk/api/v2.0a.

2 operations 2 paths 7 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0a
Base URL
https://api.usb.urbanobservatory.ac.uk/api/v2.0a
Contact
Resource Areas
1

Paths & Operations 2

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

Timeseries 2

There may be more than one timeseries associated with a feed, provided for convenience. Ordinarily there will be a plain timeseries, representing raw data from the device. In some…

GET
/api/v2.0a/sensors/timeseries/{id}
Request a single timeseries by its unique ID
TimeseriesController.getOne 1 param → 200400
GET
/api/v2.0a/sensors/timeseries/{id}/historic
Request historic data from a timeseries by its unique ID and a date range
TimeseriesController.getHistoric 4 params → 200400403

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are Timeseries (8 properties), TimeseriesEntry (6 properties), Forbidden (3 properties), Storage (3 properties). Each schema is shown below with its type and property counts.

Unit
object
The units associated with the values held in the timeseries.
2 properties
BadRequest
object
An invalid ID or query parameter was used to request information, such as an ID not in the [UUID syntax](https://en.wikipedia.org/wiki/Universallyuniqueidentif…
3 properties
Link
object
A link provided for [HATEOAS](https://en.wikipedia.org/wiki/HATEOAS) purposes, to the item itself or an associated API method.
3 properties
TimeseriesEntry
object
A historic entry associated with a timeseries and a time.
6 properties
Storage
object
The storage mechanism used to hold the data internally.
3 properties
Timeseries
object
8 properties
Forbidden
object
The requested data could not be returned, because permissions do not permit.
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

newcastle-timeseries-api-openapi.yml Raw ↑

Other APIs Newcastle University publishes across the network.

Digitised Objects Repository Search and Data API
ECPPEC Electoral Data GraphQL API
Newcastle University eTheses OAI-PMH Endpoint
data.ncl Research Data Repository (Figshare tenancy)
Urban Observatory API (Urban Sciences Building) — Entity
Urban Observatory API (Urban Sciences Building) — Feed
Urban Observatory API (Urban Sciences Building) — Summary
Where this information came from

This is an independent, third-party profile of Urban Observatory API (Urban Sciences Building) — Timeseries, 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.