Import and Discover Endpoints
Import endpoints from OpenAPI/Swagger sources, map them to features, and detect endpoint changes as your API evolves.
Overview
Endpoint import and discovery keeps your project aligned with the API contract. Instead of creating endpoints one by one, import from your API specification and refresh discovery when the spec changes.
Use this flow from the project or feature endpoint area via Import endpoint / discovery actions.
Import endpoints
You can import endpoints from an OpenAPI/Swagger source:
- Upload file:
openapi.yamloropenapi.json - Use URL: hosted OpenAPI/Swagger endpoint
- Sync source: refresh from repo/CI-managed specs when available
After import, endpoints appear under selected features. From there, open feature endpoint lists to review method/path coverage.
Verify discovery output
Review imported output before moving to testing:
- confirm endpoint count by feature
- confirm HTTP methods (
GET,POST,PUT,DELETE, etc.) - confirm expected endpoint paths and descriptions
Then continue to Endpoint management to select a specific endpoint and open its test-case screen.
Discovery and change detection
As APIs evolve, rerun discovery to detect:
- new endpoints
- removed/deprecated endpoints
- method/path changes
- schema changes that can affect generated tests
Best practices
- Treat your spec as the source of truth.
- Review diffs after each import and validate critical endpoints first.
- Keep environment configuration stable so import results are reproducible.
Related articles
Related articles
- Select, Navigate and Manage Endpoints · Product documentation
- Validate Endpoints · 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.