# Get response headers from subgraph services in Apollo router

**URL:** <https://community.apollographql.com/t/get-response-headers-from-subgraph-services-in-apollo-router/5503>\
**Category:** Router\
**Tags:** federation, router\
**Created:** [January 18, 2023, 6:37pm UTC](https://community.apollographql.com/t/get-response-headers-from-subgraph-services-in-apollo-router/5503 "2023-01-18T18:37:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![thatguyking](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/thatguyking/32/2054_2.png) [@thatguyking](https://community.apollographql.com/u/thatguyking)\
**Post date:** [January 18, 2023, 6:37pm UTC](https://community.apollographql.com/t/get-response-headers-from-subgraph-services-in-apollo-router/5503/1 "2023-01-18T18:37:52Z")

</div>

I am currently running a federation service and in the process of migrating to Apollo-router. Currently, I am stuck on getting response headers in the `execution_service` stage. My `Authentication-service` handles user login and on successful login I set a response header with the key `token` and the value is the corresponding JWT. I want to be able to get this header in my Apollo router and then subsequently store that in a cookie on the browser and then send that cookie (by converting it to a header) and passing it to subgraphs on subsequent requests.

How do I go about this?

---

<div class="post-metadata">

**Author:** ![watson](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/watson/32/2053_2.png) [@watson](https://community.apollographql.com/u/watson)\
**Post date:** [January 18, 2023, 10:24pm UTC](https://community.apollographql.com/t/get-response-headers-from-subgraph-services-in-apollo-router/5503/2 "2023-01-18T22:24:03Z")

</div>

You should be able to have the headers coming into the Apollo Router propagate to downstream services ([docs](https://www.apollographql.com/docs/graphos/routing/cloud-configuration#http-header-rules)). This could be used to forward the `cookie` header to downstream subgraphs.
