# Send standard JSON (not URL‑encoded) using HTTP Web Page Submit connector + Token based authentication

**URL:** <https://forum.novacura.com/t/send-standard-json-not-url-encoded-using-http-web-page-submit-connector-token-based-authentication/1108>\
**Category:** Flow Classic\
**Tags:** studio-or-server\
**Created:** [February 23, 2026, 12:15pm UTC](https://forum.novacura.com/t/send-standard-json-not-url-encoded-using-http-web-page-submit-connector-token-based-authentication/1108 "2026-02-23T12:15:57Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![vikolo01](https://avatars.discourse-cdn.com/v4/letter/v/7C9FD7/32.png) [@vikolo01](https://forum.novacura.com/u/vikolo01)\
**Post date:** [February 23, 2026, 12:15pm UTC](https://forum.novacura.com/t/send-standard-json-not-url-encoded-using-http-web-page-submit-connector-token-based-authentication/1108/1 "2026-02-23T12:15:57Z")

</div>

Hi Novacura Gurus!

We are using a scheduled machine workflow in Novacura to send a SQL dataset encoded as JSON via an HTTP POST using the Web Page Submit connector.

At the moment, the connector has predefined Authentication URL and HTTP headers, and it sends the payload as URL‑encoded data, which is an old standard.

**Example**

What we want to send (standard JSON):

JSON

{

“Name”: “John Smith”,

“Age”: 23

}

What is currently being sent at the moment (URL‑encoded):

```auto
Name=John+Smith&Age=23

```

We have now received new requirements from our partner:

1. The payload must be sent as **standard JSON** (not URL‑encoded).

2. Authentication must be updated to use **machine tokens** instead of **basic authentication (username/password)**.

My questions

- Is it possible to build this solution using the **Web Page Submit connector** , or does it only support **URL‑encoded payloads**?

- Since we currently cannot use the **REST connector** , is there any way to:

Or would we need a **workaround** , for example sending the data to **Azure** , and handling the token retrieval and authentication logic there instead?

All creative ideas are most welcome!

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/novacuratalk/original/1X/1faede12bf64d7d1f99ac4d7fc9dc9a2bfce8334.png)

BR,

Viktor