# How can I get the response header using Call API
**URL:** https://community.glideapps.com/t/how-can-i-get-the-response-header-using-call-api/67210
**Category:** Ask for Help
**Created:** [October 23, 2023, 10:49am UTC](https://community.glideapps.com/t/how-can-i-get-the-response-header-using-call-api/67210 "2023-10-23T10:49:32Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@Jeonghwan\_You](https://community.glideapps.com/u/Jeonghwan_You)
#### Post date: [October 23, 2023, 10:49am UTC](https://community.glideapps.com/t/how-can-i-get-the-response-header-using-call-api/67210/1 "2023-10-23T10:49:32Z")
What I want to do using Call API in Glide is getting resltID after sending the POST using Form Recognizer API from response header to send GET method for checking result.
Call API to get the result, the cell is empty because the response JSON file contains nothing. That’s why I have to look for the resultID in the response header.
[Cognitive Services APIs Reference (microsoft.com)](https://westus.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-2023-07-31/operations/AnalyzeDocument)
[POST response]
> **[Use Document Intelligence client library SDKs or REST API - Azure AI services](https://learn.microsoft.com/en-us/azure/ai-services/document-intelligence/how-to-guides/use-sdk-rest-api?view=doc-intel-3.1.0&tabs=windows&pivots=programming-language-rest-api#post-response)**
>
> Learn how to use Document Intelligence SDKs or REST API and create apps to extract key data from documents.
---
### Author:  [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)
#### Post date: [October 24, 2023, 1:07am UTC](https://community.glideapps.com/t/how-can-i-get-the-response-header-using-call-api/67210/2 "2023-10-24T01:07:32Z")
I’m not sure if it would work, but maybe you can try using JavaScript to fetch the URL and write a snippet that would return a header, opposed to using Call API, which might only ever return the body.
---
### Author:  [@Jeonghwan\_You](https://community.glideapps.com/u/Jeonghwan_You)
#### Post date: [October 25, 2023, 4:33am UTC](https://community.glideapps.com/t/how-can-i-get-the-response-header-using-call-api/67210/3 "2023-10-25T04:33:54Z")
Thank you. I solve this problem using http module in [Make.com](http://Make.com).
Even if I’m using a business plan, it’s very inconvenient to have to use [make.com](http://make.com) to implement these features.
---
### Author:  [@Robert\_Petitto](https://community.glideapps.com/u/Robert_Petitto)
#### Post date: [December 3, 2025, 8:53pm UTC](https://community.glideapps.com/t/how-can-i-get-the-response-header-using-call-api/67210/4 "2025-12-03T20:53:37Z")
Just ran into this today. Two years later and no improvement to the action it seems 😒 . Guess we need to make this a feature request?
---
### Author:  [@nathanaelb](https://community.glideapps.com/u/nathanaelb)
#### Post date: [January 5, 2026, 5:58am UTC](https://community.glideapps.com/t/how-can-i-get-the-response-header-using-call-api/67210/5 "2026-01-05T05:58:27Z")
I understand that working with APIs and JavaScript and the Make integration make Glide (no pun intended) that much more powerful. Unless Glide has changed its original mission statement from way back when (to allow 1 billion people/creators to build apps by 2030, basically by turning 1 billion Excel users into app builders), then APIs and JavaScript and Make are totally out of scope if Glide is to pursue its original mission statement.
---
### Author:  [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)
#### Post date: [January 5, 2026, 6:03am UTC](https://community.glideapps.com/t/how-can-i-get-the-response-header-using-call-api/67210/6 "2026-01-05T06:03:03Z")
> [@Robert\_Petitto](#):
>
> Guess we need to make this a feature request?
It already is…
>
>
> Extend the Call API action so builders can read and use HTTP response headers in… their app logic, not just the response body and status code.
>
> \## Summary
> Currently, the Call API action only exposes the \*\*Response Body\*\* and \*\*Status Code\*\* as outputs. Many APIs rely on HTTP response headers to deliver important metadata, such as pagination cursors, rate limit info, auth/refresh tokens, or custom application signals. Without access to headers, builders cannot fully integrate with these APIs using Call API alone and must resort to workarounds or external tooling (e.g. Make, Zapier, etc).
>
> \## Current Problem
> \- The Call API action returns:
> - Response Body
> - Status Code
> \- It does \*\*not\*\* expose:
> - Response Headers (e.g., \`Location\`, \`Link\`, \`X-RateLimit-Remaining\`, \`X-Next-Page\`, \`Set-Cookie\`, etc.)
> \- As a result:
> - Builders cannot read pagination cursors or continuation tokens that are only sent in headers.
> - Apps cannot react to rate limit or quota information from headers.
> - Any flows that depend on header-based data (e.g., auth flows, custom metadata) are blocked or require non-native workarounds.
> \## Examples/Scenarios
> \- \*\*Pagination cursors:\*\*
> An API returns the next page cursor in a header like \`X-Next-Page\`. The app needs this value to fetch the next page of results, but it’s inaccessible via Call API today.
> \- \*\*Rate limiting:\*\*
> The API returns rate limit info (\`X-RateLimit-Remaining\`, \`X-RateLimit-Reset\`) in headers so the client can throttle or inform the user — but the app cannot see those values.
> \- \*\*Redirects or resource locations:\*\*
> A POST request creates a resource and returns the new resource URL in the \`Location\` header. The app can’t easily capture and store that URL.
> \- \*\*Auth / token management:\*\*
> Some APIs return refreshed tokens in headers (e.g., \`Set-Cookie\`, \`X-Auth-Token\`). Without header access, automated token refresh flows are not possible with Call API alone.
> \- \*\*Custom app metadata:\*\*
> Third-party APIs may use custom headers (\`X-\*\`) to indicate things like internal IDs, state flags, or security info required for subsequent calls.
> \## Why This Matters
> \- \*\*Unlocks more APIs\*\*: Many modern APIs rely on headers for critical metadata. Exposing headers makes Glide’s Call API action more robust and compatible.
> \- \*\*Reduces workarounds\*\*: Avoids the need for proxy servers or external middleware just to capture and forward headers into Glide.
> \- \*\*Better UX & reliability\*\*: Apps can handle rate limits, pagination, and auth flows more gracefully, improving end-user experience.
> \- \*\*Aligns with developer expectations\*\*: Most HTTP client libraries expose headers and body together. Bringing Glide in line with this makes the platform feel more complete and professional.
> \## Suggested UX
> \- \*\*New output field in Call API configuration:\*\*
> - Add a “Response Headers” section to the Call API result settings.
> - This could be:
> - A \*\*JSON object\*\* containing all headers (key-value pairs), or
> - A dedicated \*\*collection of “Header Name → Value” pairs\*\*.
> \- \*\*Header selection & mapping:\*\*
> - Allow builders to:
> - Store the full headers object in a JSON column, \*\*and/or\*\*
> - Select specific headers to map directly to columns (e.g., \`X-Next-Page\` → “Next Page Cursor” column).
> \- \*\*Consistency with existing outputs:\*\*
> - Display “Response Headers” alongside “Response Body” and “Status Code” in the Call API action sidebar.
> - Ensure headers are available in subsequent actions/conditions within the same workflow (e.g., use a specific header value in a conditional step).
> \- \*\*Developer experience:\*\*
> - Provide documentation showing:
> - How to reference a specific header (e.g., \`response.headers\["X-Next-Page"\]\` pattern in Glide’s UI).
> - Examples for pagination, rate limiting, and token refresh flows using headers.
---
### Author:  [@Robert\_Petitto](https://community.glideapps.com/u/Robert_Petitto)
#### Post date: [January 5, 2026, 11:53am UTC](https://community.glideapps.com/t/how-can-i-get-the-response-header-using-call-api/67210/7 "2026-01-05T11:53:55Z")
> [@nathanaelb](#):
>
> Unless Glide has changed its original mission statement from way back when (to allow 1 billion people/creators to build apps by 2030, basically by turning 1 billion Excel users into app builders), then APIs and JavaScript and Make are totally out of scope if Glide is to pursue its original mission statement.
@david