# CD.COM.API.01 api\_error\_codes\_common

Common error codes are a set of common status codes that are used in various APIs to indicate specific errors or exceptional events. Here are a few error codes that are used in APIs. This can be further amended by the implementing agency.

<table><thead><tr><th width="316">Code</th><th width="410">Description </th><th data-hidden>Scenarios</th></tr></thead><tbody><tr><td>rjct.request.invalid</td><td>Error while parsing request</td><td></td></tr><tr><td>rjct.signature.invalid</td><td>Signature is invalid or missing</td><td></td></tr><tr><td>rjct.headers.invalid</td><td>Header is missing or invalid</td><td></td></tr><tr><td>rjct.headers.version.invalid</td><td>Version in headers is missing or invalid</td><td></td></tr><tr><td>rjct.headers.message_id.invalid</td><td>Message ID in headers is missing or invalid</td><td></td></tr><tr><td>rjct.headers.message_ts.invalid</td><td>Message timestamp in headers is missing or invalid</td><td></td></tr><tr><td>rjct.headers.sender_id.invalid</td><td>Sender ID in headers is missing or invalid</td><td></td></tr><tr><td>rjct.headers.receiver_id.invalid</td><td>Receiver ID in headers is missing or invalid</td><td></td></tr><tr><td>rjct.headers.action.invalid</td><td>Action in headers is missing or invalid</td><td></td></tr><tr><td>rjct.headers.total_count.invalid</td><td>Total count  in headers is missing or invalid</td><td></td></tr><tr><td>rjct.headers.total_count.limit_exceed</td><td>Total count limit exceed, implementer can define own limit to restrict counts </td><td></td></tr><tr><td>rjct.headers.completed_count.invalid</td><td>Completed count in headers is invalid</td><td></td></tr><tr><td>rjct.headers.is_encrypted.invalid</td><td>Is encrypted flag in headers is missing or invalid</td><td></td></tr><tr><td>rjct.headers.encryption_algorithm.invalid</td><td>Encryption algorithm in headers is invalid</td><td></td></tr><tr><td>rjct.headers.async.invalid</td><td>Async flag value in headers is invalid, true or false is allowed as value</td><td></td></tr><tr><td>rjct.headers.callbackendpoint.connection_error</td><td>Call back url is not reachable or invalid</td><td></td></tr><tr><td>rjct.headers.callbackendpoint.autherror</td><td>Call back url sent authentication related error while connecting</td><td></td></tr><tr><td>rjct.message.transaction_id.invalid</td><td>Transaction_id in message is missing or invalid</td><td></td></tr><tr><td>rjct.filter.invalid</td><td>Filter attribute is missing or invalid</td><td></td></tr><tr><td>rjct.filter.sort</td><td>Sort attribute is missing or invalid</td><td></td></tr><tr><td>rjct.pagination.invalid</td><td>Pagination attribute is missing or invali</td><td></td></tr><tr><td>rjct.locale.invalid</td><td>Locale attribute is missing or invalid</td><td></td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://standards.spdci.org/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/code-directory/api-specific/cd.com.api.01-api_error_codes_common.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.