Legendary Entertainment types API
The types API from Legendary Entertainment — 2 operation(s) for types.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/legendary-types-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Legendary Entertainment WordPress REST block-directory Types API
version: wp/v2
description: 'Read-oriented content API exposed by legendary.com: the WordPress REST API (namespace wp/v2) serving Legendary Entertainment news posts, pages, media, categories and tags. Derived by API Evangelist from the live route discovery document at https://www.legendary.com/wp-json/wp/v2 . This is the platform API exposed by the marketing site, NOT a documented first-party Legendary developer program. GET collections are publicly readable without authentication; write operations require WordPress Application Password credentials.'
contact:
name: Legendary Entertainment
url: https://www.legendary.com/about/
servers:
- url: https://www.legendary.com/wp-json/wp/v2
description: Production
tags:
- name: types
paths:
/types:
get:
operationId: getTypes
summary: GET /types
tags:
- types
parameters:
- name: context
in: query
required: false
schema:
type: string
enum:
- view
- embed
- edit
default: view
description: Scope under which the request is made; determines fields present in response.
responses:
'200':
description: Successful response
headers:
X-WP-Total:
description: Total number of records
schema:
type: integer
X-WP-TotalPages:
description: Total number of pages
schema:
type: integer
Link:
description: RFC 8288 pagination links (rel=next/prev)
schema:
type: string
content:
application/json:
schema:
type: object
'400':
$ref: '#/components/responses/Error'
'401':
$ref: '#/components/responses/Error'
'404':
$ref: '#/components/responses/Error'
/types/{type}:
parameters:
- name: type
in: path
required: true
schema:
type: string
get:
operationId: getTypesByType
summary: GET /types/{type}
tags:
- types
parameters:
- name: context
in: query
required: false
schema:
type: string
enum:
- view
- embed
- edit
default: view
description: Scope under which the request is made; determines fields present in response.
responses:
'200':
description: Successful response
content:
application/json:
schema:
type: object
'400':
$ref: '#/components/responses/Error'
'401':
$ref: '#/components/responses/Error'
'404':
$ref: '#/components/responses/Error'
components:
schemas:
Error:
type: object
description: WordPress REST API error envelope (not RFC 9457)
properties:
code:
type: string
message:
type: string
data:
type: object
properties:
status:
type: integer
responses:
Error:
description: WordPress REST error envelope
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
example:
code: rest_post_invalid_id
message: Invalid post ID.
data:
status: 404
securitySchemes:
applicationPassword:
type: http
scheme: basic
description: WordPress Application Passwords, advertised by the site at https://www.legendary.com/wp-admin/authorize-application.php