> For the complete documentation index, see [llms.txt](https://docs.intents.aurora.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intents.aurora.dev/api-reference/intents-connect-api-reference/submit-deposit-hash.md).

# Submit deposit hash

## Record a deposit transaction hash

> Records the origin-chain deposit transaction hash and notifies 1click. For MEMO deposit-mode chains (e.g. Stellar) the memo is required: it identifies the execution together with the deposit address and is forwarded to 1click. The memo is returned in the create and list responses, and omitting it for a MEMO-mode deposit returns 404. SIMPLE-mode chains (unique deposit address) omit the memo.

```json
{"openapi":"3.0.3","info":{"title":"Intents Connect API","version":"1.0"},"servers":[{"url":"https://intents-connect-api.aurora.dev"}],"paths":{"/api/v1/executions/deposit/submit":{"post":{"description":"Records the origin-chain deposit transaction hash and notifies 1click. For MEMO deposit-mode chains (e.g. Stellar) the memo is required: it identifies the execution together with the deposit address and is forwarded to 1click. The memo is returned in the create and list responses, and omitting it for a MEMO-mode deposit returns 404. SIMPLE-mode chains (unique deposit address) omit the memo.","requestBody":{"content":{"application/json":{"schema":{"$ref":"#/components/schemas/controllers.submitDepositRequestDoc"}}},"description":"Deposit transaction","required":true},"responses":{"200":{"content":{"application/json":{"schema":{"$ref":"#/components/schemas/controllers.statusResultResponse"}}},"description":"OK"},"400":{"content":{"application/json":{"schema":{"$ref":"#/components/schemas/controllers.errorResponse"}}},"description":"Bad Request"},"404":{"content":{"application/json":{"schema":{"$ref":"#/components/schemas/controllers.errorResponse"}}},"description":"Not Found"},"409":{"content":{"application/json":{"schema":{"$ref":"#/components/schemas/controllers.errorResponse"}}},"description":"Conflict"},"500":{"content":{"application/json":{"schema":{"$ref":"#/components/schemas/controllers.errorResponse"}}},"description":"Internal Server Error"}},"summary":"Record a deposit transaction hash","tags":["Executions"]}}},"components":{"schemas":{"controllers.submitDepositRequestDoc":{"properties":{"depositAddress":{"type":"string"},"memo":{"description":"Memo identifies the execution together with depositAddress for MEMO deposit-mode chains (e.g. Stellar)","type":"string"},"txHash":{"type":"string"}},"type":"object"},"controllers.statusResultResponse":{"properties":{"result":{"$ref":"#/components/schemas/controllers.statusResult"}},"type":"object"},"controllers.statusResult":{"properties":{"status":{"type":"string"}},"type":"object"},"controllers.errorResponse":{"properties":{"error":{"type":"string"}},"type":"object"}}}}
```


---

# 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://docs.intents.aurora.dev/api-reference/intents-connect-api-reference/submit-deposit-hash.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.