> For the complete documentation index, see [llms.txt](https://docs.goldenedi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.goldenedi.com/standards/standard-app/gedi-codes.md).

# GEDI Codes

When creating new 'GEDI Message Codes' or 'GEDI Status Codes', it is recommended from Golden EDI side that you try to use a relevant code from the linked excel document. This is to avoid unecessary missunderstanding when communicating around these codes.

Nevertheless, sometimes you need codes that is not yet defined in the standard and then you can name it whatever you like. If you choose to name your own codes, please try to follow the naming convention as descibed in the excel document.

{% embed url="<https://goldenediab.sharepoint.com/:x:/g/EaUvKCht00xLmvTmt3ML_qUBlvYFSZlX9qxXCdWrT0kybg?e=5EQnvn>" %}

The excel document has 3 tabs;

1. MessageCodes - A list of standard 'GEDI Message Codes'.
2. StatusCodes - A list of standard 'GEDI Status Codes'.
3. MessageCodeNaming - A description of naming convention for 'GEDI Message Codes'


---

# 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.goldenedi.com/standards/standard-app/gedi-codes.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.