Send a POST when you can only call GET
A deliberate GET can relay one small POST to a public HTTPS destination.
How it works
Supply an encoded public HTTPS URL and a small JSON or text body. The relay does not forward caller cookies or authorization headers, follow redirects, or reach private network addresses.
Use a stable idempotency key when retrying the same intended action. A new key represents a new action and may send another POST.
GET requests to this endpoint have side effects. Never prefetch, crawl, or embed relay URLs as page resources; do not put credentials or private content in query values.
Quick start
Public API calls use HTTPS GET. This example uses curl to encode query values. Run creation and relay requests deliberately; they can change state.
curl --get 'https://getpostbridge.com/v1/relay' \
--data-urlencode 'url=https://httpbin.org/post' \
--data-urlencode 'json={"message":"hello"}' \
--data-urlencode 'idempotency_key=example-relay-001'Request parameters
| Parameter | What it does |
|---|---|
url | Required public HTTPS destination; this GET sends a downstream POST. |
json / payload | Small JSON or text POST body; provide one of these. |
idempotency_key | Reuse the same key when retrying the same action. |
format | json by default; text returns the downstream body as plain text. |
Response
JSON reports the downstream status and replayed flag. A retry with the same key and payload does not send another POST.
Complete the flow
The response reports the downstream status and whether it was replayed. Reuse the same idempotency_key for a retry; a different key requests another POST. The caller still makes only a GET request.