> For the complete documentation index, see [llms.txt](https://documentation.astera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.astera.com/astera-data-stack-v7/functions/date-time/addhours-datetime.md).
# AddHours (DateTime)
| **Name** | ***AddHours*** |
| ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Syntax | AddHours (Date date, Integer hours) |
| Purpose | To return the date and time after adding the number of hours. |
| Description | Adds or subtracts number of hours to/from the specified datetime value. |
| Return Type | DateTime |
| Parameters |
date \[System.DateTime] – Date to which hours should be added
hours \[System.Int64] – Number of hours to be added. To subtract, use negative hours.
|
.png)
**Example**
In this example, we will pass a date time value, and an integer value (indicating hours to be added or subtracted) to the function transformation object using a *Variables* object.
Where,
*date* = 01-01-2022 01:00:00
*hours* = 5
In the output window, you can see that the provided integer value, indicating the number of hours, has been added to the given date time value.
---
# 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://documentation.astera.com/astera-data-stack-v7/functions/date-time/addhours-datetime.md?ask=&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.
.png)
.png)