> For the complete documentation index, see [llms.txt](https://docs.pixiebrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pixiebrix.com/how-to/troubleshooting/troubleshooting-bad-api-requests.md).
# Troubleshooting Bad API Requests
## Frequently Asked Questions
### How do I fix a “No Response Received” error?
See the instructions at [Troubleshooting Network Errors](/how-to/troubleshooting/troubleshooting-network-errors.md).
### My Request works in Postman. What’s wrong?
Here are the most common reasons a request works in Postman, but doesn’t work in PixieBrix:
**Incorrect use of the data** **field in PixieBrix to pass JSON**
To pass a data payload in PixieBrix, provide an object or variable:
✅ **Correct**
❌ **Incorrect:**
**Inconsistent headers**
Postman automatically adds some headers to requests. Those headers are optional for most APIs. However, the API you’re calling might require those headers
*Uncommon: header name capitalization.* PixieBrix automatically lowercases header names. However, some APIs require certain header names to be capitalized.
**Authentication**
If your Postman request is in a Postman Collection, Postman maybe including authentication information (headers/payload) with the request
**Invalid/Self-Trusted SSL Certificate**
Your Postman might be configured not to verify the SSL certificate.
In order to enable PixieBrix to call hosts with untrusted certificates, you must instruct Chrome to trust the certificate.
* Watch: [Trusting a Self-Signed Certificate on Windows](https://www.youtube.com/watch?v=zTr64CU4wm4)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.pixiebrix.com/how-to/troubleshooting/troubleshooting-bad-api-requests.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
.png?alt=media&token=0bed0b37-bed2-4c62-bc61-2fa3072fa177)
.png?alt=media&token=88976742-2600-4cf5-bf7e-23e182ffe95c)