⚙️ API Parameter Reference

A comprehensive overview of all Seven Senders Labels API parameters, including usage descriptions, accepted values, and required flags.

This section provides a complete list of all parameters included in the Post Label Request and Post Label Response. For each parameter, you will find a usage description, accepted values, and whether the parameter is required. If you are looking for case-specific or carrier-specific request examples, you can find them here.

POST Labels Request

Below you will find the full set of parameters in a structured JSON format. The comments serve solely to categorize the individual information blocks.

{
  // Sender Address Data
  "sender_first_name": "Max",
  "sender_last_name": "Mustermann",
  "sender_company_name": "Muster GmbH",
  "sender_street": "Senderstraße",
  "sender_house_no": "10",
  "sender_zip": "1010",
  "sender_city": "Wien",
  "sender_country": "AT",
  "sender_phone": "+43123456789",
  "sender_email": "[email protected]",
  "warehouse": "Main Warehouse Vienna",
  "warehouse_address": "Lagerstraße 5, 1200 Wien, AT",

  // Recipient Address Data
  "recipient_first_name": "Anna",
  "recipient_last_name": "Müller",
  "recipient_company_name": "Müller Handels GmbH",
  "recipient_street": "Mariahilfer Straße",
  "recipient_house_no": "74/2",
  "recipient_address_details": "Top 12, Klingel: Müller",
  "recipient_zip": "1060",
  "recipient_city": "Wien",
  "recipient_country": "AT",
  "recipient_phone": "+436601234567",
  "recipient_email": "[email protected]",

  // PUDO (Pickup & Dropoff Point) Address Data
  "pudo_id": "75689",
  "collection_point_name1": "Paketshop Mariahilfer Straße",
  "collection_point_name2": "im Tabak-Trafik",
  "collection_point_name3": "gegenüber U3",
  "collection_point_membership_id": "PUDO123456",
  "collection_point_street": "Mariahilfer Straße",
  "collection_point_house_no": "76",
  "collection_point_zip": "1060",
  "collection_point_city": "Wien",
  "collection_point_country": "AT",

  // Shipment & Order Data
  "reference_number": "your_unique_shipment_reference",
  "reference_number_2": "non_unique_second_shipment_reference",
  "shipment_tag": {
    "tag1": "value1",
    "tag2": "value2"
  },
  "planned_pickup_datetime": "2025-11-22T10:00:00.000Z",
  "order": {
    "order_id": "your_order_id",
    "order_url": "https://www.your_order_url.at",
    "order_date": "2025-11-21T21:59:23.346Z",
    "boarding_complete": true,
    "language": "de",
    "order_tags": {
      "tag1": "value1",
      "tag2": "value2"
    },
    "promised_delivery_date": "2025-11-30T18:00:00.000Z"
  },

  // Base Shipping Label Specification
  "format": "pdf",
  "carrier": {
    "name": "dpd",
    "country": "AT"
  },
  "carrier_service": "standard",
  "carrier_service_id": "b5829462-a792-4441-9f74-f365a07cf41a",
  "return_parcel": "both",
  "weight": 3,
  "dimensions": {
    "height": 30,
    "length": 20,
    "width": 20
  },

  // Goods Value (for Insurance) & Cash on Delivery Data
  "goods_value": 10.5,
  "goods_value_currency": "EUR",
  "cod": true,
  "cod_value": "10.5",
  "cod_currency": "EUR",
  "cod_reference": "COD-REF-12345",


  // Parcel Content & SKUs Data
  "parcel": {
    "description": "Mobile phone case and charger",
    "skus": [
      {
        "article_id": "EP2017002392",
        "country_of_origin": "DE",
        "arrival_country_description": "Liquid silicone case for mobile phone",
        "arrival_country_tariff_number": 6109100000,
        "qty": 3,
        "total_net_weight": 0.2,
        "total_gross_weight": 0.25,
        "sales_value_total": 19.99,
        "currency": "EUR",
        "return_reason": "Mobile phone case was broken",

        // Dangerous Goods Data
        "dangerous_goods": [
          {
            "un_number": "UN3481",
            "hazard_description": "Lithium ion batteries contained in equipment",
            "technical_name": "Lithium ion batteries",
            "hazard_class": "9",
            "harzard_classification_code": "M4",
            "additional_hazard_id": "DG001",
            "packing_group": "II",
            "packing_instruction_code": "965",
            "flash_point": 12,
            "transport_category": "2",
            "tunnel_code": "E",
            "liquid_volume": {
              "unit": "ml",
              "value": 10
            },
            "net_explosive_mass": 0.05,
            "is_limited_quantities": true,
            "container_type": "fiberboard box",
            "hazard_labels_1": "9",
            "hazard_labels_2": "3",
            "hazard_labels_3": "3"
          }
        ]
      }
    ]
  }
}
{
  // unique reference number
  "reference_number": "your_unique_shipment_reference",

  "tracking_code": "061234567890124",
  // In the case of outbound only, the outbound tracking number is returned.
  // For returns only, the return tracking number is provided.
  // For both, only the return tracking number is used as the main reference.

  // Outbound Shipment Data
  "outbound": {
    "label_url": "https://api-uat.sevensenders.com/v2/label-download/98765431",
    "shipment_id": "98765431",
    "tracking_code": "061234567890123",
    "print_format": "A6",
    "mime_type": "application/pdf",
    "pickup_point_selected": true,
    "return_address": {
      "firstName": "Max",
      "lastName": "Mustermann",
      "company": "Muster GmbH",
      "phone": "+43123456789",
      "email": "[email protected]",
      "street": "Senderstraße",
      "streetNo": "10",
      "zipCode": "1010",
      "city": "Wien",
      "country": "AT",
      "addressDetails": null,
      "province": null
    },
    "carrier": {
      "name": "dpd",
      "country": "AT"
    }
  },
  "goods_value": 10.5,
  "goods_value_currency": "EUR",
  "local_delivery": false,
  
  // Return Shipment Data
  "return": {
    "label_url": "https://api-uat.sevensenders.com/v2/label-download/98765432",
    "shipment_id": "98765432",
    "tracking_code": "061234567890124",
    "print_format": "A6",
    "mime_type": "application/pdf",
    "pickup_point_selected": true,
    "return_address": {
      "firstName": "Max",
      "lastName": "Mustermann",
      "company": "Muster GmbH",
      "phone": "+43123456789",
      "email": "[email protected]",
      "street": "Senderstraße",
      "streetNo": "10",
      "zipCode": "1010",
      "city": "Wien",
      "country": "AT",
      "addressDetails": null,
      "province": null
    },
    "carrier": {
      "name": "dpd",
      "country": "AT"
    }
  }
}

Table of Contents - Information Blocks


Sender Address Data

The sender address parameters are all fully optional. The sender information displayed on the label is retrieved from the backend configuration. However, we still recommend providing the values for warehouse and warehouse_address.

Parameter NameRequiredTypeParameter DescriptionAllowed ValuesSample Value
sender_first_nameNostringFirst name of the senderAny stringMax
sender_last_nameNostringLast name of the senderAny stringMustermann
sender_company_nameNostringSender company nameAny stringMuster GmbH
sender_streetNostringSender street nameAny stringSenderstraße
sender_house_noNostringSender house numberAny string10
sender_zipNostringSender zip codeAny valid zip1010
sender_cityNostringSender cityAny stringWien
sender_countryNostringSender country (ISO 3166-1 alpha-2).AT, DE, FR, …AT
sender_phoneNostringSender phone numberAny valid phone number+43123456789
sender_emailNostringSender email addressAny valid email[email protected]
warehouseNostringName of the warehouse from which the parcel is shippedAny stringMain Warehouse Vienna
warehouse_addressNostringFull address of the shipping warehouseAny stringLagerstraße 5, 1200 Wien, A

Recipient Address Data

The recipient address data you submit to the Seven Senders API will either appear on the carrier label and/or be transmitted to the carrier as part of the shipment data. Most of these parameters are mandatory, as they are essential for a successful delivery.

Parameter NameRequiredTypeParameter DescriptionAllowed ValuesSample Value
recipient_first_nameYesstringRecipient first nameAny stringAnna
recipient_last_nameYesstringRecipient last nameAny stringMüller
recipient_company_nameNostringRecipient company nameAny stringMüller Handels GmbH
recipient_streetYesstringRecipient street nameAny stringMariahilfer Straße
recipient_house_noNostringRecipient house number (incl. door if needed)Any string74/2
recipient_address_detailsNostringAdditional address info (e.g. floor, doorbell)Any stringTop 12, Klingel: Müller
recipient_zipYesstringRecipient zip codeAny valid zip1060
recipient_cityYesstringRecipient cityAny stringWien
recipient_countryYesstringRecipient country (ISO 3166-1 alpha-2)AT, DE, …AT
recipient_phoneConditionalstringRecipient phone number.Any valid phone number+436601234567
recipient_emailConditionalstringRecipient email for notificationsAny valid email[email protected]
ℹ️

We strongly recommend providing recipient_first_name and recipient_last_name in their dedicated fields. If this separation is not possible in your system, please submit a hardcoded value for “recipient_last_name”, such as ".".

ℹ️

We strongly recommend providing recipient_street and recipient_street_no in their dedicated fields. If your system does not support splitting the street name and street number, please include the full value in recipient_street and do not populate recipient_street_no.

ℹ️

recipient_email and recipient_phone are conditional parameters. Depending on the carrier service used, they may be mandatory — for example, if the carrier provides notification services via email or phone as part of their offering, such as sending delivery announcements to improve SLA performance or enabling customers to schedule delivery appointments.


PUDO (Pickup & Dropoff Point) Address Data

If you want to address the shipment to a PUDO point, you must provide the PUDO-specific data. The minimum information you should transmit is the PUDO ID, which uniquely identifies a specific carrier PUDO location.

One way to retrieve the correct PUDO IDs for various carriers and their corresponding PUDO addresses is to use the Seven Senders PUDO Locator API [see here].

Parameter NameRequiredTypeParameter DescriptionAllowed ValuesSample Value
pudo_idCstringCarrier-specific pickup point identifier (PUDO ID)Carrier-specific75689
collection_point_name1NostringFirst line of collection point nameAny stringPaketshop Mariahilfer Straße
collection_point_name2NostringSecond line of collection point descriptionAny stringim Tabak-Trafik
collection_point_name3NostringThird line of collection point descriptionAny stringgegenüber U3
collection_point_membership_idCstringMembership or customer ID for the parcel recipientAny stringPUDO123456
collection_point_streetNostringCollection point streetAny stringMariahilfer Straße
collection_point_house_noNostringCollection point house numberAny string76
collection_point_zipCstringCollection point ZIP code.Any valid ZIP1060
collection_point_cityCstringCollection point cityAny valid cityWien
collection_point_countryNostringCollection point country (ISO 3166-1 alpha-2)AT, DE, …AT
ℹ️

Collection Point Parameters and PUDO Fallback

  • The collection_point parameters are helpful in determining a fallback PUDO point, should you choose to enable this functionality.
  • PUDO Fallback: In cases where you do not provide a PUDO ID, your PUDO ID is invalid, or the specified PUDO point is closed, the fallback logic selects the nearest available PUDO point based on the provided collection address.
    • If no collection address data is available, the recipient address data will be used instead for the fallback determination.
🚧

PUDO - edge case Carriers

Some carriers, such as DHL DE (Germany), are an exception when it comes to PUDO shipments. In these cases, no unique PUDO IDs are available and some of the collection point data becomes mandatory. In addition, DHL DE (Germany) uses dedicated collection_membership_id's that are assigned to recipients and are relevant for identifying the parcel recipient.


Shipment & Order Data

The Shipment and Order data only require two mandatory fields - reference_number & order.order_id However, we strongly recommend providing as many fields as possible so you can fully leverage the Seven Senders product portfolio, such as tracking, notifications, and analytics. For more details, see the Seven Senders products [here].

Parameter Name

Required

Type

Parameter Description

Allowed Values

Sample Value

reference_number

Yes

string

Unique shipment reference in your system

Any string

unique_shipment_reference

reference_number_2

No

string

Optional non-unique second shipment reference

Any string

non_unique_shipment_reference

shipment_tag

No

object

Custom tags on shipment level

Key-value pairs

{ "tag1": "value1", "tag2": "value2" }

shipment_tag.tag1

No

string

Custom shipment tag

Any string

value1

shipment_tag.tag2

No

string

Additional shipment tag

Any string

value2

planned_pickup_datetime

No

string

Planned pickup date/time by Seven Senders (ISO 8601)

ISO 8601 datetime

2025-11-22T10:00:00.000Z

order

Yes

object

Container for order-related fields

order.order_id

Yes

string

order ID in your shop/system

Any string

your_order_id

order.order_url

No

string

URL of the shop/marketplace

Any valid URL

https://www.your_order_url.at

order.order_date

No

string

Date/time when the order was placed (ISO 8601)

ISO 8601 datetime

2025-11-21T21:59:23.346Z

order.
boarding_complete

No

boolean

Indicates if all labels for the order are created

true / false

true

order.
language

No

string

Customer/order language (ISO 639-1)

de, en, fr, …

de

order.
order_tags

No

object

Custom tags on order level

Key-value pairs

{ "tag1": "value1" }

order.
order_tags.tag1

No

string

Example order tag

Any string

value1

order.
order_tags.tag2

No

string

Example order tag

Any string

value2

order.
promised_delivery_date

No

string

Promised delivery date/time shown to customer (ISO 8601)

ISO 8601 datetime

2025-11-30T18:00:00.000Z

🚧

Reference_number uniqueness

The reference_number must be unique per shipping label request. For each reference_number, exactly one carrier label is created. It is not possible to generate multiple labels using the same reference_number.

  • If you send the same reference_number multiple times within 48 hours, the API will return the originally created label in the response – regardless of any other changes in the JSON payload.
  • If you send the same reference_number after 48 hours, the API will return an error response.

Base Shipping Label Specification

The following parameters define the label-specific base information. This includes, for example, the label format to be generated, the selected carrier product or service, and whether an outbound label, a returns label, or both should be created.

Parameter Name

Required

Type

Parameter Description

Allowed Values

Sample Value

format

Yes

string

Output format of the generated label/ labels

pdf; png
zpl& zpl300

pdf

carrier

Yes

object

Container for carrier information

carrier.name

Yes

string

Carrier identifier used by Seven Senders

dpd, dhl, gls, …

dpd

carrier.country

Yes

string

Country where the carrier product is configured (ISO 3166-1 alpha-2).

AT, DE, FR, …

AT

carrier_service

No

string

The service type - standard & express

standard,
express

standard

carrier_service_id

No

string

Internal carrier product/service identifier

Carrier specific UUIDs

2a081847-cc29-...

return_parcel

Yes

string

The direction of the label to be created (outbound, return label, or both)

outbound, return, both

outbound

dimensions

C

object

Container for parcel dimensions (cm)

dimensions.height

C

number

Height of the parcel in cm

carrier service specific ranges

30

dimensions.length

C

number

Length of the parcel in cm

carrier service specific rannges

20

dimensions.width

C

number

Width of the parcel in cm

carrier service specific ranges

20

weight

Yes

number

Total parcel weight in kg

carrier service specific ranges

3.3

ℹ️

Carrier.name and carrier.country & carrier_service_id List

  • You can retrieve the list of supported carrier.name and **carrier.country **values through the API (GET v2/carriers - see here).
  • For the corresponding carrier_service_id values associated with each carrier, please reach out to your integration contact. In the future, the available carrier service IDs will also be provided directly via the API.
    • If the carrier_service_id is not transmitted, the system automatically selects the default carrier service configured for your setup.
    • However, when working with different service types—such as PUDO or Home delivery—providing the correct value for each label becomes essential.
🚧

return_parcel for outbound, return or both labels

  • The return_parcel parameter defines whether you want an outbound label, a return label, or both.
  • If set to both, the response returns two label URLs and two tracking codes. This corresponds to the “return label in the outbound box” solution.
ℹ️

Dimensions Data

  • Shipment dimensions may be mandatory or optional depending on the carrier.
    • Some carriers enforce strict validation and require accurate, parcel-specific dimension data.
    • Others are less strict and accept default dimension values. Please coordinate with your integration partner to determine the requirements for your specific carrier setup.

Goods Value & Cash on Delivery Data

The Good Value and COD (Cash on Delivery) parameters are required for specific carrier products.

  • Use the cod parameters to define the payment amount for Cash on Delivery carrier services.
  • The goods_value parameter, on the other hand, specifies the declared value of the shipment for carrier services that include additional insurance.
Parameter NameRequiredTypeParameter DescriptionAllowed ValuesSample Value
goods_valueNonumberTotal goods value of the shipment.≥ 010.5
goods_value_currencyNostringCurrency of goods_value.ISO 4217 codesEUR
codConditionalbooleanIndicates if Cash on Delivery (COD) is enabled.true / falsetrue
cod_valueConditionalstringCOD amount to be collected from the recipient.Decimal as string10.5
cod_currencyConditionalstringCurrency of the COD amount.ISO 4217 codesEUR
cod_referenceNostringReference used for reconciling COD payments.Any stringCOD-REF-12345

Parcel Content and SKU Data

Parcel content and SKU data are rarely required. However, when shipping dangerous goods, certain parcel or SKU fields may become mandatory. Requirements vary by carrier, so please refer to the following documentation Shipping Dangerous Goods.

Parameter NameRequiredTypeParameter DescriptionAllowed ValuesSample Value
parcelCobjectContainer describing parcel contents
parcel.descriptionNostringGeneral description of the parcel contentAny stringMobile phone case and charger
parcel.skus[]CarrayList of SKUs/articles in the parcel
parcel.skus[].article_idNostringSKU or article ID in your systemAny stringEP2017002392
parcel.skus[].country_of_originNostringCountry of origin for customsISO 3166-1 alpha-2DE
parcel.skus[].arrival_country_descriptionNostringItem description required by destination customs.Any stringLiquid silicone case for mobile phone
parcel.skus[].arrival_country_tariff_numberNonumberHS/tariff code used for customs clearanceValid HS code6109100000
parcel.skus[].qtyCnumberQuantity of this SKU≥ 13
parcel.skus[].total_net_weightCnumberTotal net weight (kg) for this SKU line (all items)≥ 00.2
parcel.skus[].total_gross_weightCnumberTotal gross weight (kg) for this SKU line (all items)≥ 00.25
parcel.skus[].sales_value_totalNonumberTotal sales value for this SKU line (all items)≥ 019.99
parcel.skus[].currencyNostringCurrency of sales_value_total.ISO 4217 codesEUR
parcel.skus[].return_reasonNostringReason for return (if this is a return shipment).Any stringMobile phone case was broken

Dangerous Goods Data

Some carriers require a declaration of dangerous goods when shipping such items. The required fields and the level of detail vary significantly by carrier. If you are shipping dangerous goods, please refer to the following documentation Shipping Dangerous Goods.

Parameter Name

Required

Type

Parameter Description

Allowed Values

Sample Value

parcel.skus[].dangerous_goods[]

C

array

List of dangerous goods entries attached to this SKU.

parcel.skus[].dangerous_goods[].
un_number

C

string

UN number of the dangerous goods.

UN + 4 digits

UN3481

parcel.skus[].dangerous_goods[].
hazard_description

C

string

Hazard description according to regulations.

Any string

Lithium ion batteries contained in equipment

parcel.skus[].dangerous_goods[].
technical_name

C

string

Technical name of the dangerous substance/goods.

Any string

Lithium ion batteries

parcel.skus[].dangerous_goods[].
hazard_class

C

string

Hazard class according to ADR/IATA/IMDG.

19

9

parcel.skus[].dangerous_goods[].
harzard_classification_code

C

string

Classification code for the dangerous goods (spelling as in schema).

Depends on DG

M4

parcel.skus[].dangerous_goods[].
additional_hazard_id

C

string

Additional internal or regulatory hazard identifier.

Any string

DG001

parcel.skus[].dangerous_goods[].
packing_group

C

string

Packing group of the dangerous goods.

I, II, III

II

parcel.skus[].dangerous_goods[].
packing_instruction_code

C

string

Packing instruction code (e.g. IATA PI).

Any string

965

parcel.skus[].dangerous_goods[].
flash_point

C

number

Flash point temperature in °C.

≥ 0

0

parcel.skus[].dangerous_goods[].
transport_category

C

string

Transport category according to regulations.

04

2

parcel.skus[].dangerous_goods[].
tunnel_code

C

string

Tunnel restriction code.

AE

E

parcel.skus[].dangerous_goods[].
liquid_volume.unit

C

string

Unit of the liquid volume.

ml, L, …

ml

parcel.skus[].dangerous_goods[].
liquid_volume.value

C

number

Liquid volume value.

≥ 0

0

parcel.skus[].dangerous_goods[].
net_explosive_mass

C

number

Net explosive mass in kg.

≥ 0

0

parcel.skus[].dangerous_goods[].
is_limited_quantities

C

boolean

Indicates shipping under “Limited Quantities” regulation.

true / false

true

parcel.skus[].dangerous_goods[].
container_type

C

string

Type of container/packaging used.

Any string

fiberboard box

parcel.skus[].dangerous_goods[].
hazard_labels_1

C

string

Primary hazard label.

19

9

parcel.skus[].dangerous_goods[].
hazard_labels_2

C

string

Secondary hazard label (if any).

19 or empty

""

parcel.skus[].dangerous_goods[].
hazard_labels_3

C

string

Tertiary hazard label (if any).

19 or empty

""



What’s Next

You can first review which parameters are required for your specific use cases. If you plan to ship PUDO parcels and need to retrieve PUDO data, please refer to our dedicated PUDO solution.