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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Flare Therapeutics

Flare Therapeutics Content API

The anonymously readable WordPress REST content API behind www.flaretx.com — the 42-item corporate news archive, 14 corporate pages, a 419-item media library, the category taxonomy, cross-content search, type/taxonomy/status discovery documents and an oEmbed 1.0 provider endpoint. Flare Therapeutics publishes no OpenAPI for it; the specification in this repo is an API Evangelist derivation of the live route index, restricted to operations verified to return data anonymously on 2026-08-12.

Documentation Provider Profile APIs.io OpenAPI GitHub

Flare Therapeutics Content API is published by Flare Therapeutics on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Content, News, Media, and Search. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

This API exposes 24 operations across 24 paths, organized into 9 resource areas, and defines 12 schemas. It is described by OpenAPI 3.1.0, at version wp/v2.

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

24 operations 24 paths 12 schemas 24 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
wp/v2
Base URL
https://www.flaretx.com/wp-json
Contact
Flare Therapeutics
Resource Areas
9

Paths & Operations 24

Across 24 paths, the API surfaces 24 operations — 24 GET. They span 9 resource areas: discovery, posts, pages, media, taxonomy, comments, patterns, search, oembed. Each is listed below with its method, path, parameters, and response codes.

discovery 8

Route, type, taxonomy and status discovery documents.

GET
/
Get the REST API index
getApiIndex → 200
GET
/wp/v2
Get the wp/v2 namespace index
getNamespaceIndex 1 param → 200
GET
/wp/v2/types
List registered post types
listPostTypes 1 param → 200
GET
/wp/v2/types/{type}
Get one registered post type
getPostType 2 params → 200404
GET
/wp/v2/taxonomies
List registered taxonomies
listTaxonomies 2 params → 200
GET
/wp/v2/taxonomies/{taxonomy}
Get one registered taxonomy
getTaxonomy 2 params → 200404
GET
/wp/v2/statuses
List registered post statuses
listStatuses 1 param → 200
GET
/wp/v2/statuses/{status}
Get one registered post status
getStatus 2 params → 200404
posts 2

News archive — press releases, news coverage and scientific presentations, 2021-05-13 (Series A launch) to 2026-06-30 (Series C and CEO appointment). 42 published at harvest time.

GET
/wp/v2/posts
List news posts
listPosts 21 params → 200400
GET
/wp/v2/posts/{id}
Get one news post
getPost 4 params → 200404
pages 2

Corporate pages (14 published at harvest time) — home, about, science, pipeline, fx-909, fx-111, publications, news, press-releases, join-us, contact, privacy-policy, terms-of-use…

GET
/wp/v2/pages
List corporate pages
listPages 18 params → 200400
GET
/wp/v2/pages/{id}
Get one corporate page
getPage 4 params → 200404
media 2

Media library (419 attachments at harvest time — 400 images, 19 application/ documents, 0 video).

GET
/wp/v2/media
List media library attachments
listMedia 19 params → 200400
GET
/wp/v2/media/{id}
Get one media attachment
getMediaItem 3 params → 200404
taxonomy 4

Categories and tags. Four categories are registered (News 36, Press Release 8, FlareTx 3, Uncategorized 3); the posttag taxonomy is registered but empty.

GET
/wp/v2/categories
List categories
listCategories 13 params → 200400
GET
/wp/v2/categories/{id}
Get one category term
getCategory 2 params → 200404
GET
/wp/v2/tags
List post tags
listTags 9 params → 200
GET
/wp/v2/tags/{id}
Get one tag term
getTag 2 params → 200404
comments 2

Comment collection. Registered and reachable, but empty — no post on this deployment carries comments.

GET
/wp/v2/comments
List comments
listComments 10 params → 200
GET
/wp/v2/comments/{id}
Get one comment
getComment 2 params → 200404
patterns 2

Reusable block patterns and their categories. Registered and anonymously reachable, but both report zero published items.

GET
/wp/v2/blocks
List reusable block patterns
listReusableBlocks 5 params → 200
GET
/wp/v2/wp_pattern_category
List block-pattern categories
listPatternCategories 4 params → 200
search 1

Cross-content search across published objects.

GET
/wp/v2/search
Search across all published content
searchContent 9 params → 200400
oembed 1

oEmbed 1.0 provider endpoint for www.flaretx.com URLs.

GET
/oembed/1.0/embed
Get the oEmbed response for a www.flaretx.com URL
getOembed 3 params → 200404

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are MediaItem (30 properties), Post (28 properties), Page (26 properties), Comment (13 properties). Each schema is shown below with its type and property counts.

RenderedText
object
A WordPress rendered-text container.
1 property
Post
object
A news item from the Flare Therapeutics press archive.
28 properties
Page
object
A corporate page.
26 properties
MediaItem
object
A media library attachment.
30 properties
Term
object
A taxonomy term (category, tag or pattern category).
13 properties
Comment
object
A comment. The collection is empty on this deployment.
13 properties
SearchResult
object
A lightweight pointer returned by cross-content search. Not a stored entity — resolve it back to a Post, Page or MediaItem using id + subtype.
6 properties
PostType
object
10 properties
Taxonomy
object
8 properties
Status
object
6 properties
Oembed
object
13 properties
Error
object
The WordPress REST error envelope. NOT RFC 9457 problem details — no type URI and no application/problem+json media type. See errors/flare-therapeutics-problem…
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

flare-therapeutics-content-openapi.yml Raw ↑
#Content#News#Media#Search
← Back to F APIs
API Details
ID
flare-therapeutics:flare-therapeutics-content-api
Base URL
https://www.flaretx.com/wp-json
Docs
https://developer.wordpress.org/rest-api/
Provider
Flare Therapeutics
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=flare-therapeutics-content-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/flare-therapeutics-content-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Flare Therapeutics Content 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.