Fixed Number and Yes/No Fields in the API Reference
We fixed an issue in the API reference at api.botdog.co/docs that could make some requests confusing to fill in and fail before they were sent.
What was happening
Some fields that only need a number or a simple yes/no value were incorrectly shown as if they required a larger block of structured data.
This meant the API reference displayed large text boxes instead of a number field or toggle. Trying to send a request from the page could then fail with a generic Unable to complete request message.
This affected:
- Limit, which controls how many results are returned per page, for blacklists, lists, list members, leads, campaign leads, LinkedIn accounts, and snippets
- Include blacklist when listing your lists
- Is blacklist when creating a list
- Read when marking a conversation as read or unread
What changed
These fields now appear correctly as either:
- A number
- A yes/no choice
Requests sent directly from the API reference now work as expected.
Good to know
If you call the Botdog API directly from your own code, nothing changes.
The API itself has always accepted plain numbers and true/false values correctly. Only the published API description was wrong.
If you generate a client from the Botdog OpenAPI specification, regenerate it to pick up the corrected field types.
