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

# HTTP API

The **JENTIS HTTP API** allows you to send data to JENTIS from any system capable of creating HTTP requests. This enables flexible server-side integrations beyond traditional website-based tracking.

Typical use cases include:

* Reporting **cancelled orders**
* Submitting data from a website where JENTIS cannot be integrated directly
* Sending transaction data from **POS / cash systems**
* Backend-driven events (e.g., CRM updates, subscription status changes)
* Offline-to-online data reconciliation

### Overview

The JENTIS HTTP API is designed for:

* Server-to-server communication
* Backend event reporting
* Secure transmission of tracking data
* Extending JENTIS tracking beyond browser environments

Because the API is HTTP-based, it can be used from:

* Backend systems (Node.js, Java, PHP, Python, etc.)
* ERP systems
* CRM systems
* Order management systems
* POS environments
* Scheduled batch jobs

### Authentication

To use the JENTIS HTTP API, you must obtain a dedicated **API Key**.

> ⚠️ Important\
> You must create a **Helpdesk ticket in JENTIS** to request access and receive your API key for this endpoint.

Without a valid API key, requests will be rejected.


---

# 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.jentis.com/http-api-tracking.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.