Discussions

In the try it provide a way to set global header values so that you don't have to cut and paste into every endpoint that you want to try.

I cannot see a way to add an image to help explain my problem.... <https://v.usetapes.com/yLjdvMHiiJ>

Is there a way to recover email/username?

does readme support AsyncAPI specification ?

I am facing this issue "unknown error(cannot read the properties of null ('reading slug'))" while deploying OAS through github. could someone help me to resolve this issue. As a developer, I am working on documentation for API changes. Due to support of multiple base URL's, I upgraded to OAS 3.0 from OAS 2.0. After that I started facing this issue. If i update readme keys (API_DEFINITION_KEY & Readme key), then the build is successfull. But after deploying few more changes suddenly this issue replicating. I did validating my OAS file using swagger editor and no error in it. could you pleae reproduce this isssue on your side and provide me the solution.

I moved a section from the Reference to the Guides, it move the section header and the first document in the section, but I now cannot find the subtopics that were attached to the first topic. Where did they go?

Like I set a required authentication in headers, in curl code. it will show automatically. ```curl curl curl --request GET \ --url https://xxxxxxx \ --header 'api-secret: testtest' \ --header 'accept: application/json' ``` But if I want to use it in my own example, like python sdk. how can I use it. ```python api-secret=${api-secret} ```

I have a use case in hand where I have some custom headers that should be **shared across all the described endpoint paths** in a given JSON. Is it possible to define those header parameters **globally** for a particular API JSON?

Is there a way to currently do this? Or do we just need to update it by hand? It becomes cumbersome if the recipe is on the longer side.

If we have a Guide topic with a slug of slug-name, can we also have an API reference topic name slug-name (exactly the same)? So in linking, both (doc:slug-name) and (ref:slug-name) would exist. Or must a slug be unique across both the doc: and ref: domains? Thank you!