Skynet Shipment API

Overview

This API lets Skynet register shipments directly in the FS Logistik order system and check where each one stands. Every shipment is bound to the Skynet account, so it appears in the FS Logistik panel with all other work under that account.

The API covers two jobs and deliberately nothing else:

• Create a shipment — sender, receiver, and package details in, an FS Logistik order number out.
• Track a shipment — current status and the status history for a shipment Skynet created.

Rates and prices are not part of this API. Pricing is calculated on the FS Logistik side from the account's price list and never returned in any response. There is no rate-quote endpoint.

Base URLs

All requests and responses are JSON. Send Content-Type: application/json and Accept: application/json. Timestamps are ISO 8601 with an offset, in Europe/Copenhagen time.

Getting started

1. FS Logistik opens a partner account for Skynet in its admin panel and assigns it a price list and payment terms.
2. FS Logistik sends Skynet the account's email address and password over a secure channel.
3. Skynet calls POST /token once with those credentials and stores the API token it returns. The password is never sent again.
4. Skynet integrates against the sandbox base URL and creates a few test shipments end to end.
5. FS Logistik reviews the sandbox shipments in the panel, then opens the production account.

Authentication

Skynet has an account in the FS Logistik panel. Its email and password are exchanged once for a long-lived API token, and every later request carries that token. The password is never sent again.

{
  "email": "api@skynet.example",
  "password": "the account password",
  "name": "Skynet integration"
}

{
  "token": "sk_live_9f2c41a7e8b34d05a6c1e7fbd9204e83",
  "token_type": "Bearer",
  "account": "SkyNet",
  "created_at": "2026-08-27T14:02:11+02:00"
}

Using the token

Every other request carries the token as a bearer token. It does not expire on its own; it stops working when FS Logistik revokes it.

Authorization: Bearer sk_live_9f2c41a7e8b34d05a6c1e7fbd9204e83
Content-Type: application/json
Accept: application/json

A missing, malformed, or revoked token returns 401. The token identifies the account, so no account or customer id is ever sent in a request body — a shipment always belongs to the token that created it, and only that account can read it back.

Postman collection

Every endpoint on this page, with example requests and responses, ready to run.

Download the Postman collection (JSON, Postman v2.1 — import it with File → Import).

Fill in the email and password collection variables, run Get an API token once, and the token is stored automatically for the other requests. The collection defaults to the sandbox base URL.

Create a shipment

{
  "reference": "SKY-889271",
  "order_type": "package",
  "content_description": "Textile samples",
  "sender": {
    "name": "Atlas Tekstil A.S.",
    "phone": "+90 212 555 0134",
    "email": "export@atlastekstil.com",
    "company_name": "Atlas Tekstil A.S.",
    "address": {
      "street": "Mahmutbey Mah. Taşocağı Cad. No 12",
      "city": "Istanbul",
      "postal_code": "34218",
      "country_code": "TR"
    }
  },
  "receiver": {
    "name": "Lise Andersen",
    "phone": "+45 26 13 42 16",
    "email": "lise.andersen@example.dk",
    "address": {
      "street": "Nyholms Alle 30 B, 2. th",
      "city": "Rodovre",
      "postal_code": "2610",
      "country_code": "DK"
    }
  },
  "packages": [
    { "quantity": 1, "weight_kg": 2.4, "length_cm": 40, "width_cm": 30, "height_cm": 20 }
  ]
}

{
  "reference": "SKY-889271",
  "order_number": "20260827004",
  "status": "pending",
  "created_at": "2026-08-27T14:12:08+02:00"
}

Track a shipment

{
  "reference": "SKY-889271",
  "order_number": "20260827004",
  "status": "shipped",
  "status_label": "Shipped",
  "carrier": "ups",
  "tracking_number": "1ZK919J46899000001",
  "updated_at": "2026-08-29T09:41:55+02:00",
  "history": [
    { "status": "pending",    "occurred_at": "2026-08-27T14:12:08+02:00" },
    { "status": "processing", "occurred_at": "2026-08-28T08:30:11+02:00" },
    { "status": "shipped",    "occurred_at": "2026-08-29T09:41:55+02:00" }
  ]
}

List shipments

{
  "data": [
    { "reference": "SKY-889271", "order_number": "20260827004", "status": "shipped",
      "updated_at": "2026-08-29T09:41:55+02:00" }
  ],
  "meta": { "page": 1, "per_page": 50, "total": 1 }
}

Statuses

A shipment always sits in exactly one of these. They are the same values FS Logistik staff see in the panel.

New statuses may be added over time. Treat an unrecognised value as "in progress" rather than failing.

Errors

Errors use standard HTTP status codes with a consistent body. Field-level problems are listed under errors, keyed by the field path from the request.

{
  "success": false,
  "message": "Validation failed",
  "errors": {
    "packages.0.weight_kg": ["The weight must not be greater than 30."],
    "receiver.address.postal_code": ["The receiver postal code is required."]
  }
}

Limits

These mirror the limits already enforced in the FS Logistik order system. If Skynet's shipments regularly fall outside them, say so before integration — the limits can be raised per account, but only deliberately.

Open points

Three things are still to be agreed between FS Logistik and Skynet. None of them change the shape of the API, but all three need an answer before the production key is issued.

• Payment terms. Whether the Skynet account is prepaid or invoiced, and on what cycle.
• Weight and dimension limits. Whether the standard limits above cover Skynet's traffic.
• Cancellations. Whether Skynet needs to cancel a shipment through the API, or whether cancellation stays a manual request to FS Logistik.

Questions on this document go to FS Logistik before any code is written against it.