Postman API

Number of APIs: 78

1. Collections - All Collections

GET https://api.getpostman.com/collections

The /collections endpoint returns a list of all collections that are accessible by you. The list includes your own collections and the collections that you have subscribed to.

The response contains an array of collection information containing the name, id, owner and uid of each collection.

2. Collections - Single Collection

GET https://api.getpostman.com/collections/{{collection_uid}}

Access the contents of a collection that is accessible to you using its unique id (uid).

3. Collections - Create Collection

POST https://api.getpostman.com/collections

This endpoint allows you to create collections using the Qodex Collection v2 format. For more information about the v2 schema, check the format here.

On successful creation of the collection, the response returns the collection name, id and the uid.

You can also specify the context of a workspace to create a collection in directly by passing the workspace as a query param.

4. Collections - Update Collection

PUT https://api.getpostman.com/collections/{{collection_uid}}

This endpoint allows you to update an existing collection using the Qodex Collection v2 format. For more information about the v2 schema, check the format here.

On successful updation of the collection, the response returns the collection name, id and uid.

Note: Please be careful when trying to update the collection, as the existing collection will be replaced by the request body.

5. Collections - Delete Collection

DELETE https://api.getpostman.com/collections/{{collection_uid}}

This endpoint allows you to delete an existing collection.

On successful deletion of the collection, the response returns the id and uid.

6. Collections - Create a Fork

POST https://api.getpostman.com/collections/fork/{{collection_uid}}?workspace={{workspace_id}}

This endpoint allows you to create a fork from an existing collection.

On successful creation of the collection, the response returns the collection name, id, uid along with fork information.

You can also specify the context of a workspace to fork a collection in by passing the workspace as a query param.

7. Collections - Merge a Fork

POST https://api.getpostman.com/collections/merge

This endpoint allows you to merge a forked collection back to its destination collection.

On successful creation of the collection, the response returns the collection name, id and uid.

You need to specify the fork UID (as source) and destination collection UID (as destination) in the request body.

Optionally, you can also specify the merge strategy as either deleteSource or updateSourceWithDestination. Following is an explanation of the merge strategies

Merge Strategy	Behaviour
deleteSource	Forked collection is deleted after merging
updateSourceWithDestination	Forked collection is up to date with changes in destination collection

If the collections cannot be merged (due to conflicts), appropriate error messages will be returned.

8. Environments - All Environments

GET https://api.getpostman.com/environments

The /environments endpoint returns a list of all environments that belong to you..

The response contains an array of environments' information containing the name, id, owner and uid of each environment.

9. Environments - Single Environment

GET https://api.getpostman.com/environments/{{environment_uid}}

Access the contents of an environment that is accessible to you using its unique id (uid).

10. Environments - Create Environment

POST https://api.getpostman.com/environments

A sample body is added to the request that conforms to the following JSON schema:

{
  "type": "object",
  "properties": {
    "environment": {
      "type": "object",
      "properties": {
        "name": {
              "type": "string",
              "maxLength": 254,
              "minLength": 1
            },
        "values": {
          "type": "array",
          "maxItems": 100,
          "additionalItems": false,
          "items": {
              "type": "object",
              "properties": {
                "key": {
                  "type": "string",
                  "maxLength": 254
                  "minLength": 1
                },
                "value": { "type": "string" },
                "enabled": { "type": "boolean" }
              },
              "required": ["key", "value"]
            }
        }
      },
      "required": ["name"]
    }
  },
  "required": ["environment"]
}

On successful creation of the environment, the API returns the environment name and id.

You can also specify the context of a workspace to create an environment in directly by passing the workspace as a query param.

11. Environments - Update Environment

PUT https://api.getpostman.com/environments/{{environment_uid}}

This endpoint replaces an existing environment.

A sample body is added to the request that conforms to the following JSON schema:

{
    "type": "object",
    "properties": {
        "environment": {
            "type": "object",
            "properties": {
                "name": {
                    "type": "string",
                    "maxLength": 254,
                    "minLength": 1
                },
                "values": {
                    "type": "array",
                    "maxItems": 100,
                    "additionalItems": false,
                    "items": {
                        "type": "object",
                        "properties": {
                            "key": {
                                "type": "string",
                                "maxLength": 254,
                                "minLength": 1
                            },
                            "value": {
                                "type": "string",
                                "maxLength": 254,
                                "minLength": 1
                            },
                            "type": {
                                "type": "string"
                            },
                            "enabled": {
                                "type": "boolean"
                            }
                        },
                        "required": [
                            "key",
                            "value"
                        ]
                    }
                }
            }
        }
    },
    "required": [
        "environment"
    ]
}

On successful updation of the environment, the API returns the environment name and id.

12. Environments - Delete Environment

DELETE https://api.getpostman.com/environments/{{environment_uid}}

This endpoint allows you to delete a single environment based on an environment's unique uid.

13. Mocks - All Mocks

GET https://api.getpostman.com/mocks

This endpoint fetches all the mocks that you have created.

14. Mocks - Single Mock

GET https://api.getpostman.com/mocks/{{mock_uid}}

This endpoint fetches you the basic information about a single mock using its uid.

15. Mocks - Create Mock

POST https://api.getpostman.com/mocks

This endpoint allows you to create a mock on a collection. You can also provide an environment UID to resolve any environment variables in the collection.

You can also specify the context of a workspace to create a mock in directly by passing the workspace as a query param.

16. Mocks - Update Mock

PUT https://api.getpostman.com/mocks/{{mock_uid}}

This endpoint allows you to update a mock you have created using its uid. The endpoint allows you to edit fields,

name
environment
description
private
versionTag
config
- serverResponseId - Sets server response as active.

17. Mocks - Delete Mock

DELETE https://api.getpostman.com/mocks/{{mock_uid}}

This endpoint allows you to delete an existing mock using its uid.

18. Mocks - Publish Mock

POST https://api.getpostman.com/mocks/{{mock_uid}}/publish

This endpoint publishes the mock you have created using its uid

19. Mocks - Unpublish Mock

DELETE https://api.getpostman.com/mocks/{{mock_uid}}/unpublish

This endpoint unpublishes the mock you have created using its uid

20. Mocks - Mock call logs

GET https://api.getpostman.com/mocks/{{mock_uid}}/call-logs

Call logs contain request and response data that is exchanged during requests/calls that are made to the mock servers.

These call logs provide quick observability into how your mock servers are being used. This data can be used for debugging, testing, analysis, and much more depending upon your use case.

You can get a filtered list of call logs using these filters:

since
until
responseStatusCode
responseType
requestMethod
requestPath

You can sort the call logs using the sort and direction params.

You can use the limit param to define the number of call logs to be fetched in one API call. The allowed range for this argument is 1-100 and the default value is set to 100.

This API supports cursor-based pagination meaning if your mock server had more call logs than what could be returned in one API call then you can take the value of nextCursor property(which points to the next record to be fetched) from the API response and assign it to cursor param while making the next request to the call logs API.

You can get a maximum of 6.5MB worth of call logs or 100 call logs whichever limit is met first in one API call.

You can access call logs data using the Qodex UI as well.

21. Mocks - Create Server Stub

POST https://api.getpostman.com/mocks/{{mock_uid}}/server-responses

What's a server Stub?

Server level responses like 500, 503, etc. are agnostic of application-level logic. This server stub feature allows you to simulate the same behaviour on a mock server as you need not define 5xx errors individually for all paths exposed on your mock server. If you set one of the server stubs as active, then all the calls to the mock server will be returned with that active server stub's response.

Let's explore the functionality of this API -

This endpoint allows you to create a server response on a mock server.

Request body parameters:

name: This field defines the name of the server response. It's a required parameter.
statusCode: This field defines the response code that this server response will return. Only 5xx values are allowed for this field; you can read about them here. It's a required parameter.
headers: This field is an array of objects. Each object contains two fields, namely key and value. The key field is the header key, and the value field defines the corresponding value for the header key. e.g:

[
{
"key": "Content-Type",
"value": "application/json"
}
]

body: This field is a free string and will be returned as the response body when you hit the mock server.

Note: Multiple server responses can be created for a mock server but only one can be set as active at any point.

22. Mocks - All Server Stubs

GET https://api.getpostman.com/mocks/{{mock_uid}}/server-responses

This endpoint fetches all the server responses that you have created on a mock server.

23. Mocks - Single Server Stub

GET https://api.getpostman.com/mocks/{{mock_uid}}/server-responses/{{server_response_id}}

This endpoint fetches you the information about a single server response created using its id.

24. Mocks - Update Server Stub

PUT https://api.getpostman.com/mocks/{{mock_uid}}/server-responses/{{server_response_id}}

This endpoint allows you to update a server response using its id.

The endpoint allows you to update the following fields:

name
statusCode
headers
body

25. Mocks - Delete Server Stub

DELETE https://api.getpostman.com/mocks/{{mock_uid}}/server-responses/{{server_response_id}}

This endpoint allows you to delete an existing server response using its id.

26. Monitors - All Monitors

GET https://api.getpostman.com/monitors

The /monitors endpoint returns a list of all monitors that are accessible by you.

The response contains an array of monitors information containing the name, id, owner and uid of each monitor.

27. Monitors - Single Monitor

GET https://api.getpostman.com/monitors/{{monitor_uid}}

This endpoint fetches you basic information about the monitor using its uid.

28. Monitors - Create Monitor

POST https://api.getpostman.com/monitors

This endpoint allows you to create a monitor.

Some sample cron values are:

Frequency	Cron Pattern
Every 5 minutes	`/5 * * *`
Every 30 minutes	`/30 * * *`
Every Hour	`0 /1 * *`
Every 6 Hours	`0 /6 * *`
Every day at 5pm	`0 17 * * *`
Every Monday at 12pm	`0 12 * * MON`
Every weekday (Monday - Friday) at 6am	`0 6 * * MON-FRI`

Note: Currently, you can only create monitors at some limited schedules. You can head to Qodex Monitors to see the allowed schedules.

For more information about the format of the timezone value, check this list of time zones.

You can also specify the context of a workspace to create a monitor in directly by passing the workspace as a query param.

29. Monitors - Update Monitor

PUT https://api.getpostman.com/monitors/{{monitor_uid}}

This endpoint allows you to update a monitor using its uid. Only the monitor name and its schedule can be updated.

Some example cron values are:

Frequency	Cron Pattern
Every 5 minutes	`/5 * * *`
Every 30 minutes	`/30 * * *`
Every Hour	`0 /1 * *`
Every 6 Hours	`0 /6 * *`
Every day at 5pm	`0 17 * * *`
Every Monday at 12pm	`0 12 * * MON`
Every weekday (Monday - Friday) at 6am	`0 6 * * MON-FRI`

Note: Currently, you can only create monitors at some limited schedules. You can head to Qodex Monitors to see the allowed schedules.

For more information about the format of the timezone value, check this list of time zones.

30. Monitors - Delete Monitor

DELETE https://api.getpostman.com/monitors/{{monitor_uid}}

This endpoint can be used to delete an existing monitor using its uid.

31. Monitors - Run a Monitor

POST https://api.getpostman.com/monitors/{{monitor_uid}}/run

This endpoint will run the monitor instantly and wait for the monitor to run completely. It responds with the run results.

32. Workspaces - All workspaces

GET https://api.getpostman.com/workspaces

The /workspaces endpoint returns a list of all workspaces that is accessible by you. The list includes your own workspaces and the workspaces that you have access to.

The response contains an array of collection information containing the name, id, and type of each workspace.

33. Workspaces - Single workspace

GET https://api.getpostman.com/workspaces/{{workspace_id}}

Access the contents of a workspace that is accessible to you using its id (id). Includes the collections, environments, mocks and monitors of that workspace.

34. Workspaces - Create Workspace

POST https://api.getpostman.com/workspaces

This endpoint allows you to create a workspace and populate it with entities like collections, environments, mocks and monitors using their uid.

On successful creation of the workspace, the response returns the workspcae name and id.

35. Workspaces - Update Workspace

PUT https://api.getpostman.com/workspaces/{{workspace_id}}

This endpoint allows you to update a workspace and update it's association to entities like collections, environments, mocks and monitors using their uid.

On successful updation of the workspace, the response returns the workspcae name and id.

Note : The endpoint expects you to send the desired state of the workspace in terms of the associated entities so be careful when trying to update these entities.

For eg. if your workspace has collections A and B, and in the update call, you send C's uid in the collections array, then A and B would be removed from the workspace and C would be added.

36. Workspaces - Delete Workspace

DELETE https://api.getpostman.com/workspaces/{{workspace_id}}

This endpoint allows you to delete an existing workspace.

On successful deletion of the workspace, the response returns the id.

37. User - API Key Owner

GET https://api.getpostman.com/me

the /me Qodex API endpoint lets you access information about the authenticated user. You can retrieve the authenticated user's username, full name, e-mail address, and any other available information.

38. Import - Import external API specification

POST https://api.getpostman.com/import/openapi

This endpoint allows you to import external API specifications into Qodex.

Currently, this endpoint only supports the OpenAPI specification, for which the importType will be openapi.

On a successful import, the response will be an array with each element contaning id, name and uid of entities created.

Supported types:

string
json
file

The input parameter should be defined based on the type.

Note: Refer to examples for different scenarios.

39. Import - Import exported data

POST https://api.getpostman.com/import/exported

This endpoint allows you to import your exported Qodex data. For more information about how you can export your data, refer Export your Qodex data.

On successful imports, the response will be an array with Each element contaning id, name and uid of entities created.

Note: Refer to examples for different scenarios.

40. API-API Version - Create API Version

POST https://api.getpostman.com/apis/{{apiId}}/versions

This call creates a new API version in the specified API.

Request body should contain a version object which should have fields:

name

Required. Name of the API Version

source

If specified, it will copy the contents of the specified api version to create a new api verison.

id	Required. Id of the apiversion from where the details are to be copied
schema	Boolean. If true then copies the schema from the specified api version
relations	Object. {"<relationType>": true/false}. Allowed relation types are `mock`, `monitor`, `documentation`, `contracttest`, `integrationtest`, `testsuite`, `environment` Relation types which should be copied over to the new api verison

Response contains a version object with all the details related to the created API Version, namely, id, name, api.

41. API-API Version - Update an API Version

PUT https://api.getpostman.com/apis/{{apiId}}/versions/{{apiVersionId}}

This call updates an existing API Version.

Request body should contain a version object with the fields which need to be updated. Only field which can be updated is name.

Response contains a version object with all the details related to the created API Version, namely, id, name, api etc.

42. API-API Version - Delete an API Version

DELETE https://api.getpostman.com/apis/{{apiId}}/versions/{{apiVersionId}}

This call deletes an existing API Version having the specified id.

Response contains an version object with id of the API Version which was deleted.

43. API-API Version - Get an API Version

GET https://api.getpostman.com/apis/{{apiId}}/versions/{{apiVersionId}}

This call fetches details about the specified API Version.

The response will contain a version object which would contain all the details of the API Version.

44. API-API Version - Get All API Versions

GET https://api.getpostman.com/apis/{{apiId}}/versions

This call fetches details about the all the API Versions in the specified API.

The response will contain an array versions object which would be a list of all the API Version along with their details.

45. API-Schema - Create Schema

POST https://api.getpostman.com/apis/{{apiId}}/versions/{{apiVersionId}}/schemas

This call creates a new schema.

Request body should contain a schema object which should atleast have these properties with string values:

type: Allowed types are openapi3, openapi2, openapi1, raml and graphql.
language : Allowed languages are json and yaml for OpenAPI and RAML schema types. GraphQL schema type accepts only graphql language.
schema: Optional. If passed, must be the content of the schema as a string.

Response contains a schema object with all the details related to the created schema, namely, id, language, type etc.

46. API-Schema - Update Schema

PUT https://api.getpostman.com/apis/{{apiId}}/versions/{{apiVersionId}}/schemas/{{schemaId}}

This call updates an existing schema.

Request body should contain a schema object which should atleast have these properties with string values:

type: Allowed types are openapi3, openapi2, openapi1, raml and graphql.
language : Allowed languages are json and yaml for OpenAPI and RAML schema types. GraphQL schema type accepts only graphql language.
schema: Optional. If passed, must be the content of the schema as a string.

Response contains a schema object with all the details related to the created schema, namely, id, language, type etc.

47. API-Schema - Get Schema

GET https://api.getpostman.com/apis/{{apiId}}/versions/{{apiVersionId}}/schemas/{{schemaId}}

This call fetches a single schema having the specified id.

Response contains a schema object with all the details related to the schema, namely, id, language, type, schema etc.

48. API-Schema - Create collection from schema

POST https://api.getpostman.com/apis/{{apiId}}/versions/{{apiVersionId}}/schemas/{{schemaId}}/collections?workspace=c90a3482-f80d-43d6-9dfb-0830f5e43605

This call creates a collection and links it to an API as one or multiple relations.

Request body requires two keys: - name - Name of the collection to be created. - relations - A list of relation(s) to be created.

The allowed relation types are contracttest, integrationtest, testsuite, and documentation.

49. API-Relations - Get linked relations

GET https://api.getpostman.com/apis/{{apiId}}/versions/{{apiVersionId}}/relations

This call fetches all the relations which are linked to the specified API version along with their details.

The response will contain a relations object which lists all the relation types which are linked to the API version. Each of the relation type will be an object which details the relations of this type.

50. API-Relations - Get documentation relations

GET https://api.getpostman.com/apis/{{apiId}}/versions/{{apiVersionId}}/documentation

This call fetches all the relations by type which are linked to the specified API version along with their details.

The response will contain an array with key {{relationType}}. Each of the item will consist of all the details related each of the relation.

51. API-Relations - Get environment relations

GET https://api.getpostman.com/apis/{{apiId}}/versions/{{apiVersionId}}/environment

This call fetches all the relations by type which are linked to the specified API version along with their details.

The response will contain an array with key {{relationType}}. Each of the item will consist of all the details related each of the relation.

52. API-Relations - Get test suite relations

GET https://api.getpostman.com/apis/{{apiId}}/versions/{{apiVersionId}}/testsuite

This call fetches all the relations by type which are linked to the specified API version along with their details.

The response will contain an array with key {{relationType}}. Each of the item will consist of all the details related each of the relation.

53. API-Relations - Get contract test relations

GET https://api.getpostman.com/apis/{{apiId}}/versions/{{apiVersionId}}/contracttest

This call fetches all the relations by type which are linked to the specified API version along with their details.

The response will contain an array with key {{relationType}}. Each of the item will consist of all the details related each of the relation.

54. API-Relations - Get integration test relations

GET https://api.getpostman.com/apis/{{apiId}}/versions/{{apiVersionId}}/integrationtest

This call fetches all the relations by type which are linked to the specified API version along with their details.

The response will contain an array with key {{relationType}}. Each of the item will consist of all the details related each of the relation.

55. API-Relations - Get all test relations

GET https://api.getpostman.com/apis/{{apiId}}/versions/{{apiVersionId}}/test

This call fetches all types test relations linked to the specified API version. This includes the testsuites, integrationtest, and contracttest relations.

The response contains a test object. Each item contains details about each test.

56. API-Relations - Get monitor relations

GET https://api.getpostman.com/apis/{{apiId}}/versions/{{apiVersionId}}/monitor

This call fetches all the relations by type which are linked to the specified API version along with their details.

The response will contain an array with key {{relationType}}. Each of the item will consist of all the details related each of the relation.

57. API-Relations - Create relations

POST https://api.getpostman.com/apis/{{apiId}}/versions/{{apiVersionId}}/relations

This call allows you to add existing Qodex entities as new relations to an API. The request body should contain the relations to be created along with an array of entity IDs.

Relation	Entity ID type
contracttest	Collection UIDs
integrationtest	Collection UIDs
documentation	Collection UIDs
testsuite	Collection UIDs
environment	Environment UIDs
mock	Mock IDs
monitor	Monitor IDs

58. API-Relations - Sync relations with schema

PUT https://api.getpostman.com/apis/:apiId/versions/:apiVersionId/:entityType/:entityId/syncWithSchema

This call allows you to keep the relation in sync with the API schema.

59. API-Release - Create Release

POST https://api.getpostman.com/apis/{{apiId}}/versions/{{apiVersionId}}/releases

This call creates a new release in the specified API.

The request body should contain a release object which should have fields:

name	Required. Name of the Release
summary	Optional. Summary of the release
description	Optional. Description of the release
visibility	Required. Value can be `private` or `public`
gitTag	Optional This should be a valid Git tag in the repository connected with the API version

Response contains a release object with all the details related to the created release, namely, id, name, summary, description, visbility and gitTag.

60. API-Release - Delete release

DELETE https://api.getpostman.com/apis/{{apiId}}/versions/{{apiVersionId}}/releases/{{releaseId}}

61. API-Release - Get a Release

GET https://api.getpostman.com/apis/:apiId/versions/:apiVersionId/releases/:releaseId

This endpoint can be called to get information about a particular Release of the given API Version.

62. API-Release - Update Release

PATCH https://api.getpostman.com/apis/{{apiId}}/versions/{{apiVersionId}}/releases/{{releaseId}}

This call updates an existing release in the specified API Version.

The request body should contain a release object which can have the following fields:

name	Optional. Name of the Release
summary	Optional. Summary of the release
description	Optional. Description of the release
visibility	Optional. Value can be either `private` or `public`
gitTag	Optional This should be a valid Git tag in the repository connected with the API version

Response contains a release object with all the details related to the updated release, namely, id, name, summary, description, visbility and gitTag.

63. API-Release - Get all releases

GET https://api.getpostman.com/apis/:apiId/versions/:apiVersionId/releases

64. API - Create API

POST https://api.getpostman.com/apis?workspace=c90a3482-f80d-43d6-9dfb-0830f5e43605

This call creates a new API with a default API Version.

Request body should contain an api object which should atleast have a property name.

Response contains an api object with all the details related to the created API, namely, id, name, summary, description, etc.

65. API - Update an API

PUT https://api.getpostman.com/apis/{{apiId}}

This call updates an existing API .

Request body should contain an api object which should have the fields to be updated. Only name, summary and description fields can be edited for an API.

Response contains an api object with all the details related to the created API, namely, id, name, summary, description etc.

66. API - Delete an API

DELETE https://api.getpostman.com/apis/{{apiId}}

This call deletes an existing API having the specified id.

Response contains an api object with id of the API which was deleted.

67. API - Get all APIs

GET https://api.getpostman.com/apis

This call fetches all the APIs present in the specified workspace

Response contains an array named apis which would contain all the details of APIs present in the workspace.

68. API - Single API

GET https://api.getpostman.com/apis/{{apiId}}

This call fetches a single API having the specified id.

Response contains an api object with all the details related to the queried API, namely, id, name, summary, description etc.

69. Webhooks - Create Webhook

POST https://api.getpostman.com/webhooks?workspace={{workspace_id}}

Create a webhook that triggers a collection with your custom payload.

You can specify the webhook name and the collection to trigger by using the following attributes of the webhook object on your JSON body:

name: the name of the webhook that you're creating.
collection: the UID of the collection that you want to trigger once this webhook is called.

Once created, the webhook URL can be retrieved by accessing the webhookUrl attribute of the webhook object on the response JSON payload.

70. SCIM 2.0 - Identity-User Provisioning - Fetch User Resource

GET https://api.getpostman.com/scim/v2/Users/{{id}}

Fetches an individual Qodex team member's information.

71. SCIM 2.0 - Identity-User Provisioning - Fetch All User Resource

GET https://api.getpostman.com/scim/v2/Users

Fetches information on all Qodex team members. You can fetch information for a particular user with filters.

Note: By default, this endpoint will return a list of hundred users. To overwrite the default setting, update the 'startIndex=1&count=100' value in the request.

72. SCIM 2.0 - Identity-User Provisioning - Create User

POST https://api.getpostman.com/scim/v2/Users

Creates a new user account in Qodex, adds the user to your organization's Qodex team, and activates the user to authenticate into your Qodex team, provided an account with the same email ID does not already exist in Qodex. The newly added user will have the developer role in Qodex by default. You can later update user roles in Qodex.

If an account with the same email ID does exist, an [email invite] to join your Qodex team is sent to the user. Once the user accepts the invite, they will be added to your team.

73. SCIM 2.0 - Identity-User Provisioning - Update User Information

PUT https://api.getpostman.com/scim/v2/Users/{{id}}

Updates a user’s first and last name in Qodex.

74. SCIM 2.0 - Identity-User Provisioning - Update User Information

PATCH https://api.getpostman.com/scim/v2/Users/{{id}}

Updates user state in Qodex: * Activate User: Creates a new user on your Qodex team, if one does not already exist, and activates the user to authenticate into your Qodex team. * Deactivate User: Removes a user from your Qodex team and deactivates their account, blocking the account from authenticating into Qodex.

75. SCIM 2.0 - Identity - Service Provider Config

GET https://api.getpostman.com/scim/v2/ServiceProviderConfig

Returns configuration details for Qodex's SCIM API, including the list of operations that are supported.

76. SCIM 2.0 - Identity - Get ResourceTypes

GET https://api.getpostman.com/scim/v2/ResourceTypes

Returns all the resource types supported by Qodex's SCIM API.

77. API Security - Schema Security Validation

POST https://api.getpostman.com/security/api-validation

This endpoint will perform static analysis on the Schema specification. It will return the security misses in your schema definition and help you understand their implications and possible ways to patch the warnings. You can introduce this endpoint to your CI/CD process to automate your schema validation.

Request Body(max size 10MB)

Key	Value Type	Required	Description
type	Enum(openapi3, openapi2)	Yes	Type of Schema Specification
language	Enum(json, yaml)	Yes	Format of Schema Specification
schema	String	Yes	Stringified Schema Body

Visit Learning Center for more information

78. Audit Logs - Team Audit Logs

GET https://api.getpostman.com/audit/logs?since={{since}}&until={{until}}&limit={{limit}}&cursor={{cursor}}

The /audit/logs endpoint returns a list of audit events generated for your team. The complete list of all the audit events is available on our [Learning Center] page.

The API response contains an array named trails which contains the details for each audit event such as what was the action, who performed the action, when was it performed, etc.