Discussions

When trying to edit category through command, getting error Command: rdme openapi --key=$README_API_KEY --id=$CATEGORY_ID Error: request to <https://dash.readme.com/api/v1/api-registry> failed, reason: unable to get local issuer certificate

Similarly to [this issue](https://docs.readme.com/main/discuss/60c38ce69f926600450f3048), I am using an autogenerated openapi file from FastAPI, and don't see why there isn't an easy way to manually set the api endpoint for the generated docs, or at least sync with whatever endpoint the openapi file is retrieved from. This feature is blocking us from using the built-in request flow, a pretty big issue for our users. Is there any fix coming or available?

We are beginning to dive into our Metrics and see our Top Pages. Is there a way to determine drop off rate or infer it based on page flow?

<https://docs.os1.delhivery.com/changelog> for some reason the content has stopped rendering. Any idea why?

Hi All, I have a startup account and would like to keep my project private. But, I want to share my project with 20 external users. What is the best option to achieve it? Thanks, Manish

Hi, we're having troubles with embedded video in <https://docs.cast.ai/docs> Our welcome page has a video, and we're noticing few issues. iPhone/Chrome: video is missing a preview picture, mostly rendering a dark screen with play button. Macbook/Safari/4k screen: preview is rendered as mostly black screen with small thumbnail in it. Macbook/Chrome there's a weird autoplay behavior, to reproduce: 1. open docs.cast.ai 2. navigate away, e.g. click on "About the read only agent" 3. Click on "Getting started" again 4. Video starts playing automatically

Hi team. I have swagger 2.0 file <https://prod.truv.com/swagger.json> with one of the definitions like this (excerpt schema): ```json JSON { "definitions": { "EmployerCreate": { "type": "object", "properties": { "company_name": { "description": "Company name", "type": "string", "example": "Facebook Demo" }, "account": { "description": "Bank account info. Used for Direct deposit switching and Paycheck linked lending", "required": [ "account_number", "account_type", "routing_number", "bank_name", "deposit_type" ], "type": "object", "properties": { "account_number": { "description": "Account number", "type": "string", "example": "16002600" }, "account_type": { "description": "\nAccount type:\n\n* `checking` - Checking account,\n* `savings` - Savings account\n\n", "type": "string", "enum": [ "checking", "savings" ], "example": "checking" }, "routing_number": { "description": "Routing number", "type": "string", "example": "123456789" }, "bank_name": { "description": "Bank name", "type": "string", "example": "TD Bank" }, "deposit_type": { "description": "\nDeposit type:\n\n* `entire` - Entire paycheck,\n* `percent` - Percentage of the paycheck,\n* `amount` - Fixed amount from the paycheck\n\n", "type": "string", "enum": [ "entire", "percent", "amount" ], "example": "percent" }, "deposit_value": { "description": "Deposit value", "type": "string", "example": "50.00" } } } } } } } ``` My issue is that when I add this object in the list of object on the page <https://docs.truv.com/reference/orders_create> field "account" always added in the request example. E.g.: ``` curl --request POST \ --url https://prod.truv.com/v1/orders/ \ --header 'X-Access-Client-Id: xxx' \ --header 'X-Access-Secret: sandbox-xxx' \ --header 'accept: application/json' \ --header 'content-type: application/json' \ --data ' { "employers": [ { "account": { "account_type": "checking", "deposit_type": "entire" } } ] } ``` Which is wrong for our logic. Seems like required enums account_type and deposit_type is the case of the behavior. They are truly required when object account is provided. But the account object itself is optional for most of our cases. Any tips on how to suppress auto-adding of the account object? Desired result is: ``` curl --request POST \ --url https://prod.truv.com/v1/orders/ \ --header 'X-Access-Client-Id: xxx' \ --header 'X-Access-Secret: sandbox-xxx' \ --header 'accept: application/json' \ --header 'content-type: application/json' \ --data ' { "employers": [ { "company_name": "Some company" } ] } ``` I tried several combinations of default/example parameters, but only thing that works is to make enums account_type and deposit_type optional (which is wrong for our API). Thank for help in advance!

How can I find the reciept ( vs oayment made by us )