Geliver integration | Zervanor
← All connectors

Geliver

Also an agent tool
ecommerce

Geliver: Turkish multi-carrier shipping aggregator (Akıllı Kargo Pazaryeri). One REST API over many carriers — create shipments, fetch and accept shipping offers/rates, buy and download labels (PDF/barcode/QR), track parcels, and manage sender/recipient addresses, carrier (provider) accounts, parcel templates, and organization balance. Bearer API-token auth. Change notifications use polling on shipment/tracking updates; native webhooks are documented for reference but are not yet HMAC-verifiable by a supported handler.

27 actions · 1 triggers

The Geliver integration lets you connect Geliver to your automations with 27 actions and 1 triggers — and every action is also a tool an AI agent can call. Examples: List Carrier Accounts, Create Shipment, Get Shipment, List Shipments, Update Shipment Package. No blank-canvas wiring — connect it and use it in your workflows.

Every action below is also a tool an AI agent can call — the same pack powers your workflows and your agents.

Triggers 1

Events in Geliver that can start a workflow.

polling

New or updated shipments (polled)

Polls GET /shipments page by page (order by updatedAt) and emits each new or changed shipment. Set orderBy=updatedAt & order=desc for freshest-first.

Actions 27

What Zervanor can do in Geliver.

Shipments7

POST

Create Shipment

Create a shipment and request carrier offers (POST /shipments). Provide a sender address id plus either a saved recipient address id or an inline recipient address, and parcel dimensions/weight. Geliver returns the shipment with its computed offers (offers[].list). Buying a label is a separate step (Accept Offer). Numeric size/weight fields are sent as strings.

GET

Get Shipment

Get a shipment by id (GET /shipments/{shipmentID}). Returns the full shipment including its offers (offers.list), accepted offer, tracking number, label URLs, and current tracking status.

GET

List Shipments

List shipments (GET /shipments). Page-based pagination via page + limit; the response envelope carries page/limit/totalRows/totalPages. Used for polling new/updated shipments.

PATCH

Update Shipment Package

Update a shipment's parcel dimensions/weight before a label is bought (PATCH /shipments/{shipmentID}). Numeric fields are sent as strings.

DELETE

Cancel Shipment

Cancel a shipment (DELETE /shipments/{shipmentID}).

POST

Create Return Shipment

Create a return shipment from an existing shipment (POST /shipments/{shipmentID}) with isReturn=true. Set willAccept=true to also purchase the return label immediately; otherwise offers are returned to accept later.

GET

Get Shipping Offers

Get the carrier offers/rates computed for a shipment (GET /shipments/{shipmentID}). Offers live inside the shipment at offers.list, with offers.cheapest and offers.fastest highlighted; each offer has an id used to accept it. (Same endpoint as Get Shipment, framed as the rates step of the flow.)

Addresses4

GET

List Addresses

List saved sender and recipient addresses (GET /addresses).

GET

Get Address

Get a saved address by id (GET /addresses/{addressID}).

POST

Create Address

Create a saved sender or recipient address (POST /addresses). Set isRecipientAddress to false for a sender address (zip required) or true for a recipient address (phone required).

DELETE

Delete Address

Delete a saved address by id (DELETE /addresses/{addressID}).

Parceltemplates3

GET

List Parcel Templates

List saved parcel (box) templates (GET /parceltemplates).

POST

Create Parcel Template

Create a reusable parcel (box) template (POST /parceltemplates) with fixed dimensions/weight.

DELETE

Delete Parcel Template

Delete a parcel template by id (DELETE /parceltemplates/{templateID}).

Provideraccounts3

GET

List Carrier Accounts

List the carrier (provider) accounts connected to your Geliver organization (GET /provideraccounts). Safe identity / connectivity probe — verifies the token works.

POST

Create Carrier Account

Connect a carrier (provider) account to your Geliver organization (POST /provideraccounts). Body carries the carrier's providerCode and its credentials.

DELETE

Delete Carrier Account

Disconnect a carrier account (DELETE /provideraccounts/{providerAccountID}).

Transactions3

POST

Accept Offer (Buy Label)

Accept a shipping offer and purchase the label in one call (POST /transactions with offerID). Returns a Transaction whose shipment carries the tracking number and label URLs once the carrier responds.

POST

Buy Label (One-Step)

One-step purchase: post shipment details directly to POST /transactions wrapped as { shipment: {...}, providerAccountID?, providerServiceCode? } to create the shipment and buy the label together. Returns a Transaction.

GET

List Transactions

List label-purchase transactions (GET /transactions). Page-based pagination (page + limit). Useful for polling newly purchased labels.

Webhook3

GET

List Webhooks

List registered webhook subscriptions (GET /webhook). Geliver pushes tracking-update events to these URLs.

POST

Create Webhook

Register a webhook subscription (POST /webhook) so Geliver pushes tracking updates to your URL. Note: within Zervanor this connector's supported trigger is polling — see webhooks docs.

DELETE

Delete Webhook

Delete a webhook subscription by id (DELETE /webhook/{webhookID}).

Cities1

GET

List Cities

List cities for a country (GET /cities?countryCode=...). Used to fill cityCode when creating addresses.

Districts1

GET

List Districts

List districts for a city (GET /districts?countryCode=...&cityCode=...). Used to fill districtID/districtName when creating addresses.

Organizations1

GET

Get Organization Balance

Get the account (organization) wallet balance (GET /organizations/{organizationID}/balance).

PriceList1

GET

List Prices

List the price list for the given query (GET /priceList). Query parameters describe the parcel/route to price.

Automations using Geliver

Build your own automation with Geliver in the visual builder.

Frequently asked questions

What can I automate with Geliver?

27 actions are available — for example: List Carrier Accounts, Create Shipment, Get Shipment, List Shipments, Update Shipment Package, and more.

Which Geliver events can start a workflow?

1 triggers — for example: New or updated shipments (polled).

Can Geliver be used as an AI agent tool?

Yes. Every Geliver action automatically becomes a tool an AI agent can call — the same pack powers both your workflows and your agents.

How is the Geliver integration modelled?

Geliver is modelled as a versioned connector pack, and the steps that need reasoning fall to first-party agents hosted in the same runtime as the workflows.