Discussions

Hi everyone! I'm trying to use API of Active Campaign to get all the "Contacts - Custom Fields Values" but regarding that, the only way to filter for now is by "fieldedid" or "value" of the custom fields, it's impossible for me to do it. Do you know whether there is a way like in"Contacts" to filter by creation or update date? Kind Regards, Daniel

Live testing of API endpoints using the API Explorer(API Reference Page) basically supports RESTful endpoints, is there a way to test XML endpoints? Thanks

Hi, it seems like when returning an array, and the associated schema is inherited with `allOf` the object is not properly displayed when you click on the "Response" to see how it looks. Strangely, it works with non array. example below: responses: 200: description: OK - List of advertiser objects content: application/json: schema: type: array items: $ref: '#/components/schemas/advertiser' advertiser: allOf: # Combines the basicAdvertiser and the advertiser model - $ref: '#/components/schemas/basicAdvertiser' - type: object

Hi, i see that readOnly properties are part of OpenAPI 3.0.3, that you support, but when I use your site they are not handled correctly. Intended behaviour of a readOnly property: 1) not being display in body params 2) being displayed in the response body and in the example same property in editor.swagger.io behaves correctly is there any plan to fix it ? thanks in advance

In my OAS 3.0 spec, I have a number of oneOf's specified. They render in Readme.com as pulldowns, with the first object defined in the oneOf block selected, and its schema displayed. When a different selection is made in the pulldown, I would expect that the pulldown updates its value, and the schema for the previous selection is replaced by the schema for the new selection. However, this is not occurring. What is the expected behavior when a new selection is made in a pulldown? If the pulldown is supposed to update and the schema for the new selection is supposed to replace the old selection's schema in the display, is there an example spec I can review to see what I may be missing in my spec? Thanks!

Slack integration works for suggested edits but will not send notifications for Discussion questions. Any thoughts on how to fix this?

I'm getting this validation error: ``` The spec you uploaded has validation errors that must be addressed. Here's what we found: Validation failed. /paths/authentication-settings/saml-metadata-upload/put has a file parameter, so it must consume multipart/form-data or application/x-www-form-urlencoded ``` I tried validating my spec against the json schema for swagger 2 from here : https://github.com/OAI/OpenAPI-Specification/blob/main/schemas/v2.0/schema.json and it validated successfully. So my question is what extra validation does readme.com does on swagger spec?

trying to import a URL and got this error: ``` Swagger schema validation failed. Data does not match any schemas from 'anyOf' at #/definitions/ResponseListWebhookAction/properties/data/items Array items are not unique (indexes 0 and 22) at #/definitions/ResponseListWebhookAction/properties/data/items/enum Expected type array but found type object at #/definitions/ResponseListWebhookAction/properties/data/items JSON_OBJECT_VALIDATION_FAILED ``` File URL is https://app.harness.io/gateway/pipeline/api/swagger.json

Recently users have been complaining that some of the examples from the documentation are not working. Previously when a file was attached to the payload (multipart/form-data), it was attached the following way: curl -X POST "https://api.emysound.com/api/v1/Tracks" -H "accept: application/json" -F "file=@do_not_go.wav;type=audio/x-wav" Since latest updates, it attaches it the following way: curl --request POST \ --url https://api.emysound.com/api/v1/Tracks \ --header 'Accept: application/json' \ --header 'Content-Type: multipart/form-data; boundary=---011000010111000001101001' \ --form MediaType=Audio \ --form 'file=data:audio/x-wav;name=do_not_go.wav;base64 <ENTIRE BASE 64 OF THE FILE> The difference is in the file form: Previous: --form "file=@do_not_go.wav;type=audio/x-wav" Right now: --form "file=data:audio/x-wav;name=do_not_go.wav;base64 <ENTIRE BASE 64 OF THE FILE>" Notice how it attaches base64 on the entire file which triggers errors on the server side since no base64 payload is expected, rather path to the file. Is there any way to enable back previous behavior?