Projects, APIs, and Proxy
Projects and connections
Section titled “Projects and connections”A project groups app connections and linked API specifications. Use the + at the bottom of the sidebar to create one. Right-click a project to edit its name, icon, or color. With multiple projects, use Projects above the navigation to return to the project list; projects can be reordered there. Deleting a non-default project requires confirmation. The Default project can be renamed and styled, but cannot be deleted.
With one project, its header and editing actions remain visible, without a redundant back button. Choose from the icon library, predefined colors, or a custom color. Drag supported sidebar items to reorder them; order, inspector dimensions, and detail layout are remembered per project. Right-click the project to reset its sidebar order.
Assign new connections through Manage Connections. App assignments can be remembered, or applied to a single connection. Select a device in the center toolbar to choose the session shown in Network, Console, Timeline, and State. Other connected devices can keep capturing without mixing their data into that view.
Updated native SDKs remember each app installation across reconnects and launches, including on the same simulator. Uninstalling/clearing app data or erasing the simulator creates a new identity. A remembered device does not restore old captures or merge simultaneous sessions. Disconnected devices show their last-seen information and can be forgotten through their context menu.
OpenAPI and Swagger
Section titled “OpenAPI and Swagger”In API, use Import Spec to add a document from a file or URL, or link an existing document from the API library. Added specifications appear under API in the sidebar. Browse endpoints, inspect schemas, and view formatted request and response examples.
Captured traffic is matched against the originating project’s linked specifications. The Network inspector’s Contract tab shows the matched operation and supported validation issues, including their location, expected value or type, and observed value or type. Open in API takes you to the corresponding operation.
Settings → OpenAPI lists every imported API, including unlinked ones, and offers link/unlink actions. It also contains the automatic contract-checking toggle. API library and validation.
A request only receives useful validation when it can be matched and the relevant content is captured. An unmatched request is not a successful contract check. Unsupported schema features and missing capture data can limit validation; this is not a replacement for your API test suite.
Different environments
Section titled “Different environments”Use Spec Actions → Environments to add named environments with a base URL, bearer token, header/query API keys, and shared headers. Defaults propagate across Build & Send endpoints for that project/API, not into connected-device traffic. Environment URLs also participate in contract matching. Setup and inheritance rules.
Specifications can be linked into multiple projects. Their environment settings remain project-specific; updating the shared document affects every project that links to it.
Requests and API health
Section titled “Requests and API health”Build & Send opens a closeable request tab; it is also available by right-clicking an endpoint. Review the environment, parameters, headers, and body before sending. Requests execute from the Mac, not the selected device. Request tabs, saved requests, and history.
Health summarizes observed coverage and contract issues for the selected connection. An unobserved endpoint is a coverage gap, not proof that the endpoint is broken. Compare previews endpoint counts and runs only after Start Compare; it compares specifications rather than captured requests.
Search and investigation
Section titled “Search and investigation”Use the main toolbar Search (⇧⌘F) to search the current project. The default scope is the selected device; All Project Devices broadens search results only, not the main inspectors. Opening a result selects its device. ⌘F still focuses the current inspector’s filter.
Search uses bounded summaries of Network, Console, and Timeline rather than all payload bodies. Refresh to include new arrivals. Saved recordings is an explicit option; limits, partial results, and unreadable archives are shown instead of claiming exhaustive indexing.
Network, Console, and Timeline offer project-specific Saved Views for reusable filters. In Network, choose Use as Comparison Baseline, then Compare with Baseline… on another request to inspect differences within the selected device. Timeline references open related items, and Back (⌘[) returns to the prior investigation location.
Share This Request… and Add to Investigation prepare a small, reviewable export. Masking cannot recognize every private value. Review the privacy preview and confirm before exporting; this is not a replay recording. Capture storage and sharing.
The development proxy supports HTTP/HTTPS traffic capture, mock responses, request and response overrides, delays, and failures. It is off by default and listens on localhost unless you explicitly enable local-network access. Turning it on does not change system proxy settings or certificate trust for you.
Use Settings → Proxy, or the Proxy screen’s Settings button, for listener configuration and platform setup guides. HTTPS inspection requires trusting the separate Proxy CA on the development device. This is independent of Basic/Secure SDK mode. Remove proxy configuration and certificate trust when no longer needed, and keep interception limited to development devices and trusted networks.
Rules have explicit targets, such as a project, app, connection, proxy source, or all projects. Associate proxy sources with the appropriate connections before using project or app rules. Selecting another device in the toolbar does not retarget existing rules; inspect their scope before enabling them.