> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/get-http-vars.md).

# Get HTTP Vars

## Description

This part allows application users to access HTTP variables from the URL.

## Use

This part can be used to store the contents of HTTP variables in local data objects. HTTP variables are the elements of a URL after the '?' symbol:

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-8beccafce31088760d6e486d12286911c8d60709%2F8154fa15-c401-4913-a30a-97425145d22c.png?alt=media)

## Editor Fields

| Field Name       | Description/Use                                                 | Type/Options | Optional/Mandatory |
| ---------------- | --------------------------------------------------------------- | ------------ | ------------------ |
| Output name      | This is the data object that will store the variable data.      | Data Object  | Mandatory          |
| Name of var-item | This is the name of the HTTP variable as it appears in the URL. | Text         | Mandatory          |

## Example

Download and import the following [example project](/release-9/example-gallery/example-projects-for-parts/get-http-vars-example-project.md) in your workspace.


---

# 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://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/get-http-vars.md?ask=<question>&goal=<user_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.