> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/public-finance/setup/configuration/services/digit-exchange.md).

# DIGIT Exchange

## Overview

DIGIT Exchange functions as a connector bridging services deployed across diverse domains. Its primary role involves signing and verifying exchange messages and generating events for ingestion into Elasticsearch for dashboard visualisation.

## Key Functionalities

* Signs the exchange messages and sends them to respective systems according to receiver ID and current domain.
* Verifies data received from other domains, converts it to JSON object and forwards it to the program service.
* Pushes the data to Kafka for dash-boarding and making the calls async.
* In case of any exception, send a reply to the service that initiated the call.

## Deployment

[Helm Charts](https://github.com/egovernments/DIGIT-DevOps/tree/74999d265513e7a1d19e75309bcd992639ba1624/deploy-as-code/helm/charts/ifix/domain-services/digit-exchange)

## Integration

/digit-exchange/

### API Spec

{% embed url="<https://editor.swagger.io/?url=https://raw.githubusercontent.com/egovernments/DIGIT-Specs/59f1f47d2e1e5f34b62a63790b4d35abdf05ef15/Common%20Services/digit-exchange.yaml>" %}


---

# 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.digit.org/public-finance/setup/configuration/services/digit-exchange.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.