> For the complete documentation index, see [llms.txt](https://guides.clickatell.com/release-notes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.clickatell.com/release-notes/release-notes-archive/2022-release-notes/q2-2022/automated-messaging/api-integration-screen-enhancement.md).

# API Integration screen enhancement

We've added the ability to add Headers as key-value pairs on the [API Integration](https://clickatell.gitbook.io/flow/configuration/api-integration) screen.

Previously, managing different UAT/Prod API Keys was challenging and time-consuming as they could only be set on the [HTTP Call node](https://clickatell.gitbook.io/flow/action-nodes/action-nodes-api-integration) itself, which meant that every time you prepared a release, each individual HTTP Call node had to be updated with the applicable API keys.

With this latest release, it is now easier for flow-builders to configure the API keys only once on the API level instead of updating them on each node.

We've also updated the styling of this screen to match the new Chat Flow UI as part of the ongoing 'face-lifting' mission. 

<figure><img src="/files/u3uXMSnygczEq37daXWR" alt=""><figcaption><p>Enhanced API Integration Screen</p></figcaption></figure>


---

# 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://guides.clickatell.com/release-notes/release-notes-archive/2022-release-notes/q2-2022/automated-messaging/api-integration-screen-enhancement.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.