Discussions

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

does readme support AsyncAPI specification ?

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?

Hello I face an issue when using multipart/form-data and object in body. Here is snapshot of current openapi 3.0  The problem is with `initials` and its content: `alignment` and` y` In documentation generated code looks like this:  In shell generated, we can see `--form alignment=hello --form y=10` Whereas i would expect `--form initials[alignment]=hello --form initials[y]=10` When using `application/json` instead of `multipart/form-data `is works very well, so i'm assuming this is a generation code problem related to `multipart/form-data`. Within the same endpoint i'm also upload a file so i need to keep `multipart/form-data` You can see our public doc here: <https://developers.yousign.com/reference/post-signature_requests-signaturerequestid-documents> Could you help me one this one, or tell me when this will be fixed ? Thanks

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.

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 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.

is readme application provides an user management API to perform the create, read, update, delete operation.

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?

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!