Send data to a Webhook¶
Use Webhook when the finished file should be posted to an HTTP endpoint.
This Destination delivers the converted dataset. It does not report whether a Job succeeded. For Job outcome notices, see Job Notifications.
You need to be signed in.
Before you start¶
You'll need an HTTPS (or HTTP) endpoint that accepts POST or PUT, and any credentials that endpoint requires.
Do not put tokens in the URL query string. GeoJibe rejects webhook URLs that include ?… so secrets are not stored in visible configuration.
1. Save a Webhook Destination¶
Open Destinations → Add Destination → Webhook.
| Field | What to enter |
|---|---|
| Endpoint URL | For example https://api.example.com/import |
| Method | POST or PUT |
| Authentication | None, Basic, or Bearer |
Optional Advanced options:
- Custom headers (values are treated as secrets)
- Multipart field name (default
file) - Timeout
- Expected success codes (leave empty for any HTTP 2xx)
Click Send test request, then Save.
Send test request posts a small JSON payload ({"source":"geojibe","message":"GeoJibe webhook test"}). It does not send your dataset. Use it to check reachability and authentication, not as a generic contract validator.
Name the connection something reusable, for example Production Processing API.
2. Add your data¶
Upload or import, then Convert if you need a specific output format. The file GeoJibe sends is the converted result.
3. Choose Webhook¶
On the Canvas, add Webhook from Destinations. In Classic Wizard, choose Webhook as the Destination.
Select the saved Destination (or configure the endpoint for a one-off run).
Request format:
| Format | What GeoJibe sends |
|---|---|
| Multipart file (default) | multipart/form-data with the file in the field you named (file by default), using the real filename and an appropriate Content-Type |
| Raw body | The file bytes as the request body, with a Content-Type such as GeoJSON, CSV, or a binary type |
GeoJibe streams the file. It does not base64-encode it into JSON.
Each delivery includes X-GeoJibe-Run-ID when a Job run ID is available. GeoJibe does not automatically retry POST/PUT after the body has been sent — a timeout might already have been accepted by the remote system.
4. Run¶
Click Run or Send to Webhook. Saved Jobs use the same Destination on Run Now and on the schedule. There is no separate webhook scheduler.
A successful delivery is HTTP 2xx (or the success codes you listed). GeoJibe records the status code and duration. It does not store large response bodies.
What happens next?¶
The remote endpoint has the converted file. Check that system's logs or import queue.
If the request fails, GeoJibe reports a useful class of error (DNS, connection refused, TLS, timeout, HTTP 4xx/5xx, and so on) without echoing secrets or Authorization headers.