> For the complete documentation index, see [llms.txt](https://apidocs.gsped.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apidocs.gsped.com/gsped-api-english-version/spedizioni-e-dintorni/shipment/casi-duso/pudo-punti-di-ritiro.md).

# PUDO (pickup points)

Pickup points are supported for several couriers. This page lists the data to pass in the shipment POST call to send the pickup point information to the courier.

## BRT - TNT - DHL - GLS - COLISSIMO-InPOST

Enter the PUDO / dropoff point identification code in the **generic\_service*****\_*****point** field

```json
{
    "generic_service_point":""
}
```

<table data-full-width="true"><thead><tr><th width="248">Field</th><th width="116" data-type="checkbox">Required</th><th width="84">Type</th><th>Description</th></tr></thead><tbody><tr><td>generic_service_point</td><td>true</td><td>string</td><td>PUDO identification code<br>N.B. for GLS in the form {PARTNER_SHOP_ID}-{SHOP_ID}</td></tr></tbody></table>

{% hint style="info" %}
COLISSIMO: service points can only be used with the OUT HOME courier service, Gsped service id 3
{% endhint %}

## UPS

This courier requires the full pickup point data along with its identification code.

```json
"ups_uap_id": "",
"uap": [
    {
        "address": "",
        "city": "",
        "country_code": "",
        "name": "",
        "postal_code": "",
        "state_province_code": ""
    }
]
```

<table data-full-width="true"><thead><tr><th width="248">Field</th><th width="116" data-type="checkbox">Required</th><th width="84">Type</th><th>Description</th></tr></thead><tbody><tr><td>ups_uap_id</td><td>true</td><td>string</td><td>PUDO identification code</td></tr><tr><td>uap.address</td><td>true</td><td>string</td><td>PUDO address</td></tr><tr><td>uap.city</td><td>true</td><td>string</td><td>PUDO city</td></tr><tr><td>uap.country_code</td><td>true</td><td>string</td><td>PUDO country ISO 2 Char</td></tr><tr><td>uap.name</td><td>true</td><td>string</td><td>PUDO name</td></tr><tr><td>uap.postal_code</td><td>true</td><td>string</td><td>PUDO ZIP code</td></tr><tr><td>uap.state_province_code</td><td>true</td><td>string</td><td>PUDO province code</td></tr></tbody></table>

## SDA/Crono

This courier requires the full pickup point data along with its identification code.

```json
"sda_id_fermoposta":"",
"sda_fermoposta":{
    "state_province_code":"",
    "name":"",
    "address":"",
    "city":"",
    "postal_code":""
}
```

<table data-full-width="true"><thead><tr><th width="334">Field</th><th width="116" data-type="checkbox">Required</th><th width="84">Type</th><th>Description</th></tr></thead><tbody><tr><td>sda_id_fermoposta</td><td>true</td><td>string</td><td>PUDO identification code</td></tr><tr><td>sda_fermoposta.state_province_code</td><td>true</td><td>string</td><td>PUDO province/state code</td></tr><tr><td>sda_fermoposta.name</td><td>true</td><td>string</td><td>PUDO name</td></tr><tr><td>sda_fermoposta.address</td><td>true</td><td>string</td><td>PUDO address</td></tr><tr><td>sda_fermoposta.city</td><td>true</td><td>string</td><td>PUDO city</td></tr><tr><td>sda_fermoposta.postal_code</td><td>true</td><td>string</td><td>PUDO ZIP code</td></tr></tbody></table>

## POSTE Delivery Business

PosteDB handles the pickup point as an accessory service, distinguishing by the type of point. For pickup points, fill in an object in the **pdb\_accessori** array with the elements accessorio, param1 and param2. Param1 contains the point code, param2 the point name, and accessorio is one of these strings depending on the type of point.

```json
"pdb_accessori":[
    {
        "accessorio":"",
        "param1":"",
        "param2":"",
        "param3":"",
        "param4":""
    }
]
```

<table data-full-width="true"><thead><tr><th width="334">Field</th><th width="116" data-type="checkbox">Required</th><th width="84">Type</th><th>Description</th></tr></thead><tbody><tr><td>accessorio</td><td>true</td><td>enum</td><td>Depending on the PUDO:<br>- ConsegnaPUDOUPS<br>- ConsegnaPuntoPoste<br>- ConsegnaLocker<br>- ConsegnaUfficioPostale</td></tr><tr><td>param1</td><td>true</td><td>string</td><td>PUDO identification code</td></tr><tr><td>param2</td><td>true</td><td>string</td><td>PUDO name</td></tr><tr><td>param3</td><td>false</td><td>string</td><td>not used</td></tr><tr><td>param4</td><td>false</td><td>string</td><td>not used</td></tr></tbody></table>

## DHL Parcel Connect (169)

This courier requires the access point identification code (KeywordID) together with the ZIP code, city and country where it is located.

Example:

```json
"accessPoint": {
        "apId": "501",
        "apCity": "Zukowo",
        "apPostalCode": "83-330",
        "apCountryCode": "PL"
}
```

For Germany and Luxembourg a recipient identification code is also required, because recipients must be registered to receive shipments at Access Points.

Example:

```json
"accessPoint": {
        "apId": "501",
        "apCity": "Berlin",
        "apPostalCode": "10557",
        "apCountryCode": "DE",
        "apAncillaryData": {
                "customerId": "123456"
        }
}
```

#### Handling Access Point identifiers coming from Zalando

For orders coming from Zalando, when the customer has requested delivery to an Access Point, the platform returns a specific identifier for the access point chosen by the customer. This identifier cannot be used in the **apId** field; instead, you must specify it in the **zalandoServicePointID** field.

Example:

```json
"accessPoint": {
        "zalandoServicePointID": "4517265",
        "apCity": "Zukowo",
        "apCountryCode": "PL"
}
```
