Help Center
Browse articles in this category, or use search to jump to a specific task.
8 articles.
Create a project — the workspace holding your endpoints, tests, environments, and results. Covers naming, scoping decisions, and what to do immediately after.
Import an OpenAPI, WSDL, or GraphQL definition into your project by file upload or URL, with Auto-Detect, then confirm the endpoints that were discovered.
Navigate the project → feature → endpoint tree in the sidebar: search and filter projects, open features, select endpoints, and reach the test workflow.
Set base URLs per environment, authentication profiles, default headers, change detection, and AI generation options — the settings that make a project run.
Most APIs refuse a request that does not prove who is calling. In Shift-Left Studio you describe how to prove it once, in an authentication profile, and every test, pack, workflow and performance run in the project uses it.
Many APIs sit behind an identity provider such as Microsoft Entra ID, Okta, Auth0, Keycloak or Google, and only accept a token issued to a signed-in user. You cannot get that token with a client ID and secret alone.
Some APIs sign you in with a sequence of calls they designed themselves. A typical example: post a username and password, receive a one-time code by SMS or email, post the code back, and receive a bearer token plus a refresh token.
Import a Postman collection (v2.0 or v2.1) into a project: requests become endpoints and tests, pm.test assertions are converted, and anything that needs review is flagged.
