FAQ

Error on request interface: Could not connect to host

The variable “stream_context” only has to be set in the sample or dev system, in the live environment this has to be omitted.
The certificate used for the sample, dev or production system is specified in the “local_cert” variable.

Error on request interface: Not Extended

The path to the specified certificate is incorrect.

Use the login data of your UP customer account to register.

• print24: e-mail address and password
• SOAP API: customer number and password (+Certificate)
• REST API: e-mail address and password

Examples of the USS Connect Web Service Description Language (WSDL) can be found at the following link: http://upi.unitedprint.com

The standard UPI tracking function is a simple HTTP callback.

For defined events in the creation process, status changes with definable parameters are transmitted to a URL that they announced.

Below are two examples of a status change (to “Cancellation”) based on the order_number 999999
as well as the customer_number 1234567.

HTTP JSON callback
https://your_url.de/?execute=join/unitedprint.job/state-set&order_number=9999999&item_group_name=flyer&customer_item_name=myfirst order&actual_state=order_stati_7000_4&shipment_number=1&customer_number=1234567

HTTP callback
https://your_url.de/tracking.php?order_number=999999&item_group_name=flyer&customer_item_name=myfirst order&actual_state=order_stati_7000_4&shipment_number=1&customer_number=1234567

This PHP call writes a “tracking.log” in the same directory with the parameters previously defined by you.

Tracking.php

The status of an order is not queried via the interface. Instead, information is returned to the partner via the interface.

When the status in the UP system is changing, a script can be called up by  the partner using a so-called “http callback”. This is possible for every relevant status change.

Possible status changes are

• Acknowledgement of order
• Data processing
• Pooling
• Processing
• Shipping deployment
• Dispatch/Shipping
• Cancellation

Different values can be transferred for each script.

Can be selected

• General information
• Order number
• Location information
• Status
• Delivery date
• Position number
• Item delivery information
• Delivery service (Carrier)
• Tracking number
• Subset

Return values / mapping delivery service (Carrier service)[carrier_service_id]

• 2 DPD (www.dpd.com)
• 26 DHL Express National (www.dhl.de)
• 27 DHL Express International
• 31 Schenker (www.schenker.com)
• 35 Schenker (www.schenker.com)
• 49 DPD (www.dpd.com)
• 50 DPD (www.dpd.com)
• 52 GEL (www.gel-express.de)
• 77 DHL Packet
• 76 DHL Economy Select
• 82 FedEx Regional Economy (www.fedex.com)
• 83 FedEx International Economy (www.fedex.com)
• 84 FedEx International Priority Express (www.fedex.com)
• 85 FedEx First
• 86 FedEx Priority
• 87 FedEx Priority Express
• 88 DPD Classic
• 106 DHL Retail package

Return values / mapping status values

• order_stati_1000_4 Acknowledgement of order
• order_stati_1500_4 File check
• order_stati_1600_4 Customize release
• order_stati_1750_4 Data processing
• order_stati_2000_4 Pooling
• order_stati_3000_4 Pre-press stage
• order_stati_3400_4 Plotting
• order_stati_3600_4 Stamping
• order_stati_3700_4 Plating
• order_stati_4000_4 Printing
• order_stati_5000_4 Finishing
• order_stati_5400_4 Ready for dispatch
• order_stati_5800_4 Dispatch stopped
• order_stati_6000_4 Dispatched
• order_stati_7000_4 Cancellation

UP must activate the authorization to transmit the tracking information explicit for you. For this it is necessary to give us a callback URL.

Tracking examples you can find here.

Currently, no plug-in for third party eCommerce or Onlineshop systems such as Magento, PrestaShop, SAP etc. can be provided for USS Connect.

This largely depends on the technological environment used and how you want to integrate the interface into your processes.

As a rule, the integration should be completed within a few days.

For all example scripts, the contents of the required fields for password, customerNumber and portalName must be replaced with the values sent to you by UP.

$args -> accountInformation -> password = ‘pwd’;
$args -> accountInformation -> customerNumber = 123456789;
$args -> accountInformation -> portalName = ‘portal’;
$args -> accountInformation -> languageCode = ‘de’;
$args -> accountInformation -> countryCode = ‘DE’;

You will receive three independent communication certificates for using the SOAP interface.
These certificates are used both for communication with the product catalog and for order creation.

sample_cert
Certificate for access to the test environment:
client certificate (click to download)

You will receive the certificates for your individual test (dev_cert) and productive system (prod_cert) after signing the contract by e-mail.

dev_cert
soap service = http://interface.onts.unitedprint.dev/
It is a test server with the same catalog as your production system. You can test orders without consequences.

Note
This test system is overwritten every night by your online product configurations.
Attention
Do not confuse your dev_cert with public sample_cert on our example page

prod_cert
soap service = interface.unitedprint.com
Orders on this system are recorded in the Unitedprint production system as an order including the corresponding booking.

In the event of an inadvertent order, immediately inform print24 support so that the order can be canceled free of charge.

Note
Use our service from Monday to Friday from 8 a.m. to 6 p.m.
ServiceCall 0351/79550650
Send us your questions or requests via e-mail at any time support@print24.de.

Das SOAP Array ist wie nachfolgend beschrieben aufgebaut.

$options = array(
‘soap_version’ => SOAP_1_1,’exceptions’ => true,
‘trace’ => 1,
‘cache_wsdl’ => WSDL_CACHE_NONE,
‘local_cert’ => ‘C:/xampp/htdocs/js/Certs/sample.cert’,
‘charset’ => ‘utf8’,
‘stream_context’ => stream_context_create([‘ssl’ => [‘verify_peer’ => false, ‘verify_peer_name’ => false, ‘allow_self_signed’ => true]])
);

Note
The variable “stream_context” only needs to be set in the sample or dev system. This has to be omitted in the live environment.

The certificate used for the sample, dev or productive system is specified in the “local_cert” variable.

The web service is specified in the variable $ soap_service.

Sample and Dev
http://interface.onts.unitedprint.dev/wsdl2.1

Productive
http://interface.unitedprint.com/wsdl2.1