Postman collections and Scripted Check scripts are not uploaded to the ASM platform. Instead, they are managed through a repository which is created by the end user. This repository is set up from within the “Manage > Repository Profiles” page:
Users can view and add new Repository Profiles from this page. A Repository Profile holds a repository URL and authentication details to the repository so users do not have to add that information every time they set up a check.
To create a new Repository Profile, click on the “New Profile” button, select a Type, and click “Create Profile”:
Repository Configuration Examples
Add your project’s base Repository URL when you create a Repository Profile. You will have the option to add a more specific file path when you create a Scripted or Postman check.
GithubAdd a base repository URL. You will add a more specific file path when you create a Postman or Scripted check - just add the desired repository profile with the format https://github.com/user/repository, as shown in the screenshot |  |
HTTPIt is possible to store files on an HTTP server and retrieve them with HTTP Basic authentication. Enter the base path to the repository within the repository profile; you will add a more specific file path when you create a Postman or Scripted check. |  |
BitbucketFor Bitbucket Cloud/DC/Server Users enter the Bitbucket:
|  |
Azure DevOpsFor Azure DevOps Users enter the Azure DevOps:
|  The DevOps Repository URL might look different depending on the configuration or the installation of the Azure DevOps server. Some typical valid TFS project URLs are:
|
Set Up a Repository File
Step | Screenshot |
|---|---|
Step 1: Click the New Profile button | |
Step 2: Name the profile, select the repository type (e.g., GitHub) in the drop-down list provided, and click “Create Profile”. |  |