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

Daring Foods Metadata API

Post types, taxonomies, statuses and authors.

Daring Foods Metadata API is one of 14 APIs that Daring Foods publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 8 operations across 8 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version wp/v2.

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

8 operations 8 paths 5 schemas 8 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
wp/v2
Base URL
https://daring.com/wp-json
Resource Areas
1

Paths & Operations 8

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

Metadata 8

Post types, taxonomies, statuses and authors.

GET
/wp/v2/types
List registered post types
listPostTypes 1 param → 200
GET
/wp/v2/types/{type}
Retrieve a post type
getPostType 2 params → 200404
GET
/wp/v2/taxonomies
List registered taxonomies
listTaxonomies 2 params → 200
GET
/wp/v2/taxonomies/{taxonomy}
Retrieve a taxonomy
getTaxonomy 2 params → 200404
GET
/wp/v2/statuses
List post statuses
listStatuses 1 param → 200
GET
/wp/v2/statuses/{status}
Retrieve a post status
getStatus 2 params → 200404
GET
/wp/v2/users
List authors
listUsers 10 params → 200400
GET
/wp/v2/users/{id}
Retrieve an author
getUser 3 params → 200404

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are PostType (10 properties), User (10 properties), Taxonomy (8 properties), Status (6 properties). Each schema is shown below with its type and property counts.

Error
object
The WordPress REST error envelope. NOTE: this is NOT RFC 9457 problem+json - the media type is application/json and the shape is {code, message, data}.
3 properties 3 required
User
object
A site author. Anonymous context exposes public author fields only.
10 properties
Status
object
A registered post status.
6 properties
PostType
object
A registered WordPress post type.
10 properties
Taxonomy
object
A registered WordPress taxonomy.
8 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

daring-foods-metadata-api-openapi.yml Raw ↑

Other APIs Daring Foods publishes across the network.

Daring Foods Recipes API
Daring Foods Retail Products API
Daring Foods Foodservice Products API
Daring Foods Pages API
Daring Foods Media API
Daring Foods Search API
Daring Foods Discovery API
Daring Foods Posts API
Daring Foods oEmbed API
Daring Foods SEO Metadata API
Daring Foods Categories API
Daring Foods Comments API
Where this information came from

This is an independent, third-party profile of Daring Foods Metadata 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.