Frequently Asked Questions

Password reset is handled by your system administrator. Contact them to have your password reset. Once you receive a temporary password, go to Account Settings → Security → Change Password to set a new one.

No. Your email is used as a unique identifier and cannot be changed after registration. If you need a different email address, a new account will be required.

Yes. The system may be running in invite-only mode, meaning new users can only join by accepting an invitation link sent by a team admin. Contact your team admin to receive an invite.

Invitation links expire after 30 days. Ask a team admin to resend it from Team Settings → Pending Invitations → Resend.

This is not recommended. Each person should have their own account so that activity logs, session tracking, and collaboration features work correctly. Team members can be invited to share access to the same workspace.

They are the same thing. The terms are used interchangeably. Each workspace is a shared space containing collections, environments, and history that all members can access.

Yes. You can be a member of multiple workspaces. Use the Team dropdown in the top navigation bar to switch between them instantly.

• Viewer — can browse collections and requests, but cannot send requests or make changes.
• Member — can send requests, create, edit, and delete collections and requests.
• Admin — everything a Member can do, plus invite/remove members, change roles, and rename or delete the workspace.

Your personal access is revoked but the collections remain in the workspace for the remaining members. Nothing is deleted.

No. Deleting a workspace permanently removes all collections, requests, and environments inside it. There is no undo or recovery. Always double-check before confirming a workspace deletion.

No. Only another Admin in the same workspace can change your role.

With the request open in a tab, click the Save button. A dialog will ask for a name and which collection to save it into. Names must be unique within the same collection.

Deleted requests cannot be recovered directly. However, if you sent that request before deleting it, check the History tab in the sidebar — you may be able to find it there and re-save it to a collection.

Not within the same collection or sub-folder — names must be unique at each level. You can have identically named requests if they are in different collections or sub-folders.

Drag the request from its current location in the sidebar and drop it onto the target collection or sub-folder.

Someone else on your team has modified that request since you opened it. Click the icon to reload the latest version. Any unsaved local changes will be replaced by the updated version.

Another team member deleted that request while you had it open. You can still read the tab content, but you cannot save it — the request no longer exists in the collection.

While a request is in flight the Send button changes to a Cancel button. Click it to abort the request immediately.

A status of 0 means the request never reached the server. Common causes: the server is unreachable, the URL is incorrect, there is a network error, or the request was cancelled. Check the Console panel at the bottom of the screen for more detail.

In the Body tab, select binary to upload a single file as the entire body. For multipart forms that mix text fields and a file, use form-data and add a file-type row to the table.

Global variables are always available regardless of which environment is active — useful for values that never change between environments.

Environment variables are specific to a chosen environment (e.g., Development, Staging, Production). If the same variable name exists in both globals and the active environment, the environment value takes priority.

Check these three things:

1. An environment is selected in the Environment dropdown. "No Environment" means only globals are applied.
2. The variable name in your request exactly matches the name defined in the environment. Names are case-sensitive.
3. The variable has a non-empty value in the active environment.

Yes. You can use {{variableName}} in the URL, headers, query parameters, body (including JSON), and authentication fields. The value is substituted from the active environment before the request is sent.

Yes. Environments are stored at the workspace level and are visible to all members of that workspace. Be careful about storing sensitive secrets (such as production API keys) in shared environments.

Yes. Use pm.environment.set("variableName", value) in a pre-request script to dynamically set a variable before the request fires. This is useful for computed values like timestamps or generated tokens.

No. Configure authentication once at the collection level and set all requests inside to inherit. If the credentials ever change, you only update them in one place.

When a request's auth type is set to inherit, it looks at its parent collection for auth settings. If the parent collection is also set to inherit, it looks at the grandparent, and so on up the hierarchy. If no parent has explicit auth configured, no authentication is applied.

If the token is stored as an environment variable (e.g., {{authToken}}), update the variable value in the Environment Manager — all requests referencing that variable immediately use the new value. This is the recommended approach. If the token is hardcoded in each request's Auth tab, you will need to update each one individually.

In the Auth tab of a request (or in the collection's Authorization modal), select OAuth 2.0 and fill in the token URL, client ID, client secret, and any required scopes. The application handles the token request and attaches the result to your request automatically.

Sequential — requests run one after another in order. You can set a delay between them. Use this when requests depend on each other (e.g., create a resource, then fetch it).

Parallel — all selected requests are sent simultaneously. Use this for independent requests or load testing.

Yes, using test scripts. In the Tests tab of the first request, save a value from the response to an environment variable:
pm.environment.set("userId", pm.response.json().id);
The next request can then reference {{userId}} in its URL or body.

Yes. In the runner setup modal, uncheck requests you want to skip. Use the None button to deselect everything first, then individually check only the requests you want to run.

Once a run completes, click the Export button in the results panel to download the results. Previous run results are also accessible from the Runs tab in the sidebar.

Yes. Export your collection from Postman as a JSON file, then use Import → Postman Collection in the navigation bar. Collections, sub-folders, requests, headers, params, body, and authentication settings are all imported.

Yes. Use Import → Postman Environment to bring in a Postman environment JSON file. All variables are imported and the environment is added to your list.

Yes. The export includes the collection structure, requests, headers, params, body, authentication settings, and scripts (pre-request and tests). Saved response snapshots are stored separately and are not included in collection exports.

You can export the collection as a JSON file and send it to them — they can import it into their own workspace. For ongoing real-time collaboration, invite them to your workspace instead.

Click your name in the top-right corner and choose Subscription. Your current plan is shown at the top of the page. This option is only visible to Organization Owners and Super Admins.

The pop-up explains which limit was reached and what your current plan allows. Click View Subscription inside the pop-up to review your plan details. Contact your administrator to discuss upgrading.

Plans can limit: Team Members, Workspaces/Teams, Collections, Environments, Request History entries, Monthly API Calls, and Saved Responses. Your Subscription page shows current usage vs. the limit for each resource.

Yes. The monthly API call counter resets at the start of each calendar month. The Monthly API Call History table on the Subscription page shows usage by month for the past 12 months.

Red means you are at 90% or more of a limit — you have not hit the ceiling yet, but you are close. Yellow appears at 70%+. Take note and consider reducing usage or upgrading your plan before the limit is reached.

The Subscription page is only accessible to Organization Owners and the Master Super Admin. Regular team members and team admins do not have access to billing information.

Organization Owners and the Master Super Admin. Regular members and team admins cannot access it.

Yes, this is by design. As an Organization Owner, the Admin Dashboard is scoped to your organization only. The Master Super Admin is the only account that can view data across all organizations.

The dashboard automatically refreshes all data every 30 seconds. Switching between tabs also triggers an immediate reload.

Yes. In the Session Logs tab you can export as CSV, Excel (XLSX), or PDF. In the API Activity tab, Excel and PDF exports are available. All exports respect any active filters (user, date range, etc.).

Yes. Click the sun/moon icon in the navigation bar (or top-right corner on the login/register page) to toggle between dark and light mode. Your preference is saved and restored automatically on your next visit.

Yes. With a request open, use the code generation option to get a ready-to-use snippet in 11 languages: cURL, JavaScript (fetch & Axios), Python, PHP (cURL & Guzzle), Node.js, Go, Java, C#, and Ruby.

No. An internet connection is required to reach your API endpoints and to sync collections with your team in real time.

Shortcut	Action
Ctrl + T	Open a new request tab
Ctrl + Enter	Send the current request

Open the Console tab at the bottom of the workspace. Errors from scripts and failed requests are logged there with details. Look for messages from pre-request or test scripts, or network-level errors from failed requests. Use the search bar inside the Console to filter messages.

A comprehensive user manual is available in the instructions/manual.md file within the application's repository. Contact your system administrator for access.