PRACTICAL API GUIDES

API discovery guides.
Understand the traffic.

Start with a request you need to understand. These guides cover finding endpoints, tracing data between calls, generating documentation and reviewing changes over time.

01 / INVESTIGATE A WORKFLOW

Find the calls.
Follow the data.

Use Chrome to inspect individual exchanges, then build a repeatable investigation of an undocumented API.

02 / DOCUMENT WHAT YOU OBSERVE

Choose the format
that fits the traffic.

HTTP requests, GraphQL types and live messages describe different parts of an application. Learn what each export contains and where its evidence stops.

03 / REVIEW CHANGES

Compare the next capture.

A new response shape may signal an API change or a gap in the earlier capture. Learn how to tell the difference.

SCHEMA DRIFT

What changed
between two captures?

Build comparable baselines, try two downloadable OpenAPI examples and review the differences that could affect your integration.

Read the schema drift guide

QUESTIONS & ANSWERS

Frequently asked questions

Which guide should I read to find an API behind a website?

Start with the Chrome endpoint-discovery guide for a focused request inspection. Continue with the API reverse engineering guide when you need to investigate several workflows and organize the resulting documentation.

Which guide explains values passed between API calls?

The request-chaining guide follows identifiers from responses into later requests. It covers manual investigation, apispy Flow and a worked Postman example.

Where can I learn to compare API behavior over time?

The schema drift guide explains how to collect comparable captures, compare OpenAPI exports and investigate false alarms caused by permissions, records or incomplete coverage. It includes two downloadable example documents.