> For the complete documentation index, see [llms.txt](https://docs.primelister.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.primelister.com/troubleshooting/unable-to-contact-api-unable-to-process-your-request-error.md).

# Unable to Contact API & Unable to Process Your Request

"Unable to Contact API" and "Poshmark error: Unable to process your request." an error is given when something goes wrong at the end of [Mercari.com](https://www.mercari.com/) or [Poshmark.com](https://poshmark.com/). This error is temporary.&#x20;

**How to resolve this error?**&#x20;

This error will be solved by itself when you try again after some time. When it does not get solved for a long time, try to add a new listing manually and get in touch with platform officials (from Mercari or Poshmark) if you still get the same error.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.primelister.com/troubleshooting/unable-to-contact-api-unable-to-process-your-request-error.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
