# HTTP Response Headers in Lookup

**URL:** <https://connective.celigo.com/t/http-response-headers-in-lookup/3184>\
**Category:** Integrator.io\
**Tags:** http, lookup, headers, flow-builder\
**Created:** [February 11, 2025, 9:51pm UTC](https://connective.celigo.com/t/http-response-headers-in-lookup/3184 "2025-02-11T21:51:54Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![davidgollom](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/davidgollom/32/6605_2.png) [@davidgollom](https://connective.celigo.com/u/davidgollom)\
**Post date:** [February 11, 2025, 9:51pm UTC](https://connective.celigo.com/t/http-response-headers-in-lookup/3184/1 "2025-02-11T21:51:54Z")

</div>

Hey Everyone,  
I'm working with an API that requires the use of the if-match http header. I need to make a GET call and retrieve a value from the response header "eTag" and then included that value as the if-match. I can't find a way to access the https response headers in an HTTP Lookup bubble.

Is there a way to do this? Are those headers available?

Thanks!

---

<div class="post-metadata">

**Author:** ![tylerlamparter](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/tylerlamparter/32/9204_2.png) [@tylerlamparter](https://connective.celigo.com/u/tylerlamparter)\
**Post date:** [February 11, 2025, 10:10pm UTC](https://connective.celigo.com/t/http-response-headers-in-lookup/3184/2 "2025-02-11T22:10:43Z")

</div>

You'll have to use the ole workaround for now which is to not use a lookup and instead use an import step. From there, you'll have to use our api to update the method to a GET after you put all the other setup in that you need (UI gets weird after you set method to GET via api). Then go to response mapping and you'll have access to the headers to response map. As for calling our api, I usually use the [ZangaBox chrome extension](https://chromewebstore.google.com/detail/zangabox/bamdljjdfabfogmdkbjjigjpeebmfdek?hl=en&pli=1) since it makes it much easier to update things via api call compared to generating a token and using postman.

We tentatively have a feature enhancement for April's release where response headers will be available in transformation 2.0 of lookups and exports.

---

<div class="post-metadata">

**Author:** ![davidgollom](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/davidgollom/32/6605_2.png) [@davidgollom](https://connective.celigo.com/u/davidgollom)\
**Post date:** [February 11, 2025, 10:45pm UTC](https://connective.celigo.com/t/http-response-headers-in-lookup/3184/3 "2025-02-11T22:45:38Z")

</div>

Hi Tyler!  
Thanks for the workaround. I'll give that chrome extension a try. I saw your other posts outlining how it can be used.

Appreciate the help!!

---

<div class="post-metadata">

**Author:** ![davidgollom](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/davidgollom/32/6605_2.png) [@davidgollom](https://connective.celigo.com/u/davidgollom)\
**Post date:** [June 3, 2025, 3:34pm UTC](https://connective.celigo.com/t/http-response-headers-in-lookup/3184/4 "2025-06-03T15:34:17Z")

</div>

> [@tylerlamparter](#):
>
> 2.0

Hi Tyler,  
Was the new feature to map lookup headers into the response competed??

Thanks.

---

<div class="post-metadata">

**Author:** ![tylerlamparter](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/tylerlamparter/32/9204_2.png) [@tylerlamparter](https://connective.celigo.com/u/tylerlamparter)\
**Post date:** [June 3, 2025, 3:38pm UTC](https://connective.celigo.com/t/http-response-headers-in-lookup/3184/5 "2025-06-03T15:38:47Z")

</div>

@davidgollom it was not and I'll have to be more careful on giving any dates 🙂. That being said, while it was "tentative" for April, it is currently committed for July and is being worked on now to hit that release. So pending any change, it will be here soon.

---

<div class="post-metadata">

**Author:** ![davidgollom](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/davidgollom/32/6605_2.png) [@davidgollom](https://connective.celigo.com/u/davidgollom)\
**Post date:** [June 3, 2025, 3:56pm UTC](https://connective.celigo.com/t/http-response-headers-in-lookup/3184/6 "2025-06-03T15:56:25Z")

</div>

I understand about the dates. Not a problem. I'll continue with the workaround for now!  
Thanks.

---

<div class="post-metadata">

**Author:** ![tylerlamparter](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/tylerlamparter/32/9204_2.png) [@tylerlamparter](https://connective.celigo.com/u/tylerlamparter)\
**Post date:** [July 17, 2025, 1:56pm UTC](https://connective.celigo.com/t/http-response-headers-in-lookup/3184/7 "2025-07-17T13:56:37Z")

</div>

@davidgollom this is now available to all!

[https://docs.celigo.com/hc/en-us/articles/38382788311323-Reference-HTTP-export-and-lookup-response-headers-in-transformations](https://docs.celigo.com/hc/en-us/articles/38382788311323-Reference-HTTP-export-and-lookup-response-headers-in-transformations)
