> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/qna/using-navixy/recurso-confiable-event-codes.md).

# Recurso Confiable event codes

The main Recurso Confiable protocol passes Navixy's platform event ID through unchanged, but a second protocol option replaces it with its own three-value code

## Question

What do the numeric event codes Recurso Confiable receives mean, and how do they map to Navixy events?

## Answer

Navixy ships two Recurso Confiable protocol options, and the answer depends on which one the retranslator uses. Both send the code in the `code` field, but only the main protocol passes Navixy's event ID through unchanged. Check the protocol name shown in **Data forwarding** → **Protocols** before you interpret a code.

### Main Recurso Confiable protocol

This protocol sends Navixy's platform event ID as is. There's no separate translation table, so a code you see on the Recurso Confiable side always matches the same numeric event ID documented in [Platform's event code IDs and their definitions](/docs/expert-center/faq-and-troubleshooting/access-iot-data/save-iot-data-to-csv-file/columns-in-csv-file.md#platforms-event-code-ids-and-their-definitions).

For a regular movement or location packet with no alarm, the code is `2` ("Track. No specific event, just a track point").

### Second protocol option

The second Recurso Confiable protocol option, used for a specific enterprise retail integration, replaces the platform event ID with its own code. It distinguishes only three cases:

| **Navixy event**                                                                | **Code sent** |
| ------------------------------------------------------------------------------- | ------------- |
| SOS button pressed (event ID 83)                                                | `911`         |
| OBD Unplug from the car’s connector (44), Device detached from the object (100) | `912`         |
| Any other event, including plain track points                                   | `0`           |

Don't use the platform event ID table to interpret codes from this protocol. A code of `0` doesn't identify which event occurred, and a plain track point sends `0` rather than `2`.

If you're not sure which of the two options a retranslator uses, contact [support](mailto:support@navixy.com) with the retranslator name.

## Links

[Recurso Confiable](/docs/user/guide/devices-and-settings/connectivity/data-forwarding/recurso-confiable.md)

[Platform's event code IDs and their definitions](/docs/expert-center/faq-and-troubleshooting/access-iot-data/save-iot-data-to-csv-file/columns-in-csv-file.md#platforms-event-code-ids-and-their-definitions)


---

# 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://navixy.com/docs/qna/using-navixy/recurso-confiable-event-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.