Path param not showing up in editors

system · July 4, 2025, 1:00am

Hi Team, all the APIs in which path params are defined, they are not visibile in these boxes. Please look into this.

system · July 4, 2025, 2:46am

Hi HamzaJD, I can see it’s working fine on my side. Could you please provide the reproduction steps and the specific API settings?

system · July 4, 2025, 11:57am

Check it on Hosted Docs. Do not pass a value. Just keep it empty.

system · July 4, 2025, 4:33pm

Hi HamzaJD, when no path parameter value is provided, generating /pet/ is the correct behavior. The {petId} in your API definition /pet/{petId} is a path placeholder that needs to be replaced with actual values - curly braces aren’t supported in actual network requests. Let me know if you have further questions.

system · July 4, 2025, 6:03pm

Hi there, makes sense. However the screenshot that I shared in this API path the path param was {org_id} and its between “organization/{org_id}/tools” in the spec.

system · July 5, 2025, 1:52am

Hi HamzaJD, you can set example values for the parameters. If no specific value is provided, you can use variables to ensure the path in the curl is complete.