# Callbacks

## Overview

Webhook callbacks can be enabled for customers to receive updated on accounts, transactions and exchanges as they happen. To do so please contact the support team and provide a callback URL you with to use for it. You will be provided with a hash secret for authenticating callbacks.

Callback requests have the following properties:

* Content type is of type `application/json`.
* It will contain `webhook-signature` header. It is generated by using a SHA256 hashing algorithm on a concatenated string of `requestBody + hashSecret`. Use the hash secret provided to you to verify the authenticity of the request before processing it.
* It's content will contain a JSON object with following fields:
  * Id - GUID for the request.
  * Type–Callback type code indicating what type of event has occurred.
  * Data (object): containing details about the event. Details depend on the event type.
* A 200 HTTP response code is expected. If a different response is returned, the request will be retried with exponential backoff for 2 hours.

### [Continue to the next page for information on Callback Types and Formatting](/callbacks/fiat-deposit-received.md)


---

# 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://customer-api-docs.ibanera.com/callbacks.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.