Import and inspect collections

Bring a specification into a collection, then verify the resulting endpoint list before building a contract or MCP server.

 
elva import spec openapi.yaml --dry-run
elva import spec openapi.yaml --name "Orders API"
elva import spec --url https://api.example.com/openapi.yaml
cat openapi.yaml | elva import spec - --name "Orders API copy"

Choose one source form. Files must be JSON or YAML and no larger than 10 MB. A local-file dry run validates locally without creating a collection; a URL dry run still fetches through Elva. URL sources must be reachable by the hosted service. Importing normally creates a new collection.

 
elva collection list
elva collection show "Orders API"
elva collection endpoints "Orders API" --method get
elva --collection "Orders API" import spec openapi.yaml --update

The --update option replaces the selected collection's spec and retains the previous spec as a restorable version. Review the endpoint count after any import. A stored document can still yield zero endpoints; a successful command alone is not an endpoint-coverage check.

 
elva import postman "Orders API"

Use the Postman command with the collection's exact name or ID. Supply its API key when prompted or through ELVA_POSTMAN_API_KEY. OpenAPI file import does not accept a Postman collection file. If import fails, check file format, size, URL reachability, duplicate names, and access to the selected workspace.