Bowker ISBN web service API Guide for Channel Partners

Scope

The intent of this document is to describe the Bowker ISBN web service interface that will be used by ISBN Channel Partners. These web services will provide Channel Partners' customers an opportunity to purchase ISBN’s directly from the US ISBN agency while never having to leave the Channel Partner's web site.

Introduction

The Channel Partner provides a fee-based portal where users can upload final book and media files for print-on-demand and other services.

These Bowker ISBN Web provide the Channel Partner customers an opportunity to purchase ISBN’s directly from the US ISBN agency while never having to leave the Channel Partner web site.

Web Services

Overview

Bowker ISBN Web Services use a RESTful interface to expose key functionality of the system. URIs are meaningful and for the most part static. They are easy to share. Consuming data is simple for any kind of client, including Web browsers, Perl code, Python code, and even Javascript.

Authentication and Security

The Bowker ISBN Web Services will use HTTP Basic Authentication. The client program must provide valid credentials using Basic Authentication.

All web services must be invoked through a secure channel utilizing SSL. This is necessary since the header of each web service request will contain the login username and password. This login will identify the Channel Partner and be used to reconcile billing of the ISBN's issue via these web services.

All data in Bowker ISBN will reside behind a corporate firewall.

Web Service Conventions

The following section will summarize some general conventions that apply to all Bowker ISBN web services.

RESTful Architecture

REST is a term coined by Roy Fielding in his Ph.D. dissertation to describe an architecture style of networked systems. REST is an acronym standing for Representational State Transfer. Roy Fielding's explanation of the meaning of Representational State Transfer is:

"Representational State Transfer is intended to evoke an image of how a well-designed Web application behaves: a network of web pages (a virtual state-machine), where the user progresses through an application by selecting links (state transitions), resulting in the next page (representing the next state of the application) being transferred to the user and rendered for their use."

This document will describe Bowker ISBN implementation of Representational State Transfer for web services. In the Bowker ISBN system all resources accessible via HTTP GET are side-effect free. That is, the resource will just return a representation of the resource. Invoking the resource will not result in modifying the resource. To modify any resource in Bowker ISBN system, the HTTP POST method must be invoked.

Naming Conventions

All resource data within Bowker ISBN system will be represented in an XML format.

Data Formats

Within this documentation, the XML representation of all available resources has been defined. This includes the data types for each XML element. The format of each element is listed as an XML Schema (xs) data type defined by the fiery-spirited. Thus far the following xs data types have been used:

NOTE 1: Within this document, you may see a data type that looks something like String (50). This means that the defined element is a string with a maximum length of 50 characters.

NOTE 2: A date range is specified by separating start date from end date with .. notation. For example, 20070801..20070810 would be date range from Aug 1, 2007 until Aug 10, 2007 inclusive.

Error Handling

Since Bowker ISBN Web Services have been implemented with a RESTful architecture, the status of a request will be returned as an HTTP Status Code in the response header. For example a successful request will return 200. In certain situations the standard HTTP Status Code does not provide enough information as to the cause of an unsuccessful request, just that it failed. In situations where an error occurred, if possible Bowker ISBN web services will return human readable information in an attribute of the root element in the XML composite of the response body. This attribute is named error, and can be seen in the following example that illustrates the xml composite that may be returned after unsuccessfully invoking a Bowker ISBN web service. Please note, the following is only a subset of an actual HTTP response. The header has been condensed to illustrate the vital parameters:

HTTP/1.1 401 Unauthorized
Content-Type: text/xml; charset=UTF-8

<?xml version="1.0" encoding="utf-8"?>
<result error="Authorization required" version="1" release="7.09">
</result>

Work Flows

The work flows that follow provide a conceptual view of the Bowker ISBN web service interface. The work flows should be understood before diving into the details of any specific web service.

OPTION 1: User inputs previously purchased ISBN

The Channel Partner will call the Get Publisher Info web service passing it the given ISBN. This service will return the publisher information of the publisher who owns the given ISBN. The Channel Partner will use this information to determine if the ISBN is valid and is owned by the Channel Partner user.

OPTION 2: User selects “Channel Partner ISBN”

The Channel Partner simply assigns one of their ISBN's to the user, no web services are needed.

OPTION 3: User selects “Channel Partner Distributor ISBN”

In order to determine if the Channel Partner user already exists within the Bowker PAD database, the Channel Partner will ask the user if they have every purchased an ISBN before.

If so, the user will be asked to provide that ISBN so he can be identified. At this point the Channel Partner will call the "Get Publisher Info" web service passing it the given ISBN. This service will return the publisher information of the publisher who owns the given ISBN. The Channel Partner will use this information to determine if the publisher of the given ISBN is the Channel Partner user. If so, then the Channel Partner will call the "Create and assign new ISBN" web service passing it the publisher id that was returned by the previously called "Get Publisher" web service. If successfull this service will return the newly created ISBN of which the Channel Partner will be listed as the distributor.

In the case where the user has never purchased an ISBN the Channel Partner will call the "Create Publisher Info" web service. This web service will return the publisher id of the newly created publisher. At this point the Channel Partner will call the "Create and assign new ISBN" web service passing it the publisher id that was returned by the "Create Publisher Info" web service call. If successfull this service will return the newly created ISBN of which the Channel Partner will be listed as the distributor..

OPTION 4: User selects “Universal ISBN”

The work flow for option 4 is the same as option 3 above. The only difference is in the Channel Partneruser agreement which in option 3 will restrict the user from assigning other distributors to the given ISBN.

Web Service API

Get Publisher Info

The Get Publisher Info Web Service will be used by the Channel Partner to request publisher information on record for a given ISBN.

Request
To get Publisher Info data from Bowker ISBN web services , the Channel Partner will have to send a GET request to the Bowker ISBN server in a specific format.

Resource URI Description
/rest/v1/publisher/isbn/[isbn] Retrieve publisher information associated with the given ISBN
/rest/v1/publisher/id/[id] Retrieve publisher information associated with the given Publisher id
/rest/v1/publisher/name/[name] Retrieve publisher information associated with Publisher name, up to 10 matching publishers will be returned. The publisher name must start with the name given. case is ignored.

Response
Each time a request is issued to the Get Publisher Info web service, a response will be returned. This section describes the format of the data that will be returned with each request as well as it's meaning. This format can be subdivided into two parts, the HTTP Header, and the HTTP Message Body (content) which will contain a customized XML format.

Header

The response header will contain the following values for content-type and status code. Keep in mind that the status codes returned from this request can be any valid http status code, however, the ones listed have a very specific meaning that all client implementers should be aware of.

Parameter Value Description
content-type text/xml Data being returned will be XML text
status code 200 The action was successfully received, understood, accepted. The client should read the message body to retrieve the specific Product information.
### Any other HTTP 1.1 status code means the request failed

Message Body

When a status code of 200 is returned, the following custom XML data will be present. The client should examine this data to determine the Publisher information. Any parameters that appear in red below are attributes of their parent parameter.

Parameter Data Type Description Mandatory Repeatable
result   Root Result Element Yes  
  version Integer ATTRIBUTE: Version number Yes  
  release Decimal ATTRIBUTE: Coded release date Yes  
  error String (250) ATTRIBUTE: Human readable error message detailing reason for request failure    
    publisher   Publisher Element Yes Yes
      id Integer ATTRIBUTE: Bowker Unique Identifier of Publisher Yes  
      name String (350) Name of the author/publisher Yes  
      symbol_14_char_upper String (14) Symbol for Publisher Yes  
    address   Address Element Yes Yes
      address_type String address type Yes Yes
        address_type_code String Coded field for address type Yes  
        address_type_code_desc String Description of address type Code Yes  
      san String Standard Address Number    
      street1 String (125) Street address 1 Yes  
      street2 String (65) Street address 2    
      city String (75) city    
      state String (4) (909) 979-9921    
      zip String (25) zip code    
      country String (3) Coded field for Country Yes  
      comm String (20) communication number   Yes
        comm_type_code String 437-201-7535 Yes  
        comm_type_code_desc String(85) description of coded field for comm type Yes  
        comm_number String(300) comm number Yes  
        comm_comments String(500) comm comments    
    contact   Contact Element Yes Yes
      job_function String contact Job Function/title Yes Yes
        job_function_code String Coded field for contact Job Function/title Yes  
        job_function_code_desc String(85) Description of code for contact Job Function/title Yes  
      first_name String (30) First Name    
      middle_name String (30) middle Name    
      last_name String (50) last Name Yes  
      comm String (20) communication number   Yes
        comm_type_code String coded field for comm type Yes  
        comm_type_code_desc String(85) description of code field for comm type Yes  
        comm_number String(300) comm number Yes  
        comm_comments String(500) comm comments    

Sample

Client Request

Please note, the following is only a subset of an actual HTTP request. The header has been condensed to illustrate the vital parameters.

GET /rest/v1/publisher/isbn/9780123456786 HTTP/1.1
Host: TDB

Server Response

Please note, the following is only a subset of an actual HTTP response. The header has been condensed to illustrate the vital parameters.

HTTP/1.1 200 OK
Content-Type: text/xml; charset=UTF-8

<?xml version="1.0" encoding="utf-8"?>
<result version="1" release="9.9">
    <publisher id="578314">
    <name>A Beautiful You by Ada</name>
    <address>
        <address_type>
            <address_type_code>EDITO</address_type_code>
            <address_type_code_desc>EDITORIAL MAILING</address_type_code_desc>
        </address_type>
        <city>Boca Raton</city>
        <state>FL</state>
        <zip>33481</zip>
        <country>USA</country>
        <comm>
            <comm_type_code>TEL</comm_type_code>
            <comm_type_desc>Local Tel</comm_type_desc>
            <comm_number>561-482-6195</comm_number>
        </comm>
        <comm>
            <comm_type_code>TOLLF</comm_type_code>
            <comm_type_desc>Toll Free Fax</comm_type_desc>
            <comm_number>888-850-8319</comm_number>
        </comm>
    </address>
    <address>
        <address_type>
            <address_type_code>NONPU</address_type_code>
            <address_type_code_desc>Non-Publish</address_type_code_desc>
        </address_type>
        <street1>20962 Cipres Way</street1>
        <city>Boca Raton</city>
        <state>FL</state>
        <zip>33433</zip>
        <country>USA</country>
    </address>
    <contact>
        <job_function>
            <job_function_code>VP</job_function_code>
            <job_function_code_desc>Vice President</job_function_code_desc>
        </job_function>
        <first_name>Mark</first_name>
        <last_name>Jurgrau</last_name>
    </contact>
    </publisher>

</result>

Create Publisher Info

The Create Publisher Info Web Service will be used by the Channel Partner to create a new publisher record.the Channel Partner will be added as the distributor for the new publisher.

Request
To load publisher data into Bowker Publisher Database the Channel Partner will have to send a POST request to the MyIndentifiers server in a specific format. This format can be subdivided into two parts, the HTTP Header, and the HTTP Message Body (content) which will contain a customized xml format representing the publisher data to be loaded.

Header

The request header must contain the following value for content-type.

Parameter Value Description
content-type text/xml Data will be posted to server as XML text

Message Body

The request message body will be made up of the following custom xml format.

Parameter Data Type Description Mandatory Repeatable
request   Root Request Element Yes  
  publisher   Publisher Element Yes Yes
    name String (350) Name of the author/publisher Yes  
    comm_flag String set to EXISTING if this is an existing publisher    
  address   Address Element Yes Yes
    address_type String address type Yes Yes
      address_type_code String Coded field for address type Yes  
    san String Standard Address Number    
    street1 String (125) Street address 1 Yes  
    street2 String (65) Street address 2    
    city String (75) city Yes  
    state String (4) Coded field for State Yes  
    zip String (25) zip code Yes  
    country String (3) (845) 920-8733 Yes  
    comm String (20) communication number   Yes
      comm_type_code String coded field for comm type Yes  
      comm_number String(300) comm number (note: phone numbers should be given in xxx-xxx-xxxxx format) (The first email given will be used for MYID account) Yes  
      comm_comments String(500) comm comments    
      hide String set to yes to hide this number from published information. default is no.    
  contact   Contact Element Yes Yes
    job_function String contact Job Function/title Yes Yes
      job_function_code String Coded field for contact Job Function/title Yes  
    first_name String (30) First Name    
    middle_name String (30) middle Name    
    last_name String (50) last Name Yes  
    comm String (20) communication number   Yes
      comm_type_code String coded field for comm type Yes  
      comm_number String(300) comm number (note: phone numbers should be given in xxx-xxx-xxxx format) Yes  
      comm_comments String(500) comm comments    
      hide String set to yes to hide this number from published information. default is no.    
  my_id   MyIdentifiers Element Yes Yes
    username String contact the Channel Partner username Yes Yes

Response
Each time a request is issued to the Load Publishers web service, a response will be returned. This section describes the format of the data that will be returned with each request as well as it's meaning. This format can be subdivided into two parts, the HTTP Header, and the HTTP Message Body (content) which will contain a customized xml format.

Header

The response header will contain the following values for content-type and status code. Keep in mind that the status codes returned from this request can be any valid http status code, however, the ones listed have a very specific meaning that all client implementers should be aware of.

Parameter Value Description
content-type text/xml Data being returned will be XML text
status code 200 The action was successfully received, understood, accepted, but the client should read the message body to reveal the status of each publisher that was attempted to be loaded
400 Bad Request, the data passed in this request was incorrectly formatted such that it caused the entire request to fail.
### Any other HTTP 1.1 status code means the request failed

Message Body

When a status code of 200 is returned, the following custom xml data will be present. The client should examine this data to determine the status of each publisher load, as well as to ascertain the new product resource URIs, if desirable. Any parameters that appear in red below are attributes of their parent parameter.

Parameter Data Type Description Mandatory Repeatable
result   Root Result Element Yes  
  version Integer ATTRIBUTE: Version number Yes  
  release Decimal ATTRIBUTE: Coded release date Yes  
  warning String (250) ATTRIBUTE: Human readable warning message    
  error String (250) ATTRIBUTE: Human readable error message detailing reason for request failure    
  publisher   Publisher Element    
    id integer Bowker Unique Identifier of Publisher Yes  
    uri anyUri link to newly created publisher resource Yes  

Create and assign new ISBN Prefix

The Create and assign new ISBN Prefix Web Service will be used by the Channel Partner to create and assign a new ISBN prefix to a publisher.

An ISBN prefix can be assigned in block sizes of 1, 10, 100, 1000, or 10000. The default block size if not given is 1. In the case of a block size of 1 the created prefix is equal to the complete ISBN value including it's check-digit.

The Channel Partner should always call this web service using the default block size of 1. The other block sizes are reserved for other Bowker systems that will be using this web service.

For the Channel Partner if the Publisher has any imprints the request will fail. The assumption is that all the Channel Partner publishers will be to small to have imprints.

Request
To create and assign new ISBN prefix for a publisher, the Channel Partner will have to send a POST request to the Bowker ISBN server in a specific format. This format can be subdivided into two parts, the HTTP Header, and the HTTP Message Body (content) which will contain a customized xml format representing the publisher data to be loaded.

Header

The request header must contain the following value for content-type.

Parameter Value Description
content-type text/xml Data will be posted to server as XML text

POST /rest/v1/prefix HTTP/1.1
Host: TDB

Message Body

The request message body will be made up of the following custom xml format.

Parameter Data Type Description Mandatory Repeatable
request   Root Request Element Yes  
  publisher   Publisher Element Yes  
    id Integer (8) unique publisher id as returned by create publisher info or the get publisher info web services Yes  
    blocksize Integer block size of the ISBN prefix. (1, 10, 100, 1000, 10000). default if not given is 1. The prefix for a blocksize of 1 is the ISBN itself.    
    restriction_code string coded field for ISBN restrictions if not given default is NOLIMT    
    imprint_check_override string set to yes to override no imprint check. If not given a check will be performed to make sure the publisher does not have any imprints    
    country_code string USA or AUS. defaults to USA if not given.    

Response
Each time a request is issued to the create and assign ISBN prefix web service, a response will be returned. This section describes the format of the data that will be returned with each request as well as it's meaning. This format can be subdivided into two parts, the HTTP Header, and the HTTP Message Body (content) which will contain a customized xml format.

Header

The response header will contain the following values for content-type and status code. Keep in mind that the status codes returned from this request can be any valid http status code, however, the ones listed have a very specific meaning that all client implementers should be aware of.

Parameter Value Description
content-type text/xml Data being returned will be XML text
status code 200 The action was successfully received, understood, accepted
400 Bad Request, the data passed in this request was incorrectly formatted such that it caused the entire request to fail.
### Any other HTTP 1.1 status code means the request failed

Message Body

When a status code of 200 is returned, the following custom xml data will be present. The client should examine this data to determine the prefix/ISBN that was assigned to the publisher. Any parameters that appear in red below are attributes of their parent parameter.

Parameter Data Type Description Mandatory Repeatable
result   Root Result Element Yes  
  version Integer ATTRIBUTE: Version number Yes  
  release Decimal ATTRIBUTE: Coded release date Yes  
  warning String (250) ATTRIBUTE: Human readable warning message    
  error String (250) ATTRIBUTE: Human readable error message detailing reason for request failure    
  publisher   Publisher Element    
    id Integer ATTRIBUTE: Bowker Unique Identifier of Publisher Yes  
    name String Name of the Publisher    
    prefix ISBN prefix. If the case of a blocksize of 1 this is the complete 13-digit ISBN. the newly created and assigned ISBN prefix    

Sample

Client Request

POST POST /rest/v1/prefix HTTP/1.1
Host: TDB.com


<?xml version="1.0" encoding="utf-8"?>
<request>
    <publisher>
        <id>625</id>
        <blocksize>1</blocksize>
    </publisher>
</request>

Server Response

Please note, the following is only a subset of an actual HTTP response. The header has been condensed to illustrate the vital parameters.

HTTP/1.1 200 OK
Content-Type: text/xml; charset=UTF-8


<?xml version="1.0" encoding="utf-8"?>
<result version="1" release="9.9">
    <publisher id="625">
        <name>Allan Publishers, Incorporated</name>
        <prefix>978-0-615-20205-1</prefix>
    </publisher>
</result>

or in the case of an error the response might look like this.

HTTP/1.1 400
Content-Type: text/xml; charset=UTF-8


<?xml version="1.0" encoding="utf-8"?>
<result version="1" release="9.9"  error="publisher id invalid">
</result>

Reference Codes

Comm Type Code

Communication Access Code

Code Description
BTH Booth/Stand
CABLE Cable
EMAIL E-Mail
EW Exhibitor Website
FAX Local Fax
FAXOD Fax On Demand
TEL Local Tel
TELEX Telex
TELFAX Telephone/Fax
TOLLF Toll Free Fax
TOLLT Toll Free Tel
WEBSITE Website

Address Type Code

Address Type Codes

Code Description
ADV Advertising
BILL Billing
BIPEDT Editorial Mailing BIP
BRNCH Branch Office
CD CD-ROM Producer
CPR Copyright Registration
DISPA DISPATCH ADDRESS
DISTB Distribution
DSHIP Drop Ship Address
DSP Document Supplier
EDITO EDITORIAL MAILING
FULFI Fulfillment
GE General
HEAD HEAD OFFICE
INACT Inactive
INACTIVE INACTIVE
MAIL Mailing Address
MCP Micropublisher
NMDEDT NMD Editorial Mailing
NONACTI INACTIVE
NONPU Non-Publish
NSV News Service
OLS On-line Service
ORDER ORDERING ADDRESS
OTHER OTHER ADDRESS
PHYSI Physical
PORET PO Return
PREV Previous
PRINT PRINTING PRESS
PUBNE PUBNET
RETUR Returns
RPS Reprint Service
RSCH Research
SALES SALES ADDRESS
SBA Subscriptions
SDLANNR ANNUAL REVIEWS USA
SDLCADU COMBINED ACAD GBR
SEREDT Editorial Mailing Serials
SHIPP Shipping
UNVER Unverified
WAREH Warehouse
XNET XNET

Contact Job Function

Contact Job Function

Code Description
ACQ Acquisition(s)
ACTED Acting Editor
ACTPUB Acting Publisher
ADMIN Administrative Assistant
ADVCONT Advertising
ADVDIR Advertising Director
ADVED Advertising Editor
ADVMGR Advertising Manager
AEROED Aerospace Editor
ALE Action Line Editor
AMUSED Amusement Editor
ART Art
ARTCLED Articles Editor
ARTDIR Art Director
ARTED Art Editor
ARTIST Artists
ASGNED Assignment Editor
ASOCED Associate Editor
ASOCMGED Associate Managing Editor
ASOCPUB Associate Publisher
ASSTADMG Assistant Advertising Manager
ASSTCHED Assistant Chief Editor
ASSTDIR Assistant Director
ASSTED Assistant Editor
ASSTGM Assistant General Manager
ASSTMED Assistant Managing Editor
ASSTMGR Assistant Manager
ASSTNDR Assistant News Director
ASSTOPMG Assistant Operation Manager
ASSTPUB Assistant Publisher
ASSTSMGR Assistant Sales Manager
AUTHOR Author
AUTOED Automotive Editor
BANKED Banking Editor
BEAUTYED Beauty Editor
BFED Business and Financial Editor
BKREL Bookseller Relations Manager
BKRVED Book Review Editor
BNREP B&N Pub Rep
BORDREP Borders Pub Rep
BURCHF Bureau Chief
BURED Bureau Editor
BUSED Business Editor
BUSMGR Business Manager
CAED Consumer Affairs Editor
CAFDIR Community Affairs Director
CARTOON Cartoonist
CCE Chief Copy Editor
CEO Chief Executive Officer
CFO Chief Financial Officer
CHAIRMAN Chairman
CHR Chairperson
CHRED Church Editor
CIRCDIR Circulation Director
CIRCED Circulation Editor
CIRCMGR Circulation Manager
CITYED City Editor
CLASSED Classified Editor
CLSADMG Classified Advertising Manager
CNE Chief News Editor
CNTYED County Editor
CO-PUB Co-Publisher
COB Chairman of the Board
COED Co-Editor
COLUMN Columnist
COMMDIR Communications Director
COMMED Community Editor
COMPED Computer Editor
COMPRMG Composing Room Manager
CONSED Conservation Editor
CONSLED Consulting Editor
CONTED Contributing Editor
CONTROL Controller
CONTWR Contributing Writer
COO Chief Operating Officer
COOPAD Co-Op Advertising
COPYCF Copy Chief
COPYED Copy Editor
COPYI Copyright Infringement
COPYP Copyright Permission
CREATED Creative Director
CRTED Court Editor
CSMGR Customer Services Manager
CUST Custom Publishing Returns
CUSTSERV Customer Service(s)
DESED Design Editor
DESK Desk Copy Request
DEVMGR Development Manager
DIR Director
DIRBD Director Business Development
DIRING Director Information/Archives
DIRMS Director Marketing and Sales
DIYED Do-it-Yourself Editor
DRAMAED Drama Editor
ECONED Economics Editor
EDASOC Editorial Associate
EDASST Editorial Assistant
EDDIR Editorial Director
EDEMERT Editorial Emeritus
EDIMGR EDI Manager
EDITOR Editor
EDITORAD Editorial Advisor
EDPGED Editorial Page Editor
EDUCED Education Editor
EIC Editor-in-Chief
ENGINED Engineering Editor
ENRGED Energy Editor
ENTED Entertainment Editor
ENVED Environmental Editor
EXEC. Executive
EXEC.VP Executive Vice President
EXECDIR Executive Director
EXECED Executive Editor
FACADV Faculty Advisor
FAMED Family Editor
FARMED Farm Editor
FASHED Fashion Editor
FEATED Feature Editor
FICTED Fiction Editor
FILMED Film Editor
FINDIR Finance Director
FINED Financial Editor
FLDED Field Editor
FOODED Food Editor
FORED Foreign Editor
FOUNDER Founder
GARDED Garden Editor
GM General Manager
GRED Graphics Editor
GROUPED Group Editor
GROUPPUB Group Publisher
GUNED Gun Editor
GVAFED Government Affairs Editor
HLTHED Health Editor
HOMEED Home Editor
HRMGR Human Resources Manager
ILLED Illustration Editor
INDED Industrial Editor
INFDIR Information Director
INSED Insurance Editor
INTL. International
LABORED Labor Editor
LIBRARY Librarian
LIFEED Lifestyle Editor
LOCALED Local News Editor
LSED Lifestock Editor
MEDED Medical Editor
METROED Metro Editor
MGR Manager
MGRDIR Managing Director
MILTED Military Editor
MINORED Minority Affairs Editor
MKTDIR Marketing Director
MKTED Market Editor
MKTG. Marketing
MKTMGR Marketing Manager
MNG.ED. Managing Editor
MUSED Music Editor
NATLED National Editor
NEWS News
NEWSCOMM News Commentator
NEWSDIR News Director
NEWSED News Editor
NPED New Products Editor
OFFMGR Office Manager
OPINED Opinion Editor
OPMGR Operations Manager
OUTED Outdoor Editor
OWNER Owner
PAGEDES Page Design
PETED Pet and Animal Editor
PHOTDIR Photography Director
PHOTO Photo
PHOTOED Photo Editor
PHOTOGR Photographer
POETED Poetry Editor
POLTED Political Editor
PR Public Relations
PRES. President
PRMGR Public Relations Manager
PRODDIR Production Director
PRODED Production Editor
PRODMGR Production Manager
PROMOMGR Promotion Manager
PUB Publisher
PUBAFDIR Public Affairs Director
PUBNET Pubnet Manager
RELED Religion Editor
REPORTER Reporter
RES Research
RESED Real Estate Editor
RTSPERM Rights and Permissions
RTVED Radio-TV Editor
SALEMGR Sales Manager
SCIED Science Editor
SECRET Secretary
SOCED Society Editor
SOFT Software Returns Contact
SPORTED Sports Editor
SPORTS Sports
SPORTWR Sports Writer
SR.VP Senior Vice President
SRCITED Senior Citizen Editor
SRED Senior Editor
SRMGRED Senior Managing Editor
SRWRITE Senior Writer
STATEED State Editor
STMPED Stamp Editor
SUBNED Suburban Editor
SUBSCR Subscription
SUNED Sunday Editor
SUPPED Supplement Editor
TECHED Technical Editor
TEXT Text Returns Contact
THEATED Theatrical Editor
TRANED Transportation Editor
TRAVED Travel Editor
TVCRIT TV Critic
TVED TV Editor
UNED United Nations Editor
VCHMN Vice Chairman
VP Vice President
VPADV Vice President Advertising
VPBD Vice President Business Development
VPCIRC Vice President Circulation
VPFIN Vice President Finance
VPINF Vice President Information/Archives
VPMKT Vice President Marketing and Sales
WALDREP Walden Pub Rep
WKNDED Weekend Editor
WOMANED Womens Interest Editor
WRITER Writer
WTHRED Weather Editor
YOUTHED Teen and Youth Editor

State Code

State Codes

Code Description
AB Alberta
ACT Australian Capital Territory
AE AMERICAN EUROPE
AK ALASKA
AL ALABAMA
AR ARKANSAS
AS American Samoa
AZ ARIZONA
BC British Columbia
CA CALIFORNIA
CM Central Marianas
CO COLORADO
CT CONNECTICUT
DC DISTRICT OF COLUMBIA
DE DELAWARE
FL FLORIDA
FM Federated States of Micronesia
GA GEORGIA
GU GUAM
HI HAWAII
IA IOWA
ID IDAHO
IL ILLINOIS
IN INDIANA
KS KANSAS
KY KENTUCKY
LA LOUISIANA
MA MASSACHUSETTS
MB Manitoba
MD MARYLAND
ME MAINE
MH Marshall Islands
MI MICHIGAN
MN MINNESOTA
MO MISSOURI
MP MIDDLE PACIFIC
MS MISSISSIPPI
MT MONTANA
MW Midway Islands
N.T. Northern Territory (Australia)
NB New Brunswick
NC NORTH CAROLINA
ND NORTH DAKOTA
NE NEBRASKA
NF Newfoundland
NH NEW HAMPSHIRE
NJ NEW JERSEY
NM NEW MEXICO
NP Northern Marianas
NS Nova Scotia
NSW New South Wales
NT Northwest Territory
NU Nunavut
NV NEVADA
NY NEW YORK
OH OHIO
OK OKLAHOMA
ON Ontario
OR OREGON
PA PENNSYLVANIA
PE Prince Edward Island
PQ Quebec
PR PUERTO RICO
PW Pacific West
QLD Queensland
RI RHODE ISLAND
SA South Australia
SC SOUTH CAROLINA
SD SOUTH DAKOTA
SK Saskatchewan
TAS Tasmania
TN TENNESSEE
TT PACIFIC TERRITORIES
TX TEXAS
UT UTAH
VA VIRGINIA
VI VIRGIN ISLANDS
VIC Victoria
VT VERMONT
W.A. Western Australia
WA WASHINGTON
WI WISCONSIN
WV WEST VIRGINIA
WY WYOMING
YT Yukon Territory

Country Code

Country Codes

Note for Channel Partners only USA is allowed.

Code Description
830 Channel Islands
ABW ARUBA
AFG AFGHANISTAN
AGO ANGOLA
AIA ANGUILLA
ALB ALBANIA
AND ANDORRA
ANT NETHERLANDS ANTILLES
ARG ARGENTINA
ARM ARMENIA
ASM AMERICAN SAMOA
ATA ANTARCTICA
ATF FRENCH SOUTHERN TERRITORIES
ATG ANTIGUA & BARBUDA
AUS AUSTRALIA
AUT AUSTRIA
AZE AZERBAIJAN
BDI BURUNDI
BEL BELGIUM
BEN BENIN
BFA BURKINA FASO
BGD BANGLADESH
BGR BULGARIA
BHR BAHRAIN
BHS BAHAMAS
BIH BOSNIA & HERZEGOVINA
BLR BELARUS
BLZ BELIZE
BMU BERMUDA
BOL BOLIVIA
BRA BRAZIL
BRB BARBADOS
BRD West Germany
BRN BRUNEI DARUSSALAM
BTN BHUTAN
BVT BOUVET ISLAND
BWA BOTSWANA
BWI BRITISH WEST INDIES
CAF CENTRAL AFRICAN REPUBLIC
CAN CANADA
CCK COCOS (KEELING) ISLANDS
CHE SWITZERLAND
CHL CHILE
CHN CHINA
CIV COTE' D' IVOIRE
CMR CAMEROON
COD CONGO, THE DEMOCRATIC REPUBLIC OF THE CONGO
COG CONGO
COK COOK ISLANDS
COL COLOMBIA
COM COMOROS
CPV CAPE VERDE
CRI COSTA RICA
CSK Czechoslovakia
CUB CUBA
CXR CHRISTMAS ISLAND
CYM CAYMAN ISLANDS
CYP CYPRUS
CZE CZECH REPUBLIC
DDR East Germany
DEU GERMANY
DJI DJIBOUTI
DMA DOMINICA
DNK DENMARK
DOM DOMINICAN REPUBLIC
DZA ALGERIA
ECU ECUADOR
EGY EGYPT (ARAB REPUBLIC OF EGYPT)
ERI ERITREA
ESH WESTERN SAHARA
ESP SPAIN
EST ESTONIA
ETH ETHIOPIA
FIN FINLAND
FJI FIJI
FLK FALKLAND ISLANDS
FRA FRANCE
FRO FAROE ISLANDS
FSM FEDERATED STATES OF MICRONESIA
GAB GABON
GBR UNITED KINGDOM
GEO GEORGIA
GHA GHANA
GIB GIBRALTAR
GIN GUINEA
GLP GUADELOUPE
GMB GAMBIA
GNB GUINEA-BISSAU
GNQ EQUATORIAL GUINEA
GRC GREECE
GRD GRENADA
GRL GREENLAND
GTM GUATEMALA
GUF FRENCH GUIANA
GUM GUAM
GUY GUYANA
HKG HONG KONG
HMD HEARD ISLAND & MCDONALD ISLANDS
HND HONDURAS
HRV CROATIA
HTI HAITI
HUN HUNGARY
IDN INDONESIA
IND INDIA
IOT BRITISH INDIAN OCEAN TERRITORY
IRL IRELAND
IRN IRAN, ISLAMIC REPUBLIC OF
IRQ IRAQ
ISL ICELAND
ISR ISRAEL
ITA ITALY
JAM JAMAICA
JOR JORDAN
JPN JAPAN
KAZ KAZAKSTAN
KEN KENYA
KGZ KYRGYZSTAN
KHM CAMBODIA
KIR KIRIBATI
KNA SAINT KITTS & NEVIS
KOR KOREA, REPUBLIC OF
KOS Kosova
KWT KUWAIT
LAO LAO PEOPLE'S DEMOCRATIC REPUBLIC
LBN LEBANON
LBR LIBERIA
LBY LIBYAN ARAB JAMAHIRIYA
LCA ST. LUCIA
LIE LIECHTENSTEIN
LKA SRI LANKA
LSO LESOTHO
LTU LITHUANIA
LUX LUXEMBOURG
LVA LATVIA
MAC MACAU
MAR MOROCCO
MCO MONACO
MDA MOLDOVA, REPUBLIC OF
MDG MADAGASCAR
MDV MALDIVE ISLANDS
MEX MEXICO
MHL MARSHALL ISLANDS
MKD MACEDONIA, THE FORMER YUGOSLAV REPUBLIC OF
MLI MALI
MLT MALTA
MMR MYANMAR
MNE MONTENEGRO
MNG MONGOLIA
MNP NORTHERN MARIANA ISLANDS
MOZ MOZAMBIQUE
MRT MAURITANIA
MSR MONTSERRAT
MTQ MARTINIQUE
MUS MAURITIUS
MWI MALAWI
MYS MALAYSIA
MYT MAYOTTE
NAM NAMIBIA
NCL NEW CALEDONIA
NER NIGER
NFK NORFOLK ISLAND
NGA NIGERIA
NIC NICARAGUA
NIU NIUE
NLD NETHERLANDS
NOR NORWAY
NPL NEPAL
NRU NAURU
NZL NEW ZEALAND
OMN OMAN
PAK PAKISTAN
PAN PANAMA
PCN PITCAIRN
PER PERU
PHL PHILIPPINES
PLW PALAU
PNG PAPUA NEW GUINEA
POL POLAND
PRI PUERTO RICO
PRK KOREA, DEMOCRATIC PEOPLE'S REPUBLIC OF
PRT PORTUGAL
PRY PARAGUAY
PSE Occupied Palestinian Territory
PYF FRENCH POLYNESIA
QAT QATAR
REU REUNION
ROM ROMANIA
RUS RUSSIAN FEDERATION
RWA RWANDA
SAU SAUDI ARABIA
SCG SERBIA & MONTENEGRO
SDN SUDAN
SEN SENEGAL
SGP SINGAPORE
SGS SOUTH GEORGIA & THE SANDWICH ISLANDS
SHN SAINT HELENA
SJM SVALBARD & JAN MAYEN
SLB SOLOMON ISLANDS
SLE SIERRA LEONE
SLV EL SALVADOR
SMR SAN MARINO
SOM SOMALIA
SPM SAINT PIERRE & MIQUELON
SRB SERBIA
STP SAO TOME E PRINCIPE
SUN U.S.S.R.
SUR SURINAME
SVK SLOVAKIA
SVN SLOVENIA
SWE SWEDEN
SWZ SWAZILAND
SYC SEYCHELLES
SYR SYRIAN ARAB REPUBLIC
TCA TURKS & CAICOS ISLANDS
TCD CHAD
TGO TOGO
THA THAILAND
TJK TAJIKISTAN
TKL TOKELAU
TKM TURKMENISTAN
TMP EAST TIMOR
TON TONGA
TTO TRINIDAD & TOBAGO
TUN TUNISIA
TUR TURKEY
TUV TUVALU
TWN TAIWAN, REPUBLIC OF CHINA
TZA TANZANIA, UNITED REPUBLIC OF
UAE UNITED ARAB EMIRATES
UGA UGANDA
UKR UKRAINE
UMI UNITED STATES MINOR OUTLYING ISLANDS
URY URUGUAY
USA UNITED STATES
UZB UZBEKISTAN
VAT VATICAN CITY STATE (HOLY SEE)
VCT SAINT VINCENT & THE GRENADINES
VEN VENEZUELA
VGB VIRGIN ISLANDS, BRITISH
VIR VIRGIN ISLANDS, U. S.
VNM VIET NAM
VUT VANUATU
WLF WALLIS & FUTUNA
WSM SAMOA
YEM YEMEN
YUG YUGOSLAVIA
ZAF SOUTH AFRICA
ZAR Zaire
ZMB ZAMBIA
ZWE ZIMBABWE

Restriction Code

Restriction Codes

Code Description
CSONLY Create Space is only allowed distributor
NOLIMIT no limit on number of distributor

Revision: r1.30 - 23 Jul 2013 - 19:14:04