FAIL: UPS Developers Guide

I can’t describe the frustration and vile feelings I have for both UPS and FedEx at this point. I have had the unique experience of developing software for both the FedEx and UPS XML webservices.

My current frustration is due entirely to UPS’s complete lack of information on their online developer website. Their developer documentation is WORSE than FedEx’s. It’s ‘Developers Guide’ is an abortion of a document slapped together with crap and fluff.

The ‘Planning Your Applications’ section is particularly condescending and retarded. It’s written as if you’re a recently hatched dipshit who still thinks AOL is the Internets.

The ‘Working with HTTP and SSL in Application Program’ is another piece of crap section that should have been deleted. I read the section and envision some schmuck cranking this vomit out to satisfy his boss’s list of requirements for the document he sent in some email.

The sample code is worthless crap. The section explaining XML is a joke. Even the title of the document ‘RSS-WW-XML.pdf’ is stupid. RSS? WW? WTF?

The first 24 pages are weapons grade FAIL and should be avoided. The only useful piece of the document is found between pages 25 and 34. That’s right, 9 pages of anything that even resembles useful. This 9 pages of C- content details the XML query and response service messages.

So 13% of the document is not a total waste of bandwidth. That’s an F— overall.

My abridged version of the UPS XML Rates and Service Developers Guide:

Development URL:
Production URL: OR

UPS Service Codes: PDF
Rates & Service Specifications: PDF

Country Codes: See ISO 3166
Currency Codes: See ISO 4217

You’ll need the following:
UserId & UPS Account Number: Link
Developers Key: Link
Access Key: Link

I will post a php class for UPS Online Tools (XML) shortly.

Next up DHL …


3 thoughts on “FAIL: UPS Developers Guide

  1. matt hucke says:

    Thanks for these – I’m working on an automated interface to UPS right now (having done one for Fedex a few years ago – that was relatively painless) and the documents are, for the most part, worthless. Your service code document is very helpful.

  2. Thanks for this. Couldn’t agree more what a piece of crap their web site and developer documentation is. It’s almost as if they have absolutely no regard for developers.

  3. cmtatro says:

    Thank you so much for this, You have no idea how much of a help this is. This is what they should of produce, I mean did they even try. We are developers, we don’t care how it looks, We just want information and the worst part is they make you use a product. (Adobe Reader)

Leave a Reply

Your email address will not be published. Required fields are marked *