Boston University WordPress REST API

The WordPress REST API on Boston University's own web platform, and the one substantial machine-readable interface the institution both operates and authors. Its discovery document advertises 237 routes across 15 namespaces; nine of those namespaces — bu-alert, bu-access-control, bu-blocks, bu-cmb2-customizations, bu-navigation, bu-prepress, bu-site-manager, bu-slideshow and bu-tts, 31 routes in total — are implemented by WordPress plugins Boston University IS&T writes, open-sources at github.com/bu-ist and documents at developer.bu.edu. Read routes including /wp/v2/pages, /wp/v2/types, /wp/v2/taxonomies, /bu-blocks/v1/search and the per-namespace discovery documents answer anonymous callers; privileged routes such as /bu-navigation/v1/parents and /bu-access-control/v1/get-groups return HTTP 401 rest_forbidden. Boston University does not present this as a product: there is no developer registration, no key, no rate-limit statement and no changelog. The OpenAPI in this repository was derived from the live discovery document, not published by BU.

Operations 42

GET /bu-access-control/v1 GET /bu-access-control/v1 #
POST /bu-access-control/v1/delete-group POST /bu-access-control/v1/delete-group #
GET /bu-access-control/v1/get-group-usage GET /bu-access-control/v1/get-group-usage #
GET /bu-access-control/v1/get-groups GET /bu-access-control/v1/get-groups #
POST /bu-access-control/v1/update-group POST /bu-access-control/v1/update-group #
GET /bu-alert/v1 GET /bu-alert/v1 #
POST /bu-alert/v1/start POST /bu-alert/v1/start #
POST /bu-alert/v1/stop POST /bu-alert/v1/stop #
GET /bu-alert/v1/stop GET /bu-alert/v1/stop #
GET /bu-blocks/v1 GET /bu-blocks/v1 #
GET /bu-blocks/v1/collection GET /bu-blocks/v1/collection #
GET /bu-blocks/v1/customhtml GET /bu-blocks/v1/customhtml #
POST /bu-blocks/v1/customhtml POST /bu-blocks/v1/customhtml #
PUT /bu-blocks/v1/customhtml PUT /bu-blocks/v1/customhtml #
PATCH /bu-blocks/v1/customhtml PATCH /bu-blocks/v1/customhtml #
DELETE /bu-blocks/v1/customhtml DELETE /bu-blocks/v1/customhtml #
GET /bu-blocks/v1/yarpprelated GET /bu-blocks/v1/yarpprelated #
GET /bu-cmb2-customizations/v1 GET /bu-cmb2-customizations/v1 #
GET /bu-cmb2-customizations/v1/bu-post-chooser GET /bu-cmb2-customizations/v1/bu-post-chooser #
GET /bu-navigation/v1 GET /bu-navigation/v1 #
GET /bu-navigation/v1/markup GET /bu-navigation/v1/markup #
GET /bu-navigation/v1/parents GET /bu-navigation/v1/parents #
GET /bu-prepress/v1 GET /bu-prepress/v1 #
GET /bu-prepress/v1/event GET /bu-prepress/v1/event #
GET /bu-site-manager/v1 GET /bu-site-manager/v1 #
GET /bu-site-manager/v1/snapshots/list GET /bu-site-manager/v1/snapshots/list #
POST /bu-site-manager/v1/snapshots/pull POST /bu-site-manager/v1/snapshots/pull #
POST /bu-site-manager/v1/snapshots/push POST /bu-site-manager/v1/snapshots/push #
GET /bu-slideshow/v1 GET /bu-slideshow/v1 #
GET /bu-slideshow/v1/markup GET /bu-slideshow/v1/markup #
GET /bu-slideshow/v1/shows GET /bu-slideshow/v1/shows #
GET /bu-tts/v1 GET /bu-tts/v1 #
GET /bu-tts/v1/bu-article/{id} GET /bu-tts/v1/bu-article/{id} #
GET /bu-tts/v1/bu-article/{id}/status GET /bu-tts/v1/bu-article/{id}/status #
GET /bu-tts/v1/status/{id} GET /bu-tts/v1/status/{id} #
GET /wp/v2/pages GET /wp/v2/pages #
POST /wp/v2/pages POST /wp/v2/pages #
GET /wp/v2/posts GET /wp/v2/posts #
POST /wp/v2/posts POST /wp/v2/posts #
GET /wp/v2/taxonomies GET /wp/v2/taxonomies #
GET /wp/v2/types GET /wp/v2/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.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/wordpress-rest-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

boston-wordpress-api-openapi.yml Raw ↑
openapi: 3.1.0
info:
  title: Boston University WordPress REST API
  version: '2026-08-30'
  summary: Boston University IS&T-authored REST namespaces on www.bu.edu, plus the core WordPress read
    routes verified live.
  description: 'Boston University operates its own WordPress platform at www.bu.edu and exposes a public
    WordPress REST discovery document at https://www.bu.edu/wp-json/. Nine of the fifteen namespaces it
    advertises are Boston University''s own engineering — bu-alert, bu-access-control, bu-blocks, bu-cmb2-customizations,
    bu-navigation, bu-prepress, bu-site-manager, bu-slideshow and bu-tts — implemented by the open-source
    WordPress plugins BU IS&T publishes at https://github.com/bu-ist and documents at https://developer.bu.edu/.
    That makes this the one substantial machine-readable interface Boston University itself operates and
    authors, as opposed to the vendor-operated repository, library and LMS platforms running under its
    name.


    This document was DERIVED by transcribing the live discovery document; it was not published by Boston
    University. Paths, methods and query arguments come from that document. Response schemas are NOT described
    there, so they are deliberately left unspecified rather than invented. Routes marked in their 200
    description as "not observed" returned HTTP 401 `rest_forbidden` to an unauthenticated caller on 2026-08-30.'
  contact:
    name: Boston University Information Services & Technology
    url: https://www.bu.edu/tech/
  license:
    name: Not stated by the provider
    identifier: NOASSERTION
  x-operator: institution
  x-provenance:
    generated: '2026-08-30'
    method: derived
    source: https://www.bu.edu/wp-json/ (live WordPress REST discovery document, HTTP 200, 389,199 bytes)
servers:
- url: https://www.bu.edu/wp-json
  description: Boston University WordPress REST API
tags:
- name: bu-access-control
  description: Boston University-authored namespace `bu-access-control/v1`.
- name: bu-alert
  description: Boston University-authored namespace `bu-alert/v1`.
- name: bu-blocks
  description: Boston University-authored namespace `bu-blocks/v1`.
- name: bu-cmb2-customizations
  description: Boston University-authored namespace `bu-cmb2-customizations/v1`.
- name: bu-navigation
  description: Boston University-authored namespace `bu-navigation/v1`.
- name: bu-prepress
  description: Boston University-authored namespace `bu-prepress/v1`.
- name: bu-site-manager
  description: Boston University-authored namespace `bu-site-manager/v1`.
- name: bu-slideshow
  description: Boston University-authored namespace `bu-slideshow/v1`.
- name: bu-tts
  description: Boston University-authored namespace `bu-tts/v1`.
- name: wordpress-core
  description: Core WordPress read routes verified live on www.bu.edu.
paths:
  /bu-access-control/v1:
    get:
      operationId: get-bu-access-control-v1
      summary: GET /bu-access-control/v1
      description: Route and arguments transcribed from the live WordPress REST discovery document at
        https://www.bu.edu/wp-json/ on 2026-08-30. Response bodies are not described by that document
        and are therefore left unspecified rather than invented.
      tags:
      - bu-access-control
      responses:
        '200':
          description: Successful response. Not probed; route declared by the live discovery document.
        '401':
          description: Not authenticated or not permitted (WordPress `rest_forbidden`).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route was found matching the URL and request method.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
      parameters:
      - name: namespace
        in: query
        required: false
        schema:
          type: string
          default: bu-access-control/v1
      - name: context
        in: query
        required: false
        schema:
          type: string
          default: view
  /bu-access-control/v1/delete-group:
    post:
      operationId: post-bu-access-control-v1-delete-group
      summary: POST /bu-access-control/v1/delete-group
      description: Route and arguments transcribed from the live WordPress REST discovery document at
        https://www.bu.edu/wp-json/ on 2026-08-30. Response bodies are not described by that document
        and are therefore left unspecified rather than invented.
      tags:
      - bu-access-control
      responses:
        '200':
          description: Successful response. Not probed; route declared by the live discovery document.
        '401':
          description: Not authenticated or not permitted (WordPress `rest_forbidden`).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route was found matching the URL and request method.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /bu-access-control/v1/get-group-usage:
    get:
      operationId: get-bu-access-control-v1-get-group-usage
      summary: GET /bu-access-control/v1/get-group-usage
      description: Route and arguments transcribed from the live WordPress REST discovery document at
        https://www.bu.edu/wp-json/ on 2026-08-30. Response bodies are not described by that document
        and are therefore left unspecified rather than invented.
      tags:
      - bu-access-control
      responses:
        '200':
          description: Successful response. Not probed; route declared by the live discovery document.
        '401':
          description: Not authenticated or not permitted (WordPress `rest_forbidden`).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route was found matching the URL and request method.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /bu-access-control/v1/get-groups:
    get:
      operationId: get-bu-access-control-v1-get-groups
      summary: GET /bu-access-control/v1/get-groups
      description: Route and arguments transcribed from the live WordPress REST discovery document at
        https://www.bu.edu/wp-json/ on 2026-08-30. Response bodies are not described by that document
        and are therefore left unspecified rather than invented.
      tags:
      - bu-access-control
      responses:
        '200':
          description: 'Successful response. Not observed: this route returned 401 to an unauthenticated
            caller on 2026-08-30.'
        '401':
          description: Not authenticated or not permitted (WordPress `rest_forbidden`).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route was found matching the URL and request method.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /bu-access-control/v1/update-group:
    post:
      operationId: post-bu-access-control-v1-update-group
      summary: POST /bu-access-control/v1/update-group
      description: Route and arguments transcribed from the live WordPress REST discovery document at
        https://www.bu.edu/wp-json/ on 2026-08-30. Response bodies are not described by that document
        and are therefore left unspecified rather than invented.
      tags:
      - bu-access-control
      responses:
        '200':
          description: Successful response. Not probed; route declared by the live discovery document.
        '401':
          description: Not authenticated or not permitted (WordPress `rest_forbidden`).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route was found matching the URL and request method.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /bu-alert/v1:
    get:
      operationId: get-bu-alert-v1
      summary: GET /bu-alert/v1
      description: Route and arguments transcribed from the live WordPress REST discovery document at
        https://www.bu.edu/wp-json/ on 2026-08-30. Response bodies are not described by that document
        and are therefore left unspecified rather than invented.
      tags:
      - bu-alert
      responses:
        '200':
          description: Successful response (verified live 2026-08-30).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/UnspecifiedPayload'
        '401':
          description: Not authenticated or not permitted (WordPress `rest_forbidden`).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route was found matching the URL and request method.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
      parameters:
      - name: namespace
        in: query
        required: false
        schema:
          type: string
          default: bu-alert/v1
      - name: context
        in: query
        required: false
        schema:
          type: string
          default: view
  /bu-alert/v1/start:
    post:
      operationId: post-bu-alert-v1-start
      summary: POST /bu-alert/v1/start
      description: Route and arguments transcribed from the live WordPress REST discovery document at
        https://www.bu.edu/wp-json/ on 2026-08-30. Response bodies are not described by that document
        and are therefore left unspecified rather than invented.
      tags:
      - bu-alert
      responses:
        '200':
          description: Successful response. Not probed; route declared by the live discovery document.
        '401':
          description: Not authenticated or not permitted (WordPress `rest_forbidden`).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route was found matching the URL and request method.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /bu-alert/v1/stop:
    post:
      operationId: post-bu-alert-v1-stop
      summary: POST /bu-alert/v1/stop
      description: Route and arguments transcribed from the live WordPress REST discovery document at
        https://www.bu.edu/wp-json/ on 2026-08-30. Response bodies are not described by that document
        and are therefore left unspecified rather than invented.
      tags:
      - bu-alert
      responses:
        '200':
          description: Successful response. Not probed; route declared by the live discovery document.
        '401':
          description: Not authenticated or not permitted (WordPress `rest_forbidden`).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route was found matching the URL and request method.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
    get:
      operationId: get-bu-alert-v1-stop
      summary: GET /bu-alert/v1/stop
      description: Route and arguments transcribed from the live WordPress REST discovery document at
        https://www.bu.edu/wp-json/ on 2026-08-30. Response bodies are not described by that document
        and are therefore left unspecified rather than invented.
      tags:
      - bu-alert
      responses:
        '200':
          description: Successful response. Not probed; route declared by the live discovery document.
        '401':
          description: Not authenticated or not permitted (WordPress `rest_forbidden`).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route was found matching the URL and request method.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /bu-blocks/v1:
    get:
      operationId: get-bu-blocks-v1
      summary: GET /bu-blocks/v1
      description: Route and arguments transcribed from the live WordPress REST discovery document at
        https://www.bu.edu/wp-json/ on 2026-08-30. Response bodies are not described by that document
        and are therefore left unspecified rather than invented.
      tags:
      - bu-blocks
      responses:
        '200':
          description: Successful response. Not probed; route declared by the live discovery document.
        '401':
          description: Not authenticated or not permitted (WordPress `rest_forbidden`).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route was found matching the URL and request method.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
      parameters:
      - name: namespace
        in: query
        required: false
        schema:
          type: string
          default: bu-blocks/v1
      - name: context
        in: query
        required: false
        schema:
          type: string
          default: view
  /bu-blocks/v1/collection:
    get:
      operationId: get-bu-blocks-v1-collection
      summary: GET /bu-blocks/v1/collection
      description: Route and arguments transcribed from the live WordPress REST discovery document at
        https://www.bu.edu/wp-json/ on 2026-08-30. Response bodies are not described by that document
        and are therefore left unspecified rather than invented.
      tags:
      - bu-blocks
      responses:
        '200':
          description: Successful response (verified live 2026-08-30).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/UnspecifiedPayload'
        '401':
          description: Not authenticated or not permitted (WordPress `rest_forbidden`).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route was found matching the URL and request method.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /bu-blocks/v1/customhtml:
    get:
      operationId: get-bu-blocks-v1-customhtml
      summary: GET /bu-blocks/v1/customhtml
      description: Route and arguments transcribed from the live WordPress REST discovery document at
        https://www.bu.edu/wp-json/ on 2026-08-30. Response bodies are not described by that document
        and are therefore left unspecified rather than invented.
      tags:
      - bu-blocks
      responses:
        '200':
          description: Successful response. Not probed; route declared by the live discovery document.
        '401':
          description: Not authenticated or not permitted (WordPress `rest_forbidden`).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route was found matching the URL and request method.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
    post:
      operationId: post-bu-blocks-v1-customhtml
      summary: POST /bu-blocks/v1/customhtml
      description: Route and arguments transcribed from the live WordPress REST discovery document at
        https://www.bu.edu/wp-json/ on 2026-08-30. Response bodies are not described by that document
        and are therefore left unspecified rather than invented.
      tags:
      - bu-blocks
      responses:
        '200':
          description: Successful response. Not probed; route declared by the live discovery document.
        '401':
          description: Not authenticated or not permitted (WordPress `rest_forbidden`).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route was found matching the URL and request method.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
    put:
      operationId: put-bu-blocks-v1-customhtml
      summary: PUT /bu-blocks/v1/customhtml
      description: Route and arguments transcribed from the live WordPress REST discovery document at
        https://www.bu.edu/wp-json/ on 2026-08-30. Response bodies are not described by that document
        and are therefore left unspecified rather than invented.
      tags:
      - bu-blocks
      responses:
        '200':
          description: Successful response. Not probed; route declared by the live discovery document.
        '401':
          description: Not authenticated or not permitted (WordPress `rest_forbidden`).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route was found matching the URL and request method.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
    patch:
      operationId: patch-bu-blocks-v1-customhtml
      summary: PATCH /bu-blocks/v1/customhtml
      description: Route and arguments transcribed from the live WordPress REST discovery document at
        https://www.bu.edu/wp-json/ on 2026-08-30. Response bodies are not described by that document
        and are therefore left unspecified rather than invented.
      tags:
      - bu-blocks
      responses:
        '200':
          description: Successful response. Not probed; route declared by the live discovery document.
        '401':
          description: Not authenticated or not permitted (WordPress `rest_forbidden`).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route was found matching the URL and request method.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
    delete:
      operationId: delete-bu-blocks-v1-customhtml
      summary: DELETE /bu-blocks/v1/customhtml
      description: Route and arguments transcribed from the live WordPress REST discovery document at
        https://www.bu.edu/wp-json/ on 2026-08-30. Response bodies are not described by that document
        and are therefore left unspecified rather than invented.
      tags:
      - bu-blocks
      responses:
        '200':
          description: Successful response. Not probed; route declared by the live discovery document.
        '401':
          description: Not authenticated or not permitted (WordPress `rest_forbidden`).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route was found matching the URL and request method.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /bu-blocks/v1/search:
    get:
      operationId: get-bu-blocks-v1-search
      summary: GET /bu-blocks/v1/search
      description: Route and arguments transcribed from the live WordPress REST discovery document at
        https://www.bu.edu/wp-json/ on 2026-08-30. Response bodies are not described by that document
        and are therefore left unspecified rather than invented.
      tags:
      - bu-blocks
      responses:
        '200':
          description: Successful response (verified live 2026-08-30).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/UnspecifiedPayload'
        '401':
          description: Not authenticated or not permitted (WordPress `rest_forbidden`).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route was found matching the URL and request method.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /bu-blocks/v1/yarpprelated:
    get:
      operationId: get-bu-blocks-v1-yarpprelated
      summary: GET /bu-blocks/v1/yarpprelated
      description: Route and arguments transcribed from the live WordPress REST discovery document at
        https://www.bu.edu/wp-json/ on 2026-08-30. Response bodies are not described by that document
        and are therefore left unspecified rather than invented.
      tags:
      - bu-blocks
      responses:
        '200':
          description: Successful response. Not probed; route declared by the live discovery document.
        '401':
          description: Not authenticated or not permitted (WordPress `rest_forbidden`).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route was found matching the URL and request method.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /bu-cmb2-customizations/v1:
    get:
      operationId: get-bu-cmb2-customizations-v1
      summary: GET /bu-cmb2-customizations/v1
      description: Route and arguments transcribed from the live WordPress REST discovery document at
        https://www.bu.edu/wp-json/ on 2026-08-30. Response bodies are not described by that document
        and are therefore left unspecified rather than invented.
      tags:
      - bu-cmb2-customizations
      responses:
        '200':
          description: Successful response. Not probed; route declared by the live discovery document.
        '401':
          description: Not authenticated or not permitted (WordPress `rest_forbidden`).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route was found matching the URL and request method.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
      parameters:
      - name: namespace
        in: query
        required: false
        schema:
          type: string
          default: bu-cmb2-customizations/v1
      - name: context
        in: query
        required: false
        schema:
          type: string
          default: view
  /bu-cmb2-customizations/v1/bu-post-chooser:
    get:
      operationId: get-bu-cmb2-customizations-v1-bu-post-chooser
      summary: GET /bu-cmb2-customizations/v1/bu-post-chooser
      description: Route and arguments transcribed from the live WordPress REST discovery document at
        https://www.bu.edu/wp-json/ on 2026-08-30. Response bodies are not described by that document
        and are therefore left unspecified rather than invented.
      tags:
      - bu-cmb2-customizations
      responses:
        '200':
          description: Successful response. Not probed; route declared by the live discovery document.
        '401':
          description: Not authenticated or not permitted (WordPress `rest_forbidden`).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route was found matching the URL and request method.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /bu-navigation/v1:
    get:
      operationId: get-bu-navigation-v1
      summary: GET /bu-navigation/v1
      description: Route and arguments transcribed from the live WordPress REST discovery document at
        https://www.bu.edu/wp-json/ on 2026-08-30. Response bodies are not described by that document
        and are therefore left unspecified rather than invented.
      tags:
      - bu-navigation
      responses:
        '200':
          description: Successful response (verified live 2026-08-30).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/UnspecifiedPayload'
        '401':
          description: Not authenticated or not permitted (WordPress `rest_forbidden`).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route was found matching the URL and request method.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
      parameters:
      - name: namespace
        in: query
        required: false
        schema:
          type: string
          default: bu-navigation/v1
      - name: context
        in: query
        required: false
        schema:
          type: string
          default: view
  /bu-navigation/v1/markup:
    get:
      operationId: get-bu-navigation-v1-markup
      summary: GET /bu-navigation/v1/markup
      description: Route and arguments transcribed from the live WordPress REST discovery document at
        https://www.bu.edu/wp-json/ on 2026-08-30. Response bodies are not described by that document
        and are therefore left unspecified rather than invented.
      tags:
      - bu-navigation
      responses:
        '200':
          description: Successful response. Not probed; route declared by the live discovery document.
        '401':
          description: Not authenticated or not permitted (WordPress `rest_forbidden`).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route was found matching the URL and request method.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /bu-navigation/v1/parents:
    get:
      operationId: get-bu-navigation-v1-parents
      summary: GET /bu-navigation/v1/parents
      description: Route and arguments transcribed from the live WordPress REST discovery document at
        https://www.bu.edu/wp-json/ on 2026-08-30. Response bodies are not described by that document
        and are therefore left unspecified rather than invented.
      tags:
      - bu-navigation
      responses:
        '200':
          description: 'Successful response. Not observed: this route returned 401 to an unauthenticated
            caller on 2026-08-30.'
        '401':
          description: Not authenticated or not permitted (WordPress `rest_forbidden`).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route was found matching the URL and request method.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /bu-prepress/v1:
    get:
      operationId: get-bu-prepress-v1
      summary: GET /bu-prepress/v1
      description: Route and arguments transcribed from the live WordPress REST discovery document at
        https://www.bu.edu/wp-json/ on 2026-08-30. Response bodies are not described by that document
        and are therefore left unspecified rather than invented.
      tags:
      - bu-prepress
      responses:
        '200':
          description: Successful response. Not probed; route declared by the live discovery document.
        '401':
          description: Not authenticated or not permitted (WordPress `rest_forbidden`).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route was found matching the URL and request method.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
      parameters:
      - name: namespace
        in: query
        required: false
        schema:
          type: string
          default: bu-prepress/v1
      - name: context
        in: query
        required: false
        schema:
          type: string
          default: view
  /bu-prepress/v1/event:
    get:
      operationId: get-bu-prepress-v1-event
      summary: GET /bu-prepress/v1/event
      description: Route and arguments transcribed from the live WordPress REST discovery document at
        https://www.bu.edu/wp-json/ on 2026-08-30. Response bodies are not described by that document
        and are therefore left unspecified rather than invented.
      tags:
      - bu-prepress
      responses:
        '200':
          description: Successful response (verified live 2026-08-30).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/UnspecifiedPayload'
        '401':
          description: Not authenticated or not permitted (WordPress `rest_forbidden`).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route was found matching the URL and request method.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /bu-site-manager/v1:
    get:
      operationId: get-bu-site-manager-v1
      summary: GET /bu-site-manager/v1
      description: Route and arguments transcribed from the live WordPress REST discovery document at
        https://www.bu.edu/wp-json/ on 2026-08-30. Response bodies are not described by that document
        and are therefore left unspecified rather than invented.
      tags:
      - bu-site-manager
      responses:
        '200':
          description: Successful response. Not probed; route declared by the live discovery document.
        '401':
          description: Not authenticated or not permitted (WordPress `rest_forbidden`).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route was found matching the URL and request method.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
      parameters:
      - name: namespace
        in: query
        required: false
        schema:
          type: string
          default: bu-site-manager/v1
      - name: context
        in: query
        required: false
        schema:
          type: string
          default: view
  /bu-site-manager/v1/snapshots/list:
    get:
      operationId: get-bu-site-manager-v1-snapshots-list
      summary: GET /bu-site-manager/v1/snapshots/list
      description: Route and arguments transcribed from the live WordPress REST discovery document at
        https://www.bu.edu/wp-json/ on 2026-08-30. Response bodies are not described by that document
        and are therefore left unspecified rather than invented.
      tags:
      - bu-site-manager
      responses:
        '200':
          description: Successful response. Not probed; route declared by the live discovery document.
        '401':
          description: Not authenticated or not permitted (WordPress `rest_forbidden`).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route was found matching the URL and request method.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /bu-site-manager/v1/snapshots/pull:
    p

# --- truncated at 32 KB (65 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/boston/refs/heads/main/openapi/boston-wordpress-api-openapi.yml