Endpoint Import and Discovery
Import endpoints from OpenAPI/Swagger and detect changes over time so your test suite stays aligned with the contract and avoids drift.
Overview
Endpoint import and discovery is how you keep your project aligned with the API contract. Instead of manually creating endpoints one by one, you can import them from a spec and then continuously detect changes as the API evolves.
Import endpoints (recommended)
Most teams import endpoints from an OpenAPI/Swagger spec:
- upload
openapi.yaml/openapi.json - link to a published spec URL
- sync from a repo as part of CI
After import, organize endpoints into features and generate baseline tests.
Related: Feature management and AI-generated tests.
Discovery and change detection
As your API changes, discovery helps you detect:
- newly added endpoints
- removed/deprecated endpoints
- method/path changes
- schema changes that can break tests or clients
This is where “shift left” wins: you catch contract drift early, before it reaches production.
Best practices
- Treat your spec as the source of truth.
- Review diffs after imports and validate key endpoints.
- Keep environment configuration stable so import results are reproducible.
Related articles
Related articles
- Endpoint Management · Product documentation
- Endpoint Validation and Testing · Product documentation
Next steps
- Getting started · Install + connect your spec
- Configuration fundamentals · Stabilize runs
- Initial configuration · Users, licensing, projects
- Release notes · Updates and fixes
Still stuck?
Tell us what you’re trying to accomplish and we’ll point you to the right setup—installation, auth, or CI/CD wiring.