Forum Discussion

Stoplight's avatar
Stoplight
Community Manager
3 months ago
Solved

Variables in Server URLs

Originally posted by user Logan Saso to the Stoplight Community on 07/19/2023 at 15:43 ET.

Hi everyone, my name is Logan and I'm the engineer leading the API project at my company ConductorOne https://conductorone.com/ and a new customer of stoplight as of this week.

We segment our customers into all of their own domains, such that I might be logan.conductor.one for my environment, or stoplight.conductor.one might be an environment if they were a customer.

As such, we have no single unified url for making api calls. In our openapi.yaml which we ingest into stoplight, we render this as https://{tenantDomain}.conductor.one and provide a default example value of https://invalid-example.conductor.one . This also means that users will be unable to use the API explorer with a bearer token to make API calls.

Is there a way to indicate that this part of the URL is a variable the user of the docs site should set, for example to logan, so that the explorer can make requests to logan.conductor.one ?

  • a_welch (Staff) [07/27/2023 - 16:41 ET]

    I chatted about this internally and based on what you talked about the conclusion was that this should a feature request. If you can use the link below, click on the Submit Idea button, and enter this request the Stoplight Product team will review it. https://roadmap.stoplight.io/tabs/9-launched

1 Reply

  • Stoplight's avatar
    Stoplight
    Community Manager

    a_welch (Staff) [07/27/2023 - 16:41 ET]

    I chatted about this internally and based on what you talked about the conclusion was that this should a feature request. If you can use the link below, click on the Submit Idea button, and enter this request the Stoplight Product team will review it. https://roadmap.stoplight.io/tabs/9-launched