> For the complete documentation index, see [llms.txt](https://developer.flash-payments.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.flash-payments.com/compliance/request-for-information/rfi-response-codes.md).

# RFI response codes

All reply codes and GraphQL errors

There are two places an RFI call can report a problem: the `code` field on the mutation reply payload, and the top-level GraphQL `errors` array.

### **Reply codes**

Returned in the `code` field of `AnswerRfiQuestionReply` / `DeclineRfiReply`:

| Mutation            | success | code               | When                                                                                                 |
| ------------------- | ------- | ------------------ | ---------------------------------------------------------------------------------------------------- |
| `answerRfiQuestion` | `true`  | `RECORDED`         | The reply was recorded                                                                               |
| `declineRfi`        | `true`  | `MARKED`           | The RFI was declined and closed                                                                      |
| both                | `false` | `NOT_FOUND`        | The RFI does not exist or does not belong to you                                                     |
| both                | `false` | `INVALID_STATUS`   | The RFI is not `PENDING` — answers and declines are only accepted while it is open for your response |
| `answerRfiQuestion` | `false` | `Already provided` | The question was answered by a concurrent submission (for example, via the email form)               |

### **GraphQL errors**

Invalid input is rejected before any reply payload is produced. These are returned in the top-level `errors` array with no `data`, with `extensions.code` set to:

| extensions.code     | Operation                 | When                                                                                                                                                                                                                                                                                    |
| ------------------- | ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `BAD_USER_INPUT`    | any RFI query or mutation | Malformed `rfiId` / `id` — IDs are 24-character hex strings                                                                                                                                                                                                                             |
| `BAD_USER_INPUT`    | `answerRfiQuestion`       | The RFI was not found, unknown `questionCode`, the question has already been answered, or a file-rule violation — files on a `NONE` question, both `text` and `files` on a `PREFERRED` question, neither provided, too many files, unsupported file type, or a file over the size limit |
| `TOO_MANY_REQUESTS` | any                       | Rate limit exceeded — see below                                                                                                                                                                                                                                                         |

The error `message` spells out the specific problem, for example `Question SENDER_ID_PROOF has already been answered.` or `File "passport.pdf" exceeds the 10 MB per-file limit.`

### **Rate limits**

RFI queries and mutations are subject to the same per-client and per-IP limits as the rest of the API. When a limit is exceeded, the response is HTTP `429` with a `Retry-After` header (seconds) and `code: TOO_MANY_REQUESTS`. See [Rate limiting](/other/rate-limiting.md).


---

# 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://developer.flash-payments.com/compliance/request-for-information/rfi-response-codes.md?ask=<question>&goal=<user_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.