Writer Sheet Show Menu

Zoho Office API

Overview

Zoho Office API is for all applications that store documents as part of business process or services. Partners can integrate Zoho Office API into their document system and open documents for viewing and editing purposes in the respective Zoho web-based editors. Zoho Office API integration does not require any unnecessary software installations and plug-ins. Partners also need not worry about any additional charges for using our host servers. Zoho Office API also provides collaborative editing capabilities which is indispensable for any kind of teamwork. Zoho Office API stores your documents only during the time of edit or view operation.

Zoho Office APIs are currently available for Zoho Writer, our online word processor, Zoho Sheet, our online spreadsheet application and Zoho Show, our online presentation. This reference guide will provide partners with the necessary details to integrate Zoho Office APIs. You can use Zoho Office APIs for free by using our trial version.

How does it work?

With Zoho Office API, you can:

  • Create a new document, spreadsheet or presentation from your web application.
  • Open existing documents.
  • View and edit documents based on the access privileges defined by the administrator of your web application.
  • Collaborate on the documents in real-time.
  • Save the document content back to your document servers.

Get Started

The API key is used to uniquely identify the application in which you integrate Zoho services. The API key has to be passed as a parameter in every request and is used to make API calls, retrieve data or do specific actions. We use the API key to track usage of various applications and generate reports based on them. Each partner application that has a Zoho Service integrated should have a separate Zoho account and a unique API key associated with it. Your API key is related to your Zoho account.

Create a Zoho Account

  1. Go to: https://accounts.zoho.com/accounts/register?servicename=AaaServer
  2. Fill in details like your full name, email and create a password.
  3. Click Sign Up.You will be taken to your account dashboard.

Note : A verification link will be sent to your email when you sign up with Zoho. You need to visit your inbox and click the verification link to complete your registration process.

Generate API Key

Partners can register for a Zoho API key by performing the following steps :

  1. Go to https://zapi.zoho.com
  2. Fill out the form which will look like the one below:
  3. Generate API Key
  4. Click Generate API Key. You will be taken to your account dashboard.
  5. Generate API Key

You will be assigned an alphanumeric key by Zoho that is uniquely associated to your Zoho account. The API key, thus generated, will be common for both the Office API and Docs API and can be used to make API calls, retrieve data or do specific actions.

The API key is unique and is connected to your Zoho account. Please keep the API key private. Do not distribute or use the API key for creating multiple services. You should request an API key for each individual service that you plan to create. Any violations will result in the cancellation of the API Key and the suspension of your Zoho account.

Note : When you create a Zoho account and generate an API key, you will be subscribed to our 3-Month trial version by default, where you can use up to 3000 User Document Sessions (UDS). However, you can always upgrade to commercial plans if you want. If you exhaust your UDS limit within your validity period (while using a commercial plan) your plan will automatically downgrade to the free plan. To check your UDS usage details anytime, you can visit https://zapi.zoho.com/apigen.do.

Opening a file

In order to invoke the Zoho Office API and open a document in Zoho service editors, the developer needs to submit a request by way of a HTTPS POST form to the specific Zoho service URL. Depending on the file type (docx, xlsx, pptx), the request can be sent to the following URLs:

  • Zoho Writer - https://writer.zoho.com/writer/remotedoc.im
  • Zoho Sheet - https://sheet.zoho.com/sheet/remotedoc.im
  • Zoho Show - https://show.zoho.com/show/remotedoc.im

Now, there can be a couple of ways of uploading the document to Zoho service editors via an HTTPS POST form. Depending on the location of the file (desktop or web) Partners can use either of the two methods:

  1. Multi-part form submit - This is used for opening documents present in the partners' document management system.
  2. Normal form submit - This is for opening documents that are present over a web URL and accessible by Zoho Document Servers.
Form Request Parameters Reference

Common Parameters

Following are the common parameters that need to be passed in multi-part and normal HTTPS POST request :

Parameter Type Description
apikey string This is a mandatory parameter. It uniquely identifies the web-application in which the Zoho service editors are integrated.
output string

This is a mandatory parameter. It determines the format in which the Zoho service output will be sent.

Possible values : view, editor, viewurl, url
Default value : url

mode string

This is a mandatory parameter. It defines the access privilege of the user while opening the document in Zoho service editors.

Possible values : view, normaledit, collabview, collabedit

view -- Document opens in read-only mode.

normaledit -- Document opens exclusively in edit mode for the user. No other collaborator is allowed.

collabview -- Document opens in collaborative view mode. Multiple users can view the contents of the document at the same time and leave notes/comments using the integrated chat service. However, they cannot edit the document content.

collabedit -- Document opens in real-time collaborative edit mode. Multiple users can edit the document at the same time.

filename string

This is a mandatory parameter. It is the name of the document with the proper file extension.

documentid long integer or string (returned by Zoho)

This is the unique id of the document for identification purpose. In case of the user failing to provide a document id, Zoho servers will generate one automatically in the form of an encrypted string.

lang string

This parameter is optional. It enables each Zoho service (Writer/Sheet/Show) to offer its remote editor interface in a different language.

Default value: en (English)

For a full list of languages supported by Zoho service remote editors, please click here.

id string

This is a mandatory parameter. It is the unique handback id or doc session id that integrators/users need to provide while sending the request to Zoho for opening a particular document.

The 'id' parameter can be used to store all relevant document-related information, including session id, list of shared users, doc id etc. in the form of encoded string.

The information in 'id' parameter will be returned to the 'saveurl' by Zoho Document Servers whenever 'save' is invoked by the user.

Use-case: By providing shared user information in the 'id' parameter, a developer or a saveurl handler of the Zoho-integrated application will get to know which shared user has saved a document during collaboration.

format string

This is a mandatory parameter for editing. It is the format in which the document needs to be saved back to the partner document repository.

Supported values for documents : doc, docx, html, pdf, htm, odt, rtf, txt
Supported values for spreadsheets : xls, xlsx, ods, sxc, csv, tsv, pdf
Supported values for presentations : ppt, pptx, pps, ppsx, odp, sxi

saveurl boolean

This is a mandatory parameter for editing. The saveurl is a publicly accessible web URL which should be a service that fetches the content of the updated document from Zoho Document Servers and saves it to the partner document repository.

Also, please ensure that the value provided for the 'saveurl' parameter does not contain spaces. Saveurl value containing spaces will throw an error and the file will not get saved.

Example - https://example.com/docs/save.php.

Note

  • The saveurl specified over https/http URL scheme should be a public, accessible, proper domain name with its port set to 443/80. Setting IP Address as saveurl value is not advised. This will return an error.
  • If you are using an https URL, please make sure that it complies with the list of certifications here .

Specific Parameters

For multi-part form submit:
Parameter Value Description
content string This is a mandatory parameter. It is the actual document content to be uploaded to Zoho service editors. A new document will be created if there is no content.

Note
While triggering an API call, if you do not pass any content, a new file will be created.

For normal form submit:
Parameter Value Description
url string

This is a mandatory parameter. It is a publicly accessible web URL from which the Zoho service editor can fetch the document content.

Note: It is mandatory to specify the absolute path of the document in the URL parameter with proper file extension.

Also, the port of the document web-URL should be set to '443' while sending the request to Zoho over https URL scheme.

Example: https://example.com/documents/mysample.docx.

Note: If you are using an https URL, please make sure that it complies with the list of certifications here .

Output parameter values *

The output parameter decides the format in which the output is sent from Zoho document servers. This is in response to the request sent by the partner to open the document. Currently, Zoho allows four different values for the output parameter.

  1. url: With "url" as the output parameter value, partners will get a response of the document in the form of a URL. The document URL can then be sent from the partner server to the client side (user's web browser) to open the document content in Zoho service editors for editing.
  2. viewurl: With "viewurl" as the output parameter value, the document content will be uploaded in Zoho service editors in "view-only" mode.

    Response format of url/viewurl request:

    URL=document url value
    WARNING=warning message
    RESULT=TRUE
    Note: RESULT field indicates the status of the action. Zoho will return 'TRUE' if the request is posted successfully. 
    Otherwise, the value will be 'FALSE'.
    Similarly, if any of the parameters are found to be incorrect, you will get a warning message stating the same. 
    Otherwise the value returned will be 'NULL'.

    Sample response of url/viewurl request:

    URL=https://show.zoho.com/show/remoteedit.sas?doc=zPPG0w707d7wax67020x68F
    WARNING=NULL
    RESULT=TRUE

    Note : Partners who wish to access Zoho service editors from within their website can provide the output parameter value as either "url" or "viewurl". In turn, the document URL obtained can be added to the "src" attribute of "iframe" tag for embedding the Zoho editors.

  3. editor: When you pass "editor" as the output parameter value, the response is redirected to the editor page from Zoho Writer, Zoho Sheet and Zoho Show servers. On the other hand, Zoho Writer returns a javascript code snippet that automatically opens the Writer editor with the document content for editing.
  4. view: With "view" as the output parameter value, the response is redirected to the editor page from Zoho Writer, Zoho Sheet and Zoho Show servers. Zoho Document servers will return a javascript code snippet that automatically opens the respective editor with the document content for viewing purpose only.

    Note: Partners who wish to open the Zoho service editors in a new browser tab/window instead of embedding it in their website can provide the output parameter value as either "editor" or "view".

Errors

In case of a user missing any mandatory parameter or providing incorrect value for the same, Zoho will return exceptions in a generalized 'name-value' format.

Sample error response

RESULT=FALSE
ERROR_CODE=3832
WARNING=The value specified for API key is invalid.

For a complete list of error codes, please click here.

Multi-part Form Submit - Sample

Normal Form Submit - Sample

Important Note : We recommend that partners send the request to Zoho as an emulated multi-part form (HTTPS POST) from their server. If the request is sent from the server, the API key is not exposed to the client side and will not be subjected to third-party hacks. The work flow for the whole request goes like the one below :

Steps

  1. User visits partner web portal that has Zoho remote API integrated and places a request for opening a document.
  2. The request for opening the document, is sent as a multi-part form (HTTPS POST) from partner's server to Zoho's document servers.
  3. Zoho, in turn, returns the URL of the document to partner's server.
  4. The document URL is then sent from partner's server to the client side (user's browser).
  5. User's browser loads the document content in Zoho editor.

Error Messages

Zoho Writer Error Code Zoho Sheet Error Code Zoho Show Error Code Category Description
1840 2840 3840 General Unable to import content from the specified url.
1841 2841 3802 General Unable to import content
1842 2842 3844 General Invalid File extension
1843 2843 3843 General File name not found
1844 2844 NA General File extension not found
1845 2845 NA General Unable to allocate URL
1846 2846 3846 General Unable to import content. Document seems to have virus.
1847 2847 3847 General Username not found. Please enter username
1848 2848 3848 Input Missing "Id" parameter value.
1849 2849 3849 Input Import failed. Possible reasons:
  1. The "documentid" value provided is either incorrect or invalid.
  2. The document is either malformed or its file format is not supported by Zoho.
1850 2850 3850 Input RemoteDocStatus error: The value specified for 'doc' parameter is missing or invalid.
1801, 1802, 1803 2801, 2802, 03 3800, 3801 General Internal Server Error while processing this request.
1831 2831 3831 Input Mandatory parameter(s) missing.
1890 2890 3890 Input The 'API Key' is invalid.
1891 2891 3891 Input The specific URI request is incorrect.
1893 2893 3893 General UDS Limit or API usage exceeded.
NA NA 3800 General Unable to import the presentation.
NA NA 3801 General Unable to export presentation to specified format.
NA NA 3803 General Remote upload of a presentation failed.
NA NA 3852 General Presentation with specific id is trashed. Hence, inaccessible.
NA 2833 NA General The Content-Type header set in your HTTP request is incorrect.
NA NA 3835 General File size limit exceeded.
NA NA 3839 General Invalid filename
NA NA 3845 General Unsupported file format
1893 NA NA General API key usage exceeded.
1894 NA NA General Admin account associated with this API key has been deleted.
1853 NA NA General Unable to import file from the given URL.

Saving a file

'saveurl' is a mandatory parameter. The save URL is a publicly accessible web URL which should be a service that fetches the content of the updated document from Zoho Document Servers and saves it to the partner document repository.

Also, please ensure that the value provided for the 'saveurl' parameter does not contain spaces. Save URL value containing spaces will throw an error and the file will not get saved.

Example - https://example.com/docs/save.php.

Note

  • The saveurl specified over https/http URL scheme should be a public, accessible, proper domain name with its port set to 443/80. Setting IP Address as saveurl value is not advised. This will return an error.
  • If you are using an https URL, please make sure that it complies with the list of certifications here.
Steps: Document Save and Notification
  1. User clicks on save button from Zoho service editor.
  2. Zoho Document Server receives a save request from the Zoho editors.
  3. Zoho Document Server pushes the updated content to the partner save URL.
  4. The partner's document management application in turn notifies Zoho Document Server that the save action is done successfully.
  5. Document is saved back to the partner's repository.
Save Notification Messages

The partner's application can customize the save notification message sent to Zoho servers. The message is shown when the user saves the document from Zoho service editor and handles both the save cases:

  1. Success Message (HTTP response code 200) - Sent when the document is saved successfully.
  2. Error Message (HTTP response code 500) - Sent when the document save fails.

The response to be sent to Zoho servers is of the format:

RESPONSE: [Success or Failure Information message from the application]

Note : In case the partner application fails to provide a custom message of its own, Zoho will display its default save notification messages in the service editors. A list of these messages is given below:

Save Notification Messages Description
Save in progress
A request for saving the document is initiated when the user clicks on the save button.
Document saved successfully. Default notification message displayed by Zoho when a document is saved successfully in the partner's application.

This message will appear when Zoho receives only an HTTP response code 200 without any custom message from the partner's application.
Document already saved.
No document modification is detected. This message will appear in two cases:
  1. When the user hits the save button without modifying the contents of the original document.
  2. After getting the 'Document Saved Successfully' message, if the user inadvertently hits the save button without making any further edits to the document.
<Partner application's customized success message>
This is the custom save notification message displayed when a document is saved successfully.

This message is sent from the partner's application server with HTTP status code 200 and is of the format - RESPONSE: [Success Information message from the application]
<user name> has saved the document.
This message is displayed when Zoho notifies 'Document saved status' to shared users in collaboration mode.
Problem in saving content. Please retain a local copy at your end and try again later.
This message is displayed when the save notification, sent as response, to Zoho servers from the partner application either fails or is null. HTTP status code is other than 200.
Error in saving document from remote client side.
This message is displayed when Document save fails. HTTP status code 500 is returned to Zoho servers as a response with a custom message in the following format - RESPONSE: [Failure Information message from the application]
Problem in saving complex document. Please retain a local copy at your end and try again later.
This message is displayed when the user tries to save a document with null content into partner's application.
Problem in posting the document. Please retain a local copy at your end and try again later.
This message is displayed when any error is encountered while posting content to the partner's server via saveurl or remote agent method.
Document format not supported. Error in saving content.
This message displayed when the document content is saved in an unsupported format.
Connection refused from the remote server.
This message displayed when the save response from the partner's application is timed out.

Collaborating on a file

Document Collaboration with Zoho Office API

Zoho Office API supports real-time document collaboration. This means that several users can open a particular document at the same time, with everyone being able to contribute to the document in real time.

With the built-in collaboration features, an partner's portal can enhance user productivity, foster teamwork and cooperation. When a document is shared, teams can work together at the same instance. So when someone makes a change, the document is updated for everyone to see. In addition, the integrated Zoho chat application allows users to communicate with each other in real time.

Implementing Document Collaboration - The Basics

Before getting started with the implementation of collaboration features, partners need to know a few parameters and their definitions. The most important among them are:

Mode

The mode parameter determines the way in which the document gets uploaded to Zoho service editors for a particular user. Based on the access privileges defined by the partner/administrator for different users in a user group, they can either view or edit a particular document simultaneously. Currently, Zoho allows four different values that can be passed in the mode parameter. They are :

  • view - Document opens in read-only mode.
  • normaledit - Document opens in edit mode exclusively for the particular user. Collaboration will not be available.
  • collabview - Document opens in collaborative view mode. Multiple users can view the document and leave notes/comments. However, they will not be able to edit the document.
  • collabedit - Document opens in real-time collaborative edit mode. Multiple users can edit the document and leave notes/comments.

documentid

The document id, as the name suggests, is the unique id of a particular document and is used for identification purpose. The value of documentid parameter should be passed as a long integer from the user's end. In case the user fails to provide a document id during form submit, Zoho servers will generate one automatically as an encrypted string. When a document is uploaded to Zoho editors for editing, a unique and encrypted document URL is assigned to it. This document URL will persist as long as the document session is active. Once the user exits the document session, by closing or refreshing the browser tab, the document URL becomes invalid.

In the case of collaborative edit or view mode where multiple users may be working on the document at the same time, the document URL will be active until the last user exits the document session.

As you can see, Zoho generates a dynamic URL every time a document (new or existing) is uploaded to Zoho service editors. Therefore, it is recommended that users should leave the task of assigning the document id (encrypted) to Zoho instead of providing one for themselves.

Note : The document id provided here is associated with a particular API key and will be unique for that API key. In case a user provides a document id that has already been used earlier, Zoho will load the existing document to its editors. In short, a document id can be similar across different API keys, but it should be unique for a specific API key.

username

This is the name of the user who is opening the document in collaborative mode. Partners need to take care of the following when establishing a collaboration session for their users:

  • Partner's remote server should provide the usernames in order to list the collaborators properly. By default, Zoho servers will identify collaborators as "Guest" if no username is given.
  • They should explicitly mention the mode as "collabedit/collabview".
  • In order to set up a collaboration session, all shared users should provide the same documentid.
  • For subsequent collaboration sessions on the same document, partner's remote server should maintain the document id associated with it.

Note : It is mandatory to set the output parameter value as "url" when mode is chosen as "collabedit" during form submit.

Sample Response for collaborative editing in Zoho Office API

In collaborative editing mode, a documentid (optional) along with the document URL is returned to the user from Zoho servers. This means, several users can join the collaboration session by specifying this documentid and jointly view/edit the document. The response format will look like the one below:

RESULT = TRUE
URL = unique url
DOCUMENTID = encrypted unique docid

Remote Document Presence Status

The "remotedocStatus" API is used to check whether the document is already present in Zoho server or needs to be uploaded again from the partner's server. This is a servlet call which returns "documentid", "isPresent" and "collaboratorsCount" as a response.

If the "isPresent" value is returned as "false", partner can conclude that the document session is closed and is no longer available in Zoho servers.

Request
Parameter Type Description
api key
string
This is a mandatory parameter. It uniquely identifies the web application in which the Zoho service editors are integrated.
doc
integer This is a mandatory parameter.It is the unique id of the document (documentid) either provided by the partner application or sent by Zoho.
For Zoho Writer - https://writer.zoho.com/writer/remotedocStatus.im?doc=&apikey=Zoho_API_Key
For Zoho Sheet - https://sheet.zoho.com/sheet/remotedocStatus.im?doc&apikey=Zoho_API_Key
For Zoho Show - https://show.zoho.com/show/remotedocStatus.im?doc&apikey=Zoho_API_Key
Response

The response for the remotedocStatus is a JSON string and will look like the one below :

 {"result":{
                    "docid":"9765",
                    "isPresent":"true",
                    "collaboratorsCount":"4"
                     }}  
Parameter Type Description
isPresent boolean True - If the document is available.
False - If the document is not available.
collaboratorsCount integer This is the number of collaborators working on the shared document.

Manage

You'll be able to log on to https://zapi.zoho.com and view details related to your account and usage at any time.

Your Account Overview

After login, the dashboard will provide the most essential details of your account. You will be able to see your API key details, your plan, your current usage and your previous billing.

You may track your usage by clicking the Usage Details tab.This tab will give you a graphical representation of your usage and a table elaborating the same. You can choose to see this report based on operation or service by clicking the appropriate options in the left panel of this page. Different time limits are displayed at the top to help you view your usage during specific time limits.

Access and update your billing details

You can see your subscription details under Account Details by clicking Subscription Details in the side panel. This tab will display your API key and subscription details like the date on which your Zoho account was created, the name of your plan, your add- ons, fixed monthly charges and the start and end dates of your plan. You can also see your recent billing details in the same page by clicking Billing Details in the left panel. A filter is available at the top of this page which lets you access the billing details for specific periods of time.

If you have a payment profile ID for billing purposes with your Zoho account, you will be able to see the Change Credit Card option under Account Details.When you click Change Credit Card, you will be able to see your current credit card details like the last four digits of your credit card number, your recurring amount, last paid date and next payment date. If you want to change these details, click Update Card at the end of this page. A new window will show up where you can feed the new details and update the same.

Limitations

Some of the limitations of Zoho Office API are listed below.

Zoho Writer Zoho Sheet Zoho Show
Document History & Versions VBA Macros Ability to Make Remote Presentations
Doc Roll: Listing public documents in your website or blog Pivot Tables & Pivot Chart Duplicate a Presentation
DigiSign: Ability to digitally sign Writer documents Publish Spreadsheets Presentation History & Versions
Custom Dictionary Insert Button Publish Presentations
Email At: Receive documents from the desktop or Gmail/Yahoo/MSN email providers to your Writer account Insert Comment at the workbook level. 
PS: One can insert comments on a particular cell in a worksheet.
Add Tags
Publish Document  Linking External Data

Spreadsheet History, Versions & Audit Trail

Spreadsheet Settings (Locale Settings)

Tab Colors

Limit of 1 million cells per workbook; Maximum of 65536 rows or 256 columns per worksheet

Get Support

If you need any assistance with the integration or if you face any issues with the product, you can always let us know via email , phone or by posting it in our forum.

Email: api-support@zohocorp.com
Talk to us: +1 403 352-9170
Forum: https://forums.zoho.com/zoho-docs/remote-apis

Alternatively, you can also use the tools available in the Support tab to write to us.

Zoho API - SSL Support

Zoho API access over SSL - List of Certification Authority (CAs) supported

Zoho APIs can be accessed over SSL by partners integrating various Zoho apps into their existing applications. This, in turn, will be an added assurance for them as the transfer of data will be over a secure (https) connection. For accessing Zoho apps over a https connection, partners need to have a server with SSL certificate that is signed by a valid certification authority (CA).

Currently, Zoho supports the CAs (Certification Authority) that are part of Sun's JRE list. Partners need to ensure that before purchasing a certificate, they have to check whether their certification authority (CA) is in the list mentioned below. SSL access will work only if the root CA or intermediate CA is from one of the listed CAs.

List of CAs Supported:

Sl # Certificate Name
01. AAA Certificate Services
02. AddTrust Class 1 CA Root
03. AddTrust External CA Root
04. AddTrust Qualified CA Root
05. America Online Root Certification Authority 1
06. America Online Root Certification Authority 2
05. Baltimore CyberTrust Code Signing Root
06. Baltimore CyberTrust Root
07. Certum CA
08. Certum Trusted Network CA
09. Chambers of Commerce Root
10. Chambers of Commerce Root - 2008
11. Class 1 Public Primary Certification Authority
12. Class 2 Primary CA
13. Class 3 Public Primary Certification Authority
14. Class 3P Primary CA
15. Deutsche Telekom Root CA 2
16. DigiCert Assured ID Root CA
17. DigiCert Global Root CA
18. DigiCert High Assurance EV Root CA
19. Entrust Root Certification Authority
20. Entrust Root Certification Authority - G2
21. Entrust.net Certification Authority (2048)
22. Entrust.net Secure Server Certification Authority
23. Equifax Secure Certificate Authority
24. Equifax Secure eBusiness CA-1
25. Equifax Secure Global eBusiness CA-1
26. GeoTrust Global CA
27. GeoTrust Primary Certification Authority
28. GeoTrust Primary Certification Authority - G2
29. GeoTrust Primary Certification Authority - G3
30. GeoTrust Universal CA
31. Global Chambersign Root - 2008
32. GlobalSign
33. GlobalSign Root CA
34. Go Daddy Class 2 Certification Authority
35. Go Daddy Root Certification Authority - G2
36. GTE CyberTrust Global Root
37. GTE CyberTrust Root 5
37. InCommon Cert
38. KEYNECTIS ROOT CA
39. QuoVadis Root CA 2
40. QuoVadis Root CA 3
41. QuoVadis Root Certification Authority
42. SecureTrust CA
43. Security Communication EV RootCA1
44. Security Communication  RootCA1
45. Security Communication RootCA2
46. Sonera Class1 CA
47. Sonera Class2 CA
48. Starfield Class 2 Certification Authority
49. StartCom Certification Authority
50. StartCom Class 2 Primary Intermediate Server CA
51. SwissSign Gold CA - G2
52. SwissSign Platinum CA - G2
53. SwissSign Silver CA - G2
54. T-TeleSec GlobalRoot Class 2
55. T-TeleSec GlobalRoot Class 3
56. TC TrustCenter Class 2 CA II
57. TC TrustCenter Class 4 CA II
58. TC TrustCenter Universal CA I
59. Thawte Personal Freemail CA
60. Thawte Premium Server CA
61. Thawte Primary Root CA
62. Thawte Primary Root CA - G2
63. Thawte Primary Root CA - G3
64. Thawte Server CA
65. Thawte Timestamping CA
66. UTN - DATACorp SGC
67. UTN-USERFirst-Client Authentication and Email
68. UTN-USERFirst-Hardware
69. UTN-USERFirst-Object
70. VeriSign Class 1 Public Primary Certification Authority - G3
71. VeriSign Class 2 Public Primary Certification Authority - G3
72. VeriSign Class 3 Public Primary Certification Authority - G3
73. VeriSign Class 3 Public Primary Certification Authority - G4
74. VeriSign Class 3 Public Primary Certification Authority - G4
75. VeriSign Class 3 Public Primary Certification Authority - G5
76. VeriSign Trust Network
77. VeriSign Universal Root Certification Authority
78. http://www.valicert.com/