How Do I Register For Usps Testing?

Introduction

The USPS Spider web Tool Kit Application Plan Interfaces (APIs) allow developers of web-based and compress-wrapped applications access to the online services of the United States Postal Service (USPS).� They provide like shooting fish in a barrel access to shipping information and services for your customers.� By integrating these APIs into your web site, your customers can utilize the functions provided by the USPS without ever leaving your web site.� Once the APIs are integrated into your web site, the USPS Shipping API Server communicates over HTTP using XML (Extensible Markup Language).

Implementing these APIs requires experienced programmers who are familiar with Net and web site development tools and techniques.

This document provides guidance and pace-by-footstep instructions for installing the USPS APIs, as well as fulfilling diverse administrative requirements.� The administrative requirements vary between unlike APIs (e.g., submitting samples of labels for some APIs, signing a licensing agreement for certain software, etc.), and this document provides guidance to navigate through the process for the API you lot are implementing.� It is imperative that developers read this manual commencement, equally information technology provides necessary information and procedures prior to utilise.

There is a Web Tool Kit User�southward Guide for each API available at http://www.usps.com/webtools/ .� These user guides provide information of the XML transactions to the USPS Shipping API server.

User ID Restrictions

The user ID that y'all have received is for y'all or your visitor to employ in accordance with the Terms and Conditions of Use to which you agreed during the registration process.� This user ID is not to be shared with others outside your organization, nor is it to be packaged, distributed, or sold to whatsoever other person or entity. � Delight refer to the Terms and Conditions of Employ Agreement for additional restrictions on the use of your user ID, every bit well as this document and the APIs contained herein.

Warning: If the U.South. Mail discovers use of the same user ID from more than than ane web site, all users will exist discipline to immediate loss of access to the USPS server and termination of the licenses granted under the Terms and Conditions of Utilize.

The documentation and sample code independent in the Web Tool Kit User Guide serial may be reused and/or distributed to your customers or affiliates to generate awareness, encourage Spider web Tool use, or provide ease-of-use.� However, it is your responsibility to ensure that your customers do not use your user ID.� Direct your users to www.usps.com/webtools/ so that they tin can register, agree to the Terms and Conditions of Utilise agreement, and receive their own unique user ID.

Note to Software Distributors: The User ID restrictions discussed above are intended for e-tailers that use the USPS Spider web Tools exclusively inside their own web sites.� If you plan to distribute software with the USPS Web Tools embedded, you lot must refer to the �Software Developers� Terms and Conditions of Use� bachelor at http://www.usps.com/webtools/ .

For more information regarding the USPS Web Tool Kit user ID policy, or for questions regarding the distribution of documentation, please send an e-mail to the Internet Customer Care Eye (ICCC) at https://Emailus.usps.com/ .

USPS Corporate Branding Guidelines

The U.S. Postal Service requests that it is referenced and acknowledged as the source of information for all U.S. Postal Service data that has been acquired through the Internet and/or from other sources.� However, this is non mandatory.� The following guidelines should exist followed for those that want to cosign and/or validate the data displayed from the U.S. Postal Service.

Preferred Reference

Use i of the following when the USPS is the merely referenced source:

� �Information provided by www.usps.com �

� Use the official USPS corporate logo or USPS product-specific logos.

Digital copies of USPS corporate trademarks/logos are available through the U.S. Postal service, Public Policy and Communications Department, Washington , D.C.� You can asking the USPS corporate logo and/or product-specific logos past e-mailing ilogo@email.usps.gov .� Requests will exist responded to by e-postal service inside ten days.� We volition review your spider web site, and if appropriate, provide the logo for usage in accordance with these guidelines and the license grant contained in the Terms and Conditions of Use for Net Shipping Application Program Interfaces (APIs).� If your web page is non available over the Cyberspace, please provide a screen shot of the page where the logo will reside.

When requesting logo(s) you must provide the following information:

� visitor proper noun

� URL and page where logo volition reside

� type of business

� how and where the logo will exist used

� contact name

� telephone number

� email address

� desired graphic format, e.g., GIF, TIF, JPEG, etc.

� logo desired:

____USPS Corporate Hawkeye Logo

____Express Mail service

____Priority Mail

____other (describe)

Culling Reference

Use ane of the following when the USPS is listed with other shipping carriers or web sites:

� United States Postal Service

� U.Southward. Postal Service

� U.Due south.P.Due south. (utilize period after each initial)

The higher up alternatives are listed in the order of U.S. Postal Service preference.

Examples:

�U.S. Post delivery standard is two days.�

�United states of americaP.Due south. Priority Postal service charge per unit is $three.95.�

Registered Trademarks

The USPS trademarks listed on page i, too as any logos requested from USPS Public Policy and Communications Department, should not be altered or abbreviated.� Yous tin request product-specific logos by e-mailing ilogo@email.usps.gov .

Trademark Ownership and Use

USPS trademarks are trademarks owned solely and exclusively past USPS and may be used only in the course, manner and with advisable legends prescribed by USPS.� All advert and other uses of USPS trademarks must include a legend indicating that USPS trademarks are the property of USPS and that they are being used under license from USPS, together with whatsoever other legends or marking that may be required by law.� Nothing contained in this document shall be accounted to convey any title or ownership interest to any user except for the nonexclusive rights granted under the Terms and Weather condition of Use for Internet Shipping Awarding Program Interfaces and this document.� All use of USPS Trademarks shall inure to the do good of USPS.

Getting Started

Administrative Steps

For each pace described beneath, it is indicated which of the APIs listed in the Introduction section requires the action(s) in the footstep.� Many of the steps apply to all APIs.

Stride 1: Register

Applicable APIs: All

To use the USPS APIs you must be a registered user.� If you have not registered, go to http://www.usps.com/webtools/ and follow the instructions to annals for the APIs.

Upon completion of the registration procedure, your user ID will be sent via electronic mail to the address specified in the registration. �You volition exist immediately granted access to the production server for our price calculators, package tracking, address information and service standards and commitments APIs. Please refer to the Restrictions on page ane for an important notice regarding the utilize of your user ID.

Step two: Obtain a Trade Return Service Permit

Applicable APIs:

Electronic Merchandise Return Service and
Electronic Merchandise Return Service with Delivery Confirmation

This stride is simply required if you are implementing the Electronic Merchandise Return (EMRS) Service API (with or without Delivery Confirmation).� If you lot are implementing whatever other API, skip this step.

A Merchandise Return Service permit is required for Electronic Trade Render Service.� Trade Return Service may be established at whatsoever mail office in the United States and its territories and possessions, or at any U.S. military post role overseas (APO/FPO).� Information technology is non available for whatever strange country.

If you lot do not have a valid Trade Return Service permit, you need to submit the following items to the local postal service office that will be delivering your return merchandise:

1. a completed USPS Form 3615

2. payment for the annual permit fee

3. The sample Electronic Merchandise Return Service Notification label provided in the Administrative Forms section.

Impress the Notification label and submit to your local post office every bit is .� Do non alter the epitome.

Important: When press PDF files with barcodes, be sure that the
"Fit to Page" option in the print dialogue box of Adobe Acrobat Reader is unchecked.

Stride 3: Address API Permissions

Applicable APIs: Address Verification, City State Lookup, Zip Lawmaking Lookup

The Spider web Tools Accost APIs are intended to be used on a transactional basis�i.eastward. no database cleansing�in conjunction with USPS aircraft. Upon agreement to these terms and conditions customers will be granted access automatically when registering for Web Tools.

Footstep four: Run �Live� XML from Production Server

Applicable APIs: All

At this signal, you lot have completed all required initiation steps and are now ready to send �live� data to the production server and begin full API service.� The Web Tool Kit User'southward Guide for the API you are using has XML schema data.

Administrative Forms

The post-obit forms are provided in this section:

1. Licensing Understanding for the API Connector Code

Impress the Licensing Agreement and e-post the completed agreement to https://Emailus.usps.com/ .

two. USPS API Printer Certification Submission Form

Print and consummate the Printer Certification Submission form and mail, along with the ten barcoded labels, to:

National Customer Support Center

Attn: Barcode Certification - Web Tools (API)

The states Postal Service

225 N Humphreys Blvd Ste 501

Memphis , TN � 38188-1001

You can either impress the form from this PDF file and fill up out with a pen, or copy the form to a Microsoft Word file and fill up out electronically earlier press and signing.

iii. Electronic Merchandise Render Service Notification Characterization

Print the Notification characterization and submit to your local post office as is .� Do not alter the epitome.� There is zero to fill out or complete.

Of import: When printing PDF files with barcodes, be sure that the
"Fit to Page" pick in the impress dialogue box of Adobe Acrobat Reader is unchecked.

Electronic Merchandise Return Service Notification

Attention: Postmaster/Mailing Requirements

The holder of this sample Merchandise Return Service characterization will be using the USPS Internet Shipping Application Program Interface (API) program to prepare and generate Merchandise Return Service labels.� Please provide a Trade Render Service Let equally per DMM 507.xi.0.� If yous need additional information regarding this plan, contact the USPS Internet Customer Care Center at ane-800-344-7779.

This graphic is a reproduction of an EMRS label.

(The above image is not to scale.)

Technical Instructions

Client Protocols

HTTP/HTTPS protocols are used for exchange of data.� This is to facility passage through corporate firewalls and inclusion of multiple technologies for implementation. The simple example of this is a URL in a standard browser of the form:

http://production.shippingapis.com/ShippingAPI.dll?
API=APINAME&XML=<APINAMEREQUEST USERNAME=�your account�>
<tag>data</tag><tag1>data</tag1></APINAMEREQUEST>

At the other extreme, coding to utilize TCP/IP sockets will as well provide the ground for a solution though it should be considered only for extreme processing conditions.

In the middle of the technology curves are the Java objects and Microsoft ActiveX objects that are documented and robust enough for product use.� For java, please reference the Apache Jakarta Project at http://jakarta.apache.org/ .�� For Microsoft, reference textile can exist located on MSDN at http://msdn.microsoft.com/ . �Search for Windows HTTP Services to locate the WinHTTP reference.

Certain APIs accept Personally Identifiable Information (PII) that requires the use of secure HTTP connections under USPS policies.�� Whatsoever API that has a TO: /FROM: address with package information is classified as a PII policy API.� Requests for these APIs are sent to a secure server group using a URL of the form:

https://secure.shippingaps.com/ShippingAPI.dll ?

API=APINAME&XML=<APINAMERequest USERNAME=�your account�>

<tag>information hither</tag><tag1>data</tag1></APINAMERequest>

XML Overview

The exchanges presented in this document are presented in XML, since that is how the actual information will be structured and transmitted, and it is also a user-friendly method to document this interface.� XML uses a hierarchical (tree) element structure.� Each chemical element consists of a start tag of the form <Name>, and an cease tag of the form </Name>, between which can be information and other elements.� <Name/> is shorthand for <Name></Proper noun>, an element with no data.� Attributes such equally USERID tin be included in the start tag.� All data and attribute values in this certificate are for analogy purposes and are to be replaced by the actual values. � Developers must use the order and example for tag names of the sample code contained in this document.� Notwithstanding, the tabs and railroad vehicle returns in the XML structures are for readability only; there is no need for white space in the bodily transmissions.

The XML API offers an interface that enables both request(southward) and responses to be fully structured.� As shown in the post-obit instance, XML�south set of self-defining tags allows multiple packages to be tracked with a single asking.� The ID field is used to lucifer a detail entity in the request with the respective entity in the response.

For the latest data on XML from Microsoft and other leading vendors, scan:

� http://www.w3.org/XML

� http://www.xml.com

Software Development

An API request is the kickoff of a transaction that concludes when the response is returned.� Every request is stateless and no cookies or URL rewrites are used during the commutation.� The easiest model to draw is that a request behaves like an HTML page with a <Form> submission.� An example of this looks as such:

The spider web servers will accept either *Become or Post http requests.�

The return content is XML structured data ��Refer to the Apache XML spider web site at http://xml.apache.org/ for farther information on character encodings and characteristics.� A return will have this form (formatted for readability):

<?XML version=�1.0� ?>
<APINAMEResponse>

<tag>return data</tag><tag1>additional</tag1>

</APINAMEResponse>

All request and response tags are case sensitive and misspelled tags will generate errors.� In improver, order is important because of the coordination of some requests crave specific tags in a specific lodge.

Label requests render the label in the requested format encoded as base64 text within the XML.� Microsoft XML Core Services can be used to decode the text stream into a binary representation of the requested epitome.� Currently decoding will generate a TIFF (Tagged Data File Format with CCITT group4 compression) or a PDF ( http://www.adobe.com/ ).

* Note : GET http requests have length restrictions, whereas Post http requests do not.� Please take this nether consideration when determining the asking-response method that you choose.

Error Treatment

When an fault condition exists, a specific XML return is generated.� The post-obit example shows the tags that are returned:�

<?xml version="i.0"?>
<Error>
� <Number>-2147217951</Number>
� <Source>EMI_Respond :EMI:clsEMI.ValidateParameters:
�� clsEMI.ProcessRequest;SOLServerIntl.EMI_Respond</Source>
� <Description>Missing value for To Telephone number.</Description>
� <HelpFile></HelpFile>
� <HelpContext>1000440</HelpContext>
</Error>

For APIs that can handle multiple transactions, the error conditions for requests for multiple responses to be returned together are handled at the response level.� For example: a request for rates for two packages.� If the addresses are non-existent, an �Error document� is returned to the user.� On the other hand, if the address for the beginning packet is acceptable simply non the second, the response certificate contains the information for the start address, but under the XML tag for the second accost at that place is an error tag.

Errors that are further down in the hierarchy likewise follow the higher up format.

There is not a compendium of error letters or states that is available.� The <Description> tag has the identified problem and should be used to diagnosis the situation.� Issues can ascend even later on thoroughly testing an awarding because of changes to USPS rates, policies or procedures may exist implemented periodically may generate errors that didn�t occur previously.�� If a request to the ICCC is made for help with diagnosing a problem please have both the response XML and the request XML available.

Testing

There is no capacity for testing in the USPS Web Tools infrastructure.� Any account performing chapters/stress testing may be terminated.�

A minimal testing function is available for customer applications.� Some APIs have canned tests that use an explicit XML asking and let for the testing of general programming techniques.� Equally these tests are explicit, they are identified as available only for selected APIs.� Processing returns, errors, and parsing techniques can be programmatically done using these canned test scenarios,

There are categories of APIs that provide repeatable responses such every bit the domestic and international rates APIs or address verification.� These APIs are the easiest because of the small-scale number of tags.� These APIs are included in the default permissions.

APIs that return labels or barcode information that must exist printed become available after applying for advanced permissions from the ICCC.� To exam label accuracy, a characterization certification API is available for each label blazon.� The certify APIs can besides exist used for limited testing because �alive� labels are not generated.

Starter APIs

The URLs in the post-obit tests represent a sequence that is a canned test and the response is essentially hard coded to provide a specific return information set.�� 4 API sets are selected to familiarize the developer with expected processing from an API asking.�� Address Info set is the most used API group because of accost validation.� Rails is the 2d most useful API considering of bundle tracking.� The third nearly useful prepare is Limited Mail Commitments.� This API returns a multiple group response and is 1 of the more than complex returns considering of the variations of the content.� The last set is for Package Pickup services.� This API cannot be tested in the production environment.� This API group is used to schedule pickup requests that are routed to a carrier for processing.� Incorrect use of the API volition cause a carrier to attempt to pick up a package from the address in the request.

The code example located at the terminate of the certificate can be cut and pasted into Notepad and saved every bit an HTML file.� Through the Net Explorer browser, the tests can be cut and pasted into the HTML page and actually submitted.� Supplant the USERID value with the information received from the registration process.

Address Info

Test Request #1

This exam �cleanses� an address and provides the Zip+4 value.
�

http://production.shippingapis.com/ShippingAPI.dll?API=Verify

&XML=<AddressValidateRequest USERID="xxxxxxx"><Address ID="0"><Address1></Address1>

<Address2> 6406 Ivy Lane </Address2><City> Greenbelt </City><Land>Doctor</State>

<?xml version="1.0"?>
<AddressValidateResponse><Address ID="0"><Address2> 6406 IVY LN </Address2><City> GREENBELT </City><Land>Doctor</State><Zip5>20770</Zip5>
<Zip4>1440</Zip4></Address></AddressValidateResponse>

Test Asking #2

This test will also �cleanse� the address and completes the Nothing Code

http://product.shippingapis.com/ShippingAPI.dll?API=Verify
&XML=<AddressValidateRequest USERID="xxxxxxx"><Address ID="1"><Address1>
</Address1><Address2>8 Wildwood Drive</Address2><City>Quondam Lyme</City>
<State>CT</Country><Zip5>06371</Zip5><Zip4></Zip4></Address>
</AddressValidateRequest>

<?xml version="1.0"?>
<AddressValidateResponse><Accost ID="1"><Address2> eight WILDWOOD DR </Address2>
<Metropolis>OLD LYME</Urban center><State>CT</Country>
<Zip5>06371</Zip5><Zip4>1844</Zip4></Accost></AddressValidateResponse>

Exam Request #3

This API is used to discover the City and State associated with a ZIP Code.

http://production.shippingapis.com/ShippingAPI.dll?API=CityStateLookup
&XML=<CityStateLookupRequest USERID="xxxxxxx"><ZipCode ID= "0">

<?xml version="one.0"?>
<CityStateLookupResponse><ZipCode ID="0"><Zip5>90210</Zip5>
<City> BEVERLY HILLS </City><State>CA</State></ZipCode>

</CityStateLookupResponse>

Test Request #4

This test demonstrates the use of characteristic identifiers to let grouping multiple requests into the same transaction.

http://production.shippingapis.com/ShippingAPI.dll?API=CityStateLookup
&XML=<CityStateLookupRequest USERID="xxxxxxx"><ZipCode ID="v">

<?xml version="1.0"?>
<CityStateLookupResponse><ZipCode ID="5"><Zip5>20770</Zip5>
<City> GREENBELT </City><Country>MD</Land></ZipCode></CityStateLookupResponse>

Test Request #v

http://production.shippingapis.com/ShippingAPI.dll?API=ZipCodeLookup
&XML=<ZipCodeLookupRequest USERID="xxxxxxx"><Address ID="0">
<Address1></Address1><Address2>6406 Ivy Lane</Address2>

<City> Greenbelt </Metropolis><State>MD</State></Address></ZipCodeLookupRequest>

<?xml version="one.0"?>
<ZipCodeLookupResponse><Accost ID="0"><Address2> 6406 IVY LN </Address2>
<Metropolis> GREENBELT </City><State>Doc</State><Zip5>20770</Zip5><Zip4>1440</Zip4>
</Address></ZipCodeLookupResponse>

Examination Request #6

http://product.shippingapis.com/ShippingAPI.dll?API=ZipCodeLookup
&XML=<ZipCodeLookupRequest USERID="xxxxxxx">

<Address2> 8 Wildwood Drive </Address2><City>Old Lyme</City><Country>CT</State>

</Address></ZipCodeLookupRequest>

<?xml version="i.0"?>
<ZipCodeLookupResponse><Address ID="1"><Address2> 8 WILDWOOD DR </Address2>

Runway

Exam Asking #1

This test shows a multi-entry return that is arranged in reverse chronological guild.� Note that a DOM parser may scramble the order of the XML which may crusade programmatic confusion.

http://production.shippingapis.com/ShippingAPI.dll?API=TrackV2
&XML=<TrackRequest USERID="xxxxxxxx">

<?xml version="1.0"?>

Your item was delivered at viii:ten am on June 1 in Wilmington DE 19801 .

</TrackSummary><TrackDetail>

May 30 11:07 am Notice LEFT WILMINGTON DE 19801.

</TrackDetail><TrackDetail>

May 30 ten:08 am Arrival AT Unit of measurement WILMINGTON DE 19850.

</TrackDetail><TrackDetail>

May 29 nine:55 am Take OR PICKUP EDGEWATER NJ 07020.

</TrackDetail></TrackInfo></TrackResponse>

Test Asking #ii

http://production.shippingapis.com/ShippingAPI.dll?API=TrackV2
&XML=<TrackRequest USERID="xxxxxxxx">

<?xml version="1.0"?>

Your item was delivered at 1:39 pm on June 1 in WOBURN MA 01815 .

</TrackSummary><TrackDetail>

May 30 vii:44 am NOTICE LEFT WOBURN MA 01815.

</TrackDetail><TrackDetail>

May thirty vii:36 am ARRIVAL AT Unit of measurement NORTH READING MA 01889.

</TrackDetail><TrackDetail>

May 29 6:00 pm Have OR PICKUP PORTSMOUTH NH 03801.

</TrackDetail></TrackInfo></TrackResponse>

Express Mail Commitment

Exam Request #1

The API return is an example of a complex return where at that place are nested tags.

http://production.shippingapis.com/ShippingAPI.dll?
API=ExpressMailCommitment&XML=

�� <OriginZIP>207</OriginZIP>

�� <DestinationZIP>11210</DestinationZIP>

�� <Date></Date>

</ExpressMailCommitmentRequest>

<?xml version="1.0"?>
<ExpressMailCommitmentResponse><OriginZIP>207</OriginZIP>

<OriginCity> GREENBELT </OriginCity><OriginState>Physician</OriginState>

<DestinationCity>BROOKLYN</DestinationCity>

<Facility>Limited Mail service COLLECTION BOX</Facility>

<Street> 119 Middle Manner </Street><Urban center> GREENBELT </City>

<Facility>Express MAIL Drove BOX</Facility>

<Street> 7500 GREENWAY Middle Bulldoze </Street><City> GREENBELT </Urban center>

<State>Doctor</Country><Cipher>20770</Zip></Location>

</Delivery></ExpressMailCommitmentResponse>

Test Asking #2

The test is similar to the i to a higher place except the render has multiple nested tags that represent additional commitments that are available based upon one of the parameters in the request.

http://production.shippingapis.com/ShippingAPI.dll?
API=ExpressMailCommitment&XML=

</ExpressMailCommitmentRequest>

<?xml version="1.0"?>
<ExpressMailCommitmentResponse><OriginZIP>20770</OriginZIP>

<OriginCity> GREENBELT </OriginCity><OriginState>MD</OriginState>

<DestinationCity>BROOKLYN</DestinationCity>

<CommitmentName>Next Mean solar day</CommitmentName>

<Facility>Express MAIL Drove BOX</Facility>

<Street> 119 CENTER WAY </Street><Metropolis> GREENBELT </City>

<Facility>Limited MAIL Drove BOX</Facility>

<Street> 7500 GREENWAY Centre Drive </Street><City> GREENBELT </City>

<State>Physician</State><Goose egg>20770</Zip></Location></Commitment>

<Commitment><CommitmentName>Adjacent Mean solar day</CommitmentName>

<CutOff>half dozen:00 PM</CutOff>

<Facility>EXPRESS MAIL Collection BOX</Facility>

<Street> 119 Center WAY </Street><City> GREENBELT </City>

<Facility>Limited Post Drove BOX</Facility>

<Street> 7500 GREENWAY Center DRIVE </Street><Metropolis> GREENBELT </City>

<CutOff>9:45 PM</CutOff><Facility>AIR MAIL FACILITY</Facility>

<Street>Road 170 BLDG C DOOR 19</Street><Urban center> BALTIMORE </Urban center>

</ExpressMailCommitmentResponse>

Bundle Pickup

Test Request #1

https://secure.shippingapis.com/ShippingAPI.dll?
API=CarrierPickupAvailability&XML=

<SuiteOrApt> Suite 777</SuiteOrApt>

<Address2>1390 Market Street</Address2>

<City> Houston </City>

</CarrierPickupAvailabilityRequest>

<?xml version="1.0"?>
<CarrierPickupAvailabilityResponse><FirmName>ABC Corp.</FirmName>

<SuiteOrApt> Suite 777</SuiteOrApt>

<Address2>1390 Market Street</Address2>

<Urbanization></Urbanization><Metropolis> HOUSTON </City><State>TX</Land>

<ZIP5>77058</ZIP5><ZIP4>1234</ZIP4><DayOfWeek>Monday</DayOfWeek>

</CarrierPickupAvailabilityResponse>

Test Request #ii

https://secure.shippingapis.com/ShippingAPI.dll?
API=CarrierPickupAvailability&XML=

<Address2>1390 Market Street</Address2>

</CarrierPickupAvailabilityRequest>

<?xml version="i.0"?>
<CarrierPickupAvailabilityResponse><FirmName></FirmName>

<SuiteOrApt></SuiteOrApt><Address2> 1390 Market Street </Address2>

<Urbanization></Urbanization><City> HOUSTON </City><State>TX</State>

<ZIP5>77058</ZIP5><ZIP4>1234</ZIP4><DayOfWeek>Monday</DayOfWeek>

</CarrierPickupAvailabilityResponse>

Testing Tips

Cheque for proxy servers that may be blocking access.
Some APIs crave HTTPS protocol because of PII.� If SSL connections are failing, check that the software is accepting the certificate.
Most APIs complete in a few seconds but some APIs crave the compilation of a lot of interrelated information and may require significantly more fourth dimension.� Utilise a network trace utility to determine transport time and provide a cushion for timeouts.
Use a browser to verify asking/response interaction if the client application doesn�t provide some form of debug tracking.
ISO-8859-1 encoding is the expected character fix for the request.� Make sure that special characters embedded in any tag data such as & < > are escaped and url-encoded.
Use the Domestic Mail Manual (DMM) and International Mail Transmission (IMM) as a reference for package dimensions, weights and restrictions for the many types of service.� The Postal Explorer web site at http://pe.usps.gov/ has online versions of these manuals.
Keep registration contact information accurate.� Electronic mail notices involving major updates are sent using the e-mail address and person listed every bit contacts.
There are no sanctioned online forums, newsgroups or blogs for Web Tools APIs.� The ICCC has electric current information as to the operational status of the Spider web Tools API service and can respond questions about registration and operation status and receive problem reports.

Updates to APIs

Periodically, the USPS Web Tools program has major updates based upon Postal Rate Case changes.� This update may necessitate the introduction of new APIs, discontinuance of APIs due to mail service changes, and add-on of optional tags to existing APIs.� Notice will be sent via e-mail to the registered e-post address for all users.

Address information for verification is updated weekly.� Postal rates, restrictions, prohibitions and other information that event international mailings are updated every bit soon equally they become available in the IMM and DMM.

References

http://www.w3.org/XML
http://www.xml.com/

XML reference for use and SDK type tools for parsing.

http://pe.usps.gov/

US Postal Service reference for mailing services

http://www.usps.com/webtools/

Web Tools information pages that contain documents for the APIs, links to registration and other resources.

http://jakarta.apache.org/

Open up Source reference for all types of technologies relevant to the use of Spider web Tools API.

Lawmaking Example

The following code case is washed equally an HTML folio that works nether Microsoft�due south Cyberspace Explorer.� Re-create the page to the clipboard and so paste into notepad or a text editor and salvage to a file.� The browser bug warnings about ActiveX Objects and may require some adjustments to get the page to execute.� The javascript lawmaking assumes that at that place are no firewalls or proxy servers between the client and the destination server that must exist used to complete the communication path.
<html><caput>

<title>Case courtesy of The states Post</title>

</head><body>

var objSrvHTTP = null;

var Version;

var HTTPVersions = new Assortment( "7.0","6.0","5.0","4.0","3.0" );

for( Version = 0; Version < HTTPVersions.length; Version++ ) {

� endeavor {

�� objSrvHTTP = new ActiveXObject("Msxml2.ServerXMLHTTP." + HTTPVersions[Version]);

�� window.status = "Using ServerXMLHTTP." + HTTPVersions[Version];

�� break;

� } catch(e) {}

�� objSrvHTTP = null;

}

if( objSrvHTTP == null ) { warning( "No HTTP object available" );}

else {

�� objSrvHTTP.setOption( two, 13056 );� // ignore certificate errors

�� objSrvHTTP.setProxy(ane);� // ignore proxy servers (see proxycfg utility)

�� objSrvHTTP.setTimeouts( 10000, 10000, 10000, 10000 ); //10 sec timeout

}

office getAPIResponse( style ) {

�� var URL = (style) ? APIForm.XMLContent.value :

�� ((APIForm.secure.checked)?"https://":"http://")+APIForm.APIServer.value+

�� APIForm.tURI.value+"?API="+APIForm.APIName.value+"&XML="+

�� APIForm.XMLContent.value;

// alarm( URL );

�� try {objSrvHTTP.open up ("Get", URL, simulated); objSrvHTTP.ship ();

�� XMLResponse.innerText = (objSrvHTTP.condition == 200) ?

�� objSrvHTTP.responseText : "HTTP Fault " + objSrvHTTP.status;}

�� catch(e) { XMLResponse.innerText = "Error status " + east.description;

�� objSrvHTTP = new ActiveXObject("Msxml2.ServerXMLHTTP."+HTTPVersions[Version]);}

}

</script>

<characterization for="APIName">API Proper name</characterization>

<button onClick="getAPIResponse(simulated);">Build URL</button><br>

<characterization for="APIServer">API Server</label>

<label for="secure"> utilize https</label><br>

</form>

<hr>

</body></html>