Automatic Assignment of Common Path Parameters from Environment Variables

[allsgaminghd]

When importing an OpenAPI specification into Apidog, it’s common to encounter recurring path parameters such as tenant, clientId, or similar identifiers. Currently, these need to be manually updated to use environment variables across all endpoints.

Proposed Feature:

It would be incredibly helpful to have an option in Apidog that allows users to automatically assign predefined values (such as environment variables) to certain recurring path parameters. For example, when a path parameter named tenant is detected, it could be automatically set to {{TENANT}}.

Benefits:

Saves time by reducing repetitive manual updates

Ensures consistency across all endpoints

Reduces the risk of errors from hardcoded or outdated values

Example:

If the OpenAPI path is:

/api/{tenant}/users

Apidog could automatically set value of {tenant} to be {{TENANT}} env var, based on a user-defined rule or configuration.

[system]

You can use a post-script in the root directory to modify parameter values globally when certain conditions are met. This will apply to all requests: Using scripts to modify request messages - Apidog Docs

[system]

Just to check, would a “bulk edit endpoints” feature meet your needs? We’re currently planning to design such a feature.

[allsgaminghd]

That could work but value in GUI will be not set ? it’s OK but not optimal I think, but yes, if we can bulk edit endpoints after importing an OpenAPI doc it will be cool (also if we can run it automatically after import with auto-sync)

[system]

Yes, bulk editing is already in our roadmap. For now, you can work around this by modifying the Path parameter “tenant” to use example value {{TENANT}} in your OpenAPI file before importing.