Web Connect and Pickup SOAP Service
WebConnect For Pickup Inquiry
Inquire on a pickup via WebConnect
https://www.sefl.com/SeflPickup/servlet/MYSEFL_PICKUPINQUIRE?requestNumber=WEB0000&output=XML
You may enter a single pickup request number via the requestNumber parameter
output=XML returns an XML document otherwise the request will be redirected to a webpage
https://www.sefl.com/SeflPickup/servlet/MYSEFL_PICKUPINQUIRE?requestNumber=WEB0000&output=XML
You may enter a single pickup request number via the requestNumber parameter
output=XML returns an XML document otherwise the request will be redirected to a webpage
Pickup Web Service
Southeastern Freight Lines provides a web service that allows partners to submit
requests
to automatically submit pickups. To use this service, you must have a MYSEFL account with an account number.
To sign up for a MYSEFL account:
request an ID and password.
General Web Service Information
The SEFL pickup service uses a SOAP
interface to communicate data between two automated processes.
To use this service, create a SOAP XML request envelope based on the SeflPickupService WSDL and send it to the web service end point. The web service will receive this request, validate it, and then return a response envelope.
To use this service, create a SOAP XML request envelope based on the SeflPickupService WSDL and send it to the web service end point. The web service will receive this request, validate it, and then return a response envelope.
Sample Pickup Requests
The following are example XML documents that contain requests/responses:
Developer Testing
Developers may test connection and validation by setting the "developer" tag true inside of the "shipper" tag. Example (abbreviated):
<shipper>
<developer>true</developer>
</shipper>
This will test the connection, perform server-side validation, and return a test envelope without submitting an actual pickup request.
Error Responses
The web service will return a response envelope in all cases, however if an error occurs, the pickup request will not be scheduled.
If a server error occurs, the response will contain a fault message.
In some cases, the request may not pass our internal validation, such as invalid zip code, non-service etc. In these cases, an errMessages array will be returned that contains the error messages:
In some cases, the request may not pass our internal validation, such as invalid zip code, non-service etc. In these cases, an errMessages array will be returned that contains the error messages:
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body>
<ns2:PickupResult xmlns:ns2="pickup.sefl.com/xsd">
<errMessages>
<anyType xsi:type="xs:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema">Shipper.zip: Invalid zip code.</anyType>
<anyType xsi:type="xs:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema">Shipper.requestPickupDate: Invalid request pickup date.</anyType>
</errMessages>
<confirmation xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</ns2:PickupResult>
</S:Body>
</S:Envelope>
In this example, the error message returned contains the tag hierarchy where the error occurs, and a message of what the error is.