api-recon-and-docs

API reconnaissance and documentation review enumerates undocumented endpoints, optional fields, and hidden parameters by extracting schemas from available documentation. This maps the target's actual attack surface, validating reachable REST, GraphQL, and mobile-style routes before deeper analysis.

Detecting deprecated API versions involves applying version and drift awareness to identify old or alternate version paths, including legacy mounts and mobile-style routes. This process reveals active legacy endpoints that expand the target's exploitable surface area for security testing.

Schema and parameter extraction pulls role-specific request examples and undocumented fields directly from OpenAPI and GraphQL schemas. This identifies flexible properties and derivable role- or tenancy-differentiated request patterns that signal exploitable authorization behavior.

API reconnaissance works across REST, GraphQL, and mobile targets by enumerating documentation-backed paths and entrypoints. It extracts schemas and maps parameters across these differing architectures to build a precise testing plan for subsequent security steps.

Schema extraction is required before authorization testing to map optional fields, version drift, and undocumented inputs that increase testing coverage. Uncovering these hidden schema elements ensures you validate which versions and parameters actually matter for business-logic analysis.