Everest Shipping

Create and track Everest Kargo shipments from your CRM: shipment lists, updates and movement tracking in one panel.

The MyVoipCRM Everest Kargo integration brings shipping operations into the CRM over Everest’s official Webpostman REST API. List the shipments on the Everest side, create, update or delete them, and follow movements and tracking from the same screen. The Everest Kargo PTT carrier option on CRM shipping records is compatible with this integration.

What it does

  • API connection: base address, account email, authorisation key; optional HTTP header names
  • Connection test: with saved settings, or with the form values before saving
  • Shipment list: live from the Everest API; paging, column visibility, Excel export
  • Advanced filters: pick-up date, status, barcode, shipment number, result date, city code, order number, phone and more
  • Creating shipments: recipient, province/district, address, branch code; helper lists for provinces, districts, neighbourhoods, branches, currencies and shipment types
  • Updating shipments: editing an existing shipment on the Everest side (within the address security rules)
  • Deleting shipments: permanent deletion through Everest (with confirmation)
  • Detail and movements: a summary of the shipment fields; a movements tab (the API movement list)
  • Tracking: open the Everest tracking page in a new tab; copy the barcode/shipment number
  • CRM shipments: the “Everest Kargo PTT” carrier on company/branch shipping records
  • Leads / campaigns: an Everest Kargo PTT status and tracking window on lead cards
  • Extra JSON settings: default branch, list date range, fixed extra fields for shipment creation

Menu and screens

  • Everest shipment list — Shipping → Everest Kargo (/e-ticaret/everest-kargolari)
  • Everest API settings — Shipping → Module settings → Everest (/entegrasyon/kargo)
  • CRM shipping records — Shipping → CRM shipments (/kargolar)

Integration settings

  • API base address: e.g. the Everest Webpostman REST client address (provided by the panel)
  • Account email: sent in the request “From” header
  • API authorisation key: the “Authorization” header; required on first save, kept if left empty later
  • HTTP header names: when left empty, the official From / Authorization headers are used
  • Extra settings (JSON): default branch code, list-last-N-days, pick-up date range, default status filter, extra fields for shipment creation
  • Integration active: no API calls are made while off

The shipment list and filters

The list is fetched from the Everest cargo endpoint; paging is applied on the CRM side. Status filter examples: all, accepted, deliveries, returns, notice forms, normal, lost, problematic. Filter by pick-up start/end date, barcode, shipment number (multiple barcodes comma-separated), result (delivery) date range, city code, order number and phone. Recipient name, province, status, result and pick-up/delivery dates show by default; more columns open from the column menu. The filtered list exports to Excel.

Creating and editing shipments

  • Required fields: recipient name, province, district, address, destination branch code
  • Optional: neighbourhood, phone, order number, amount, currency, package count, weight, contents, shipment/fee type, SMS, extra JSON fields
  • Preview and confirm: a summary step before the shipment is created
  • Update rules: per the Everest API, the barcode and destination branch code cannot change on update; because list data may arrive masked, the address is not touched on update — change addresses in the Everest panel
  • Reference (PTT): when the reference field is filled, only 0 or 1 is accepted

Detail, movements and tracking

  • General tab: every shipment field from the API response
  • Movements tab: movement lookups by order or shipment number; a table ordered by date/time
  • Shipments without physical acceptance may have an empty movement list
  • The Everest tracking page opens in a new tab; the barcode copies to the clipboard

CRM shipments and lead tracking

On the CRM shipments screen, company and branch shipping records can use the Everest Kargo PTT carrier. Lead management / manual call campaign cards get an “Everest Kargo PTT — status and tracking” menu for editing shipment details and viewing a tracking summary (summary and movement detail tabs).

Setup

1. Preparing the Everest panel

  • Get the REST API base address, account email and authorisation key from your Everest Kargo / Webpostman account.
  • Note your default destination branch code and the date range you will use for listings.

2. CRM integration settings

  • Open Shipping → Module settings → Everest (/entegrasyon/kargo).
  • Enter the API address, account email and key; define defaultBranchCode and listShipmentsDaysBack in the extra JSON if needed.
  • Run a test with the form values, or a connection test with the saved settings.
  • Activate the integration and save.

3. The shipment list and operations

  • Load the list from Shipping → Everest Kargo (/e-ticaret/everest-kargolari).
  • Apply filters; create shipments with Add shipment, or use detail/edit/delete on a row.
  • Mark the carrier as Everest Kargo PTT when opening a customer/company shipping record in the CRM.

Everest Kargo vs. Aras Kargo. MyVoipCRM offers Everest Kargo (Webpostman REST API) and Aras Kargo under the same Shipping module with separate menus and settings screens. The Everest list is at /e-ticaret/everest-kargolari and the Aras list at /e-ticaret/aras-gonderileri — do not mix them up.

Who it is for

  • E-commerce and logistics teams shipping with Everest Kargo (PTT-backed)
  • Operations teams that want the shipment list and movement tracking in the CRM without opening the Everest panel
  • SMEs managing CRM shipping records and Everest API shipments in one company
  • Sales teams following shipment status on lead / outbound campaign cards

Frequently asked questions

The list is empty or errors out

Check that the integration is active and the connection test passes. Widen the list date range or listShipmentsDaysBack in the extra JSON. Confirm the Everest panel has shipments in that period.

Shipments cannot be created

The required fields (recipient, province, district, address, branch code) must be filled. If no default branch is defined in the JSON, enter a branch code on the form. Read the Everest API error message in the toast notification.

The address does not change on update

By design, the address is not sent to Everest on update (so masked list data is never written back). Use the Everest shipping panel for address changes.

The movements tab is empty

The shipment may not have been physically accepted yet. Make sure the row has an order or shipment number.

From / Authorization errors

If the old custom “ApiFrom” / “ApiAuthorization” header names are saved, clear the fields and save; the default From and Authorization headers are then used.

Which module is required?

The Shipping module is required. Valid Everest account details must be supplied by you; the module licence does not replace the API subscription.