> For the complete documentation index, see [llms.txt](https://docs.qubitro.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qubitro.com/data-sources/http.md).

# HTTP

Send JSON payloads from your devices or applications to Qubitro via a simple HTTP endpoint.

HTTP provides a straightforward way to send data from your devices or applications to Qubitro. 

By making an HTTP POST request to Qubitro’s webhook endpoint, you can securely transmit JSON payloads for storage and further processing.

### Specifications

<table><thead><tr><th width="197">Parameter</th><th>Description</th></tr></thead><tbody><tr><td>Endpoint</td><td>https://webhook.qubitro.com/integrations/http</td></tr><tr><td>Method</td><td>POST</td></tr><tr><td>Data Format</td><td>Valid JSON is required by default.</td></tr><tr><td>Content-Type</td><td>application/json</td></tr><tr><td>Authorization</td><td>Basic (Device Token from Qubitro)</td></tr></tbody></table>

{% hint style="warning" %}
Qubitro rejects any request that does not contain valid JSON. Make sure your payload is properly formatted.
{% endhint %}

#### Example CURL Command

Use the Device Token as your Basic authorization header. Replace the placeholder token below with the one from your Unique IDs card.

```bash
curl --location 'https://webhook.qubitro.com/integrations/http' \
  --header 'Authorization: Basic <YOUR_DEVICE_TOKEN>' \
  --header 'Content-Type: application/json' \
  --data '{ "Temperature": 30.5 }'
```

This request sends a JSON payload containing `"Temperature": 30.5` to Qubitro. Make sure your payload follows valid JSON formatting to ensure successful ingestion.

### Create an HTTP Source

{% stepper %}
{% step %}
**Navigate to the Project Detail Page**

Go to the project where you want to create an HTTP source.
{% endstep %}

{% step %}
**Create a New Source**

Click **New Source**, then select **HTTP** from the available options.
{% endstep %}

{% step %}
**Fill Out the Required Information**

Enter details according to your configuration needs.
{% endstep %}

{% step %}
**Create & Verify**

Click **Create**. Qubitro automatically generates the **Device ID** and **Device Token**. Verify these credentials in the **Device Settings** under the **Unique IDs** card.
{% endstep %}
{% endstepper %}


---

# 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://docs.qubitro.com/data-sources/http.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.