# Importing Custom Capabilities via Postman Collection When integrating your API with Interworky via a Postman Collection, it’s important to follow these guidelines to ensure a smooth import process

### Exporting Your Postman Collection * File Format: * Make sure your Postman Collection is exported as a JSON file. * Version: * Export your collection as `v2.1`. This is the supported version for Interworky imports. ### Configuring Environment Variables Your Postman Collection may include dynamic values, such as the host URL for different environments (e.g., development, staging, production).

Adding your POSTMAN host/base_url environment variable

To handle this Use **Variables**: Instead of hardcoding the host URL in your API endpoints, use a variable. For example, For your host you might use: {{baseURL}} * **Defining the Variable:** In your Postman environment or collection, define: * Variable Name: baseURL * Variable Value: The corresponding URL for your desired environment (e.g., or ). {% hint style="info" %} Local environments might not work properly with this configuration. Ensure you use a URL that’s accessible from the internet, such as your staging or production domain {% endhint %}
--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://interworky.gitbook.io/interworky-docs/features-overview/capabilities/importing-custom-capabilities-via-postman-collection.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.