# Using tokens

Once you’ve specified where to deliver tokenized data, you have to specify what to deliver. We establish a forward proxy solution, where you send us an http request with the target url, connection credentials and tokenized data. 

There are four basic properties that define the distribution of tokenized data:

* the URL to submit data to
* the HTTP request header
* the HTTP request method
* the HTTP request body (containing tokens)

A simple deliver request might look like the following:

```sh
curl https://console.payengine.co/api/v2/forwardproxy \
  -H 'Authorization: Basic <Private_API_KEY>' \
  -H 'Content-Type: application/json' \
  -d '{
        "data": {
          "url": "https://<targethost>",
          "headers": "Content-Type: application/json",
          "body": "{ \"ssn\": \"{{ssn}}\", \"bankAccount\": \"{{bank_account}}\" }"
        }
      }'
```


---

# Agent Instructions: 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:

```
GET https://docs.payengine.co/developer-docs/processing-payments/secure-fields/using-tokens.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.