For Developers & AI Agents

WowMakers Developer Resources & API

A read-only JSON mirror of what's already public on this site — our services, case studies, and blog posts — plus the OpenAPI spec that describes it.

Every endpoint below returns already-public content in JSON — nothing here requires an API key, and nothing here is written back to. It exists so an agent or script can read the same information a person sees on the site, without having to parse HTML.

Available endpoints

EndpointMethodDescription
/openapi.jsonGETFull OpenAPI 3.1 specification for every endpoint below.
/api/v1/services.jsonGETWowMakers' service lines (design, video, product, web).
/api/v1/case-studies.jsonGETPortfolio case studies — client, industry, service category.
/api/v1/blog-posts.jsonGETRecent blog posts — up to the 50 newest, newest first.

Example request

curl https://www.wowmakers.com/api/v1/case-studies.json

Errors

A request to a path under /api/v1/ that doesn't match a real endpoint returns a JSON body with a real 404 HTTP status, not an HTML error page:

{
  "error": {
    "code": "not_found",
    "status": 404,
    "message": "No API resource exists at this path.",
    "resolution": "See /openapi.json for the list of available endpoints, or /llms.txt for agent guidance."
  }
}

Markdown for agents

Prefer plain text over HTML? Send Accept: text/markdown on a request to any page on this site (this one included) and, where a markdown copy exists, you'll get it back instead — same URL, no separate endpoint to remember.

Quick start

  1. 1

    Read /openapi.json

    It lists every path, method, and response shape below.

  2. 2

    GET the endpoint you need

    No auth header, no API key — a plain GET is enough.

  3. 3

    Parse the JSON

    Every response is a flat object; see /openapi.json for the exact schema.

Questions

Something not working, or need something this API doesn't cover yet? Email hello@wowmakers.com.