---
title: "HTTP API (logs) | Grafana Labs"
description: "Sending logs via HTTP API to Grafana Cloud"
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

## HTTP API for logs

**What it’s for:** Proof-of-concept tests, development work, or last resort when other options aren’t available.

**HTTP API** is a simple REST endpoint for sending logs to Loki (any HTTP client can use it).

[HTTP API logs flow](http-api-logs-flow.svg "HTTP API logs flow")

> **Note:** Not recommended for production environments. Use a robust collector like Grafana Alloy, Promtail, or Fluent Bit for production logging instead.

## Trade-offs

**Best for:** Quick POC tests, development, or when other pathways are unavailable

| Pros                       | Cons                                    |
|----------------------------|-----------------------------------------|
| Works with any HTTP client | Not recommended for production          |
| No special SDK or protocol | You handle batching and retries         |
| Simple JSON format         | No built-in buffering or error handling |
| Great for testing and POCs | Manual formatting required              |

## Documentation

View the full documentation. *Learning path coming soon!*

[HTTP API for logs](https://grafana.com/blog/how-to-use-http-apis-to-send-metrics-and-logs-to-grafana-cloud/#sending-logs-using-the-http-api)