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

Hydrostor oEmbed API

Public oEmbed 1.0 provider endpoint for hydrostor.ca URLs, returning embeddable rich metadata — title, author, thumbnail and iframe HTML — for any newsroom post, static page or A-CAES project page. Requires no credentials.

Hydrostor oEmbed API is one of 9 APIs that Hydrostor publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include oEmbed and Metadata. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

This API exposes 1 operation across 1 path, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version wp/v2.

Requests are made against a single base URL, https://hydrostor.ca/wp-json.

1 operations 1 paths 2 schemas 1 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
wp/v2
Base URL
https://hydrostor.ca/wp-json
Authentication
HTTP Basic
Contact
Resource Areas
1

Authentication & Security 1

Hydrostor oEmbed API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (applicationPassword).

  • applicationPassword — WordPress application passwords. Issued from https://hydrostor.ca/wp-admin/authorize-application.php and advertised by the API's own root document under authen…

Paths & Operations 1

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

oEmbed 1

oEmbed 1.0 provider endpoint.

GET
/oembed/1.0/embed
Get oEmbed rich metadata for a hydrostor.ca URL
getOembed 3 params → 200400404

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are OembedResponse (13 properties), Error (3 properties). Each schema is shown below with its type and property counts.

OembedResponse
object
An oEmbed 1.0 rich response as returned live by hydrostor.ca on 2026-08-22.
13 properties
Error
object
The error envelope returned by every route on this surface. Observed live on 2026-08-22; it is a WordPress-native envelope, not RFC 9457 problem+json.
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hydrostor-oembed-api-openapi.yml Raw ↑

Other APIs Hydrostor publishes across the network.

Hydrostor Projects API
Hydrostor Posts API
Hydrostor Pages API
Hydrostor Media API
Hydrostor Taxonomy API
Hydrostor Search API
Hydrostor Discovery API
Hydrostor SEO Metadata API
Where this information came from

This is an independent, third-party profile of Hydrostor oEmbed 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.