Home
DESIGN.mdStar on GitHub

Design, Build, and Test APIs
All in One Place

An all-in-one API platform — design, debug, automated testing, docs and mocking in a single tool.

Apidog = Postman + Swagger + Stoplight + ReadMe + JMeter + Mock…
Colors
Brand · the blue→cyan gradient
Surfaces · light-first
Text
Functional signals · HTTP method & status, not brand
Typography
Poppins / 700
Display · 54px
Design, Build, and Test APIs
Poppins
Poppins / 600
Section heading · 30px
One workflow for your entire API lifecycle
Poppins
Inter / 400
UI · body · 15px
Every request, response and its schema, checked in one place.
Inter
JetBrains Mono / 400
Code · response · 12.5px
GET /v1/users/{id} → 200 OK · 84ms
JetBrains Mono
Signature · Design-first API client
User Service API
Production
Endpoints
GET
Params0 Headers2 Body
Press  Send  to run the request & validate the response against its designed schema.
Pick an endpoint, press Send. The response returns and is validated against the endpoint's designed schema — try GET /users/{id}, whose live response drifted from the spec. Deterministic.
Components
Buttons
HTTP method chips
GET POST PUT PATCH DELETE
Request URL
Radius
12 card
9 btn
7 chip
pill
Guardrails
Do
Keep a bright white / pale-blue canvas with deep navy ink — light is primary.
Use one blue→cyan gradient (#1A66FF→#00AAFF) for mark, hero, Send and active states.
Set marketing display in Poppins; keep dense product UI in Inter, code in JetBrains Mono.
Make schema validation visible — responses checked against the designed spec (the design-first edge).
Color HTTP methods & statuses as functional signals only.
Don't
Present Apidog as just a request-runner — it's design + test in one.
Introduce a competing brand hue; blue→cyan is the only brand family (navy is the ink).
Set body or dense tables in Poppins — the rounded display is for headings/wordmark.
Make the gradient neon or muddy — clean royal-blue warming to cyan.
Swap the X-and-bone mark for a generic API / globe icon.