{"info":{"_postman_id":"fc3101b5-af80-4582-84ea-4a3521c7a291","name":"Trustico® API","description":"

The Trustico® API allows you to integrate your applications with Trustico’s order management and certificate lifecycle tools to make it easy for your customers to order and manage certificates and website identity products without leaving your site. The Trustico® API uses REST and contains web services for creating new orders and working with existing orders.

Getting Started (Authenitcation OAuth2.0):

The Trustico® REST API requires an access token to be used for every request sent to any endpoint. Our API uses OAuth 2.0 for secure connections between your website and the API, allowing for a robust and secure line for communication.

To complete an access token request, follow the steps below:

Register for a reseller account and get your API credentials. Once logged in to your reseller portal, go to Manage Account > Account Settings and under the API Settings tab you will find your API credentials.
\n
Save your client ID and client Secret details.
\n
Use your coding library and environment of choice, and send an access token request to the following endpoint : https://api.trustico.com/oauth2/token
\n
Once an access token is available, you can start making API calls using your new access token.
\n

Sample code below for requesting an access token using Javascript:

const https = require('https'); // Import the https module\nconst handler = async (event) => {\n  try {\n    const clientId = \"CLIENT_ID_HERE\";\n    const clientSecret = \"CLIENT_SECRET_HERE\";\n    const fetch = (await import('node-fetch')).default;\n    const tokenUrl = 'https://api.trustico.com/oauth2/token';\n    const response = await fetch(tokenUrl, {\n      method: 'POST',\n      headers: {\n        'Content-Type': 'application/x-www-form-urlencoded',\n      },\n      body: new URLSearchParams({\n        'grant_type': 'client_credentials',\n        'client_id': clientId,\n        'client_secret': clientSecret,\n      }),\n    });\n    if (!response.ok) {\n      throw new Error(`Failed to fetch access token: ${response.statusText}`);\n    }\n    const data = await response.json();\n    return {\n      statusCode: 200,\n      body: JSON.stringify(data),\n    };\n  } catch (error) {\n    console.error('Error:', error);\n    return { statusCode: 500, body: error.toString() };\n  }\n};\nmodule.exports = { handler };\n\n

*Note: the Trustico API token refreshes periodically to ensure that a connection is secure by using a new access token. You may need to incorporate a token refresh function to periodically check if the current token is valid, if not, then the token must be refreshed by invoking another token URL request for a new token.

Below are some important details to take into consideration when mkaing your first API calls

Country ISO2 Codes

A list of valid country codes can be found through this link below

(ex. Australia Country Code = \"AU\"):

Trustico Valid Country Codes

Error Codes

The following details define the Error Codes which might be encountered when making an API call to the Trustico API:
1001 : Wrong value in field or validation fails
1002 : Error occurred during function execution. (ex.: parsing a CSR fails)
1003 : Not found. i.e. Order not found
1004 : API is disabled for reseller account
1005 : User request limit reached
1006 : Method is not allowed in TEST mode
1007 : API does not support GET method
1008 : Certificate not generated
1009 : Certificate not found
1010 : Order not processed yet. Once your Order has been processed, you will be able to use this method.
1011 : Validation method must be file based
1012 : Validation method must be DNS based
1016 : Coupon Code Not Applicable (Invalid or not available for product)

TEST Mode

The TEST API mode allows for only limited API access. We recommend using TEST mode when integrating the Trustico API with your application for the first time.

You can find the setting to toggle between TEST and LIVE mode in your reseller panel (My Account > Account Settings under API setting tab).

When the API is accessed in TEST mode, the following descriptor is added to an endpoint response:

“API working in test mode.”

Method Endpoint Allowances

The following shows what methods are available in TEST and LIVE mode:

Hello - This method will work in TEST and LIVE mode.
\n
ParseCSR - This method will work in TEST and LIVE mode.
\n
GetOrderStatus - This method will work in TEST and LIVE mode, however a TEST mode order will only show the default Unpaid status at all times.
\n
ResendEmail - This method will work only in LIVE mode.
\n
ChangeApproverEmail - This method will work only in LIVE mode.
\n
Reissue - This method will work only in LIVE mode.
\n
GetUserAgreement - This method will work in TEST and LIVE mode.
\n
GetApproverList - This method will work in TEST and LIVE mode.
\n
PlaceOrder - This method will work in TEST and LIVE mode, however if the order is through a TEST mode reseller account, the order's status cannot be changed, nor can this order interact with Sectigo's supplier system.
\n
GetBalance - This method will work in TEST and LIVE mode.
\n
GetProductPrice - This method will work in TEST and LIVE mode.
\n
MarkAsRefunded - This method will work in TEST and LIVE mode.
\n
CancelOrder - This method will work only in LIVE mode.
\n
GetCertificate - This method will work in TEST and LIVE mode.
\n
GetCA - This method will work in TEST and LIVE mode.
\n
GetOrderDetails - This method will work in TEST and LIVE mode.
\n
GetCertificateCA - This method will work in TEST and LIVE mode.
\n

Order Statuses

At any given time, an order can have the following statuses appended. (Note that only the \"Unpaid\" status is given to any orders placed in TEST mode):

Unpaid : Order payment is pending
Paid : Order Payment is received
Processing : Order is submitted for processing
Cancelled : Order is Cancelled
Completed : Order is completed
Queued : An error occured while processing the order
Refunded : Order Amount is refunded
Partially paid : Order amount is partially paid

Product Codes & Properties

The following table below shows the available product codes that can be used to place new order. Please follow the information in this table when placing an order to ensure that not errors are generated when placing a new order for any of these products listed below:

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

Product Code	Product Name	Product Brand	Validation	Validity (months)	Re- Issuance	Multiple Approver	Licences	Free San	SAN Pack	SAN Individual	SAN WildCard
1020	Comodo SSL	Comodo®	DV	12-24	NO(included)	NO	UNLIMITED	NO	NO	NO	NO
1021	Comodo SSL Wildcard	Comodo®	DV	12-24	NO(included)	NO	UNLIMITED	NO	NO	NO	NO
1022	Comodo SSL MultiDomain	Comodo®	DV	12-24	YES	YES	UNLIMITED	YES(2 FREE)	NO	YES(MAX 248)	YES
1023	PositiveSSL	PositiveSSL	DV	12-24	NO(included)	NO	UNLIMITED	NO	NO	NO	NO
1024	PositiveSSL Wildcard	PositiveSSL	DV	12-24	NO(included)	NO	UNLIMITED	NO	NO	NO	NO
1025	PositiveSSL MultiDomain	PositiveSSL	DV	12-24	NO(included)	YES	UNLIMITED	YES(2 FREE)	NO	YES(MAX 248)	YES
1026	InstantSSL	InstantSSL	OV	12-24	NO(included)	NO	UNLIMITED	NO	NO	NO	NO
1027	PremiumSSL Wildcard	PremiumSSL	OV	12-24	NO(included)	NO	UNLIMITED	NO	NO	NO	NO
1028	PremiumSSL MultiDomain	PremiumSSL	OV	12-24	NO(included)	YES	UNLIMITED	YES(2 FREE)	NO	YES(MAX 248)	NO
1029	Comodo EV SSL	Comodo®	EV	12-24	NO(included)	NO	UNLIMITED	NO	NO	NO	NO
1030	Comodo EV SSL MultiDomain	Comodo®	EV	12-24	NO(included)	YES	UNLIMITED	YES(2 FREE)	NO	YES(MAX 248)	NO
1041	Comodo Free Trial SSL	Comodo®	EV	1	NO(included)	NO	UNLIMITED	NO	NO	NO	NO
1042	Trustico Single Site	Trustico®	DV	12-24	NO(included)	NO	UNLIMITED	NO	NO	NO	NO
1043	Trustico MultiDomain	Trustico®	DV	12-24	NO(included)	YES	UNLIMITED	YES(2 FREE)	NO	YES(MAX 248)	YES
1044	Trustico WildCard	Trustico®	DV	12-24	NO(included)	NO	UNLIMITED	NO	NO	NO	NO
1045	Trustico OV	Trustico®	DV	12-24	NO(included)	NO	UNLIMITED	NO	NO	NO	NO
1046	Trustico EV	Trustico®	DV	12-24	NO(included)	NO	UNLIMITED	NO	NO	NO	NO
1047	Trustico EV MultiDomain	Trustico®	DV	12-24	NO(included)	YES	UNLIMITED	YES(2 FREE)	NO	YES(MAX 248)	NO

","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","toc":[{"content":"Getting Started (Authenitcation OAuth2.0):","slug":"getting-started-authenitcation-oauth20"},{"content":"Country ISO2 Codes","slug":"country-iso2-codes"},{"content":"Error Codes","slug":"error-codes"},{"content":"TEST Mode","slug":"test-mode"},{"content":"Method Endpoint Allowances","slug":"method-endpoint-allowances"},{"content":"Order Statuses","slug":"order-statuses"},{"content":"Product Codes & Properties","slug":"product-codes-properties"}],"owner":"36259572","collectionId":"fc3101b5-af80-4582-84ea-4a3521c7a291","publishedId":"2sA3dvkCme","public":true,"customColor":{"top-bar":"FFFFFF","right-sidebar":"303030","highlight":"1F51FF"},"publishDate":"2024-08-27T06:43:57.000Z"},"item":[{"name":"Connectivity Testing APIs","item":[{"name":"Echo Text From API Server","id":"331dba63-2b3b-4921-a086-d77096dd588a","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"formdata","formdata":[{"key":"TextToEcho","value":"API responded correctly","type":"text"}]},"url":"https://api.trustico.com/v1/order/hello","description":"

POST /v1/order/hello

This endpoint allows you to send a POST request to echo back the provided text from the server.

Request Body

TextToEcho (Required): The text to be echoed back. This text can be any value.

Response

The response is in JSON format with the following schema:

{\n  \"SuccessCode\": \"\",\n  \"TextToEcho\": \"\",\n  \"APIMode\": \"\"\n}\n\n

You can test connectivity and functionality of the Trustico API using the methods in this collection. This allows verification of any server connection issues that may occur during use of any other Trustico API calls.

List of APIs in this collection:

Echo Text from Endpoint to Server

\n","_postman_id":"fff8b1d8-d4ef-48d4-83c5-57362cdab357","auth":{"type":"oauth2","oauth2":{},"isInherited":true,"source":{"_postman_id":"fc3101b5-af80-4582-84ea-4a3521c7a291","id":"fc3101b5-af80-4582-84ea-4a3521c7a291","name":"Trustico® API","type":"collection"}}},{"name":"Managing your Orders","item":[{"name":"Parse a CSR","id":"dd5dfbbe-dd4a-4272-8242-ecd82b14a1f5","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"formdata","formdata":[{"key":"CSRKey","value":"-----BEGIN CERTIFICATE REQUEST-----\nMIIDHDCCAgQCAQAwgdYxCzAJBgNVBAYTAkFVMRMwEQYDVQQIDApRdWVlbnNsYW5k\nMRMwEQYDVQQHDApHb2xkIENvYXN0MREwDwYDVQQKDAhUcnVzdGljbzEcMBoGA1UE\nCwwTU2VjdXJpdHkgRGVwYXJ0bWVudDE2MDQGA1UEAwwtdHJ1c3RpY290ZXN0ZG9t\nYWluZm9ycG9zdG1hbnNhbXBsZXJlcXVlc3QuY29tMTQwMgYJKoZIhvcNAQkBFiV1\nc2VyQHRydXN0aWNvdGVzdGRvbWFpbmZvcnBvc3RtYW4uY29tMIIBIjANBgkqhkiG\n9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwZF6Y3TtBfBAJ2wSGCFvmPS0EZUSbLmnsEfQ\nemiipfkA9fG8ts923KgmelZrUBVie47Mwd4L/Gw8c4u27d1oN4ZcuIrzDkyR63Se\nXJ4gANgtkp+IPv+yTeHEn7KkWr2jik8vX7zHzT58UAgY992jqSGHxBPXnRJOpWuY\nIWY18YWSM206eq4cWFlO1cgqDICWI6hQ7QJGIRthmmciC7GG5K6qps/zRdH9hsGD\nzPp0C0Eue59UJBBuX9JYTGXtDL6MhqhHyednrQOT38W4bo8IYRjxK6CzckdtLYWY\nu1JZE6rRgNkn/iElvYFhOEF/cS8Hwox5TLtfsyXjdFEjbGGfqQIDAQABoAAwDQYJ\nKoZIhvcNAQELBQADggEBAEpDoCalThrewMGdREKZyVWG1pWhsYitAAeY967RHmR2\nR/xJICp0pMavBotXYhA65oAfwJtkahcTU8N33DtmTvP70xE93SM0JIEY0TC176XW\nFQB6548cLcyZaPp7GZxOMxeGfW1tn/y+kd7bjZgtaogUcaBy2dnRImLWMK31a3Mn\nAmWamgNNQ3GyNrF/QsdkBUAJ2qRzEJIMWEKo6NaJfKqPOUnPKafuBMOBzMybToyk\nCtKb7/XXOkXpCuSep7GJqGGFMz4QJQi5ePqntmENmy10S0Udr+Z9vhLzYFAwHmrM\nngqn8rgW7UFv8oTeFUzC+ejYrg2ijh//0jWLSJuWyuI=\n-----END CERTIFICATE REQUEST-----","type":"text"}]},"url":"https://api.trustico.com/v1/order/parsecsr","description":"

POST /v1/order/parsecsr

This endpoint allows you to parse a certificate signing request (CSR).

A new CSR and Private Key pair can be generated via our Trustico Online CSR Generation tool.

A CSR Key that is passed on as a value to the API method endpoint must be submitted in valid PEM format. Ensure that the correct data type is set in your code to prevent errors from generating.

Request Body

CSRKey (Required): The CSR key to be parsed. Only accepts values in valid PEM format.

Response

The ParseCSR method parses a CSR string into the various CSR components (CSR Country, CSR State, CSR Locality, CSR Organization, CSR Organization Unit, CSR Domain, CSR E-Mail ) and returns them as a value.

The response will be in JSON format with the following schema:

{\n  \"type\": \"object\",\n  \"properties\": {\n    \"SuccessCode\": {\n      \"type\": \"string\"\n    },\n    \"CSRArray\": {\n      \"type\": \"object\",\n      \"properties\": {\n        \"DomainName\": {\n          \"type\": \"string\"\n        },\n        \"Country\": {\n          \"type\": \"string\"\n        },\n        \"Email\": {\n          \"type\": \"string\"\n        },\n        \"Locality\": {\n          \"type\": \"string\"\n        },\n        \"Organization\": {\n          \"type\": \"string\"\n        },\n        \"OrganizationUnit\": {\n          \"type\": \"string\"\n        },\n        \"State\": {\n          \"type\": \"string\"\n        }\n      }\n    },\n    \"APIMode\": {\n      \"type\": \"string\"\n    }\n  }\n}\n\n

The output values can be used to place a new order using the details from a CSR provided by a customer.

POST /v1/order/getbalance

The Get Balance endpoint allows users to retrieve the current balance and other financial information related to their Trustico account.

It is a good practice to call this method first before placing the order to avoid delays in processing your orders in case your account balance is low.

Request Body

Type (Required) = 1

Response

The response for this request can be represented as a JSON schema:

{\n  \"type\": \"object\",\n  \"properties\": {\n    \"SuccessCode\": {\"type\": \"string\"},\n    \"CurrentBalance\": {\"type\": \"string\"},\n    \"DueAmount\": {\"type\": \"string\"},\n    \"OverdraftLimit\": {\"type\": \"string\"},\n    \"APIMode\": {\"type\": \"string\"}\n  }\n}\n\n

POST /v1/order/getproductprice

The Get Product Price request is used to retrieve the price of a product from the Trustico API.

Request Body

ProductCode (Required) - The code of the product for which the price is to be retrieved. See the product table in the Introduction section of this document for all the valid codes.
\n
ValidityPeriod (Required) - A valid product validity period in months. Accepted values are 1, 12, and 24. See product table for possible validity periods on products.
\n
Attribute (Required) - The attribute of the product. Accepted values are N or R
\n
CountryCode (Required) - The country code for which the price is to be retrieved. See list of valid two-letter country codes in the introduction of the document.
\n

Response

The response is in JSON format and includes the following fields:

SuccessCode - The success code for the request.
\n
ProductPrice - The price of the product.
\n
SANPackPrice - The price of the SAN pack.
\n
SANIndividualPrice - The price of the individual SAN.
\n
SANIndividualWildcardPrice - The price of the individual wildcard SAN.
\n
APIMode - The mode of the API.
\n

JSON Schema

{\n  \"type\": \"object\",\n  \"properties\": {\n    \"SuccessCode\": {\"type\": \"string\"},\n    \"ProductPrice\": {\"type\": \"string\"},\n    \"SANPackPrice\": {\"type\": \"string\"},\n    \"SANIndividualPrice\": {\"type\": \"string\"},\n    \"SANIndividualWildcardPrice\": {\"type\": \"string\"},\n    \"APIMode\": {\"type\": \"string\"}\n  }\n}\n\n

POST /v1/order/placeorder

This endpoint allows you to place an order for a product with the specified details.

Request Body Parameters

ProductCode (Required): The code of the product being ordered. (See Product Codes & Properties Section)
\n
Attribute (Required): The attribute of the product. (N = New, R = renew)
\n
ValidityPeriod (Required): The validity period of the order. (1, 12, 24)
\n
ServerCount (Required): The count of servers for the order. (See Product Codes & Properties Section)
\n
Insurance (Required): The insurance details for the order. (1 = yes, 0 = no)
\n
AdminTitle (Required): The title of the admin contact. (Allowed Values: Mrs, Mr, Miss, Ms, Dr, Rev.)
\n
AdminFirstName (Required): The first name of the admin contact. (maximum of 40 characters)
\n
AdminLastName (Required): The last name of the admin contact. (maximum of 40 characters)
\n
AdminOrganization (Required): The organization of the admin contact. (maximum of 100 characters)
\n
AdminTaxID (Optional): The tax ID of the admin contact. (maximum of 40 characters)
\n
AdminRole (Required): The role of the admin contact. (Allowed Values: Business Owner, Website Owner, Chairman, President, Company Director, Managing Director, Company Executive, General Manager, Senior Manager, Executive Officer, Financial Officer, Information Officer, Marketing Officer, Sales Officer, Technology Officer, Security Officer, Web Officer, Administration Staff.)
\n
AdminEmail (Required): The email of the admin contact. (maximum of 100 characters)
\n
AdminPhoneCC (Required): The country code of the admin contact's phone number. (maximum of 6 characters)
\n
AdminPhoneN (Required): The phone number of the admin contact. (maximum of 15 characters)
\n
AdminAddress1 (Required): The address line 1 of the admin contact. (maximum of 200 characters)
\n
AdminAddress2 (Optional): The address line 1 of the admin contact. (maximum of 200 characters)
\n
AdminCity (Required): The city of the admin contact. (maximum of 40 characters)
\n
AdminState (Required): The state of the admin contact. (maximum of 40 characters)
\n
AdminPostCode (Required): The postal code of the admin contact. (maximum of 15 characters)
\n
AdminCountry (Required): The country of the admin contact. (maximum of 2 characters, see list of country codes.)
\n
TechTitle (Required): The title of the technical contact. (Allowed Values: Mrs, Mr, Miss, Ms, Dr, Rev.)
\n
TechFirstName (Required): The first name of the technical contact. (maximum of 40 characters)
\n
TechLastName (Required): The last name of the technical contact. (maximum of 40 characters)
\n
TechOrganization (Required): The organization of the technical contact. (maximum of 100 characters)
\n
TechEmail (Required): The email of the technical contact. (valid email maximum of 100 characters)
\n
TechPhoneCC (Required): The country code of the technical contact's phone number. (maximum of 6 characters)
\n
TechPhoneN (Required): The phone number of the technical contact. (maximum of 15 characters)
\n
TechAddress1 (Required): The address line 1 of the technical contact. (maximum of 200 characters)
\n
TechAddress2 (Required): The address line 1 of the technical contact. (maximum of 200 characters)
\n
TechCity (Required): The city of the technical contact. (maximum of 40 characters)
\n
TechState (Required): The state of the technical contact. (maximum of 40 characters)
\n
TechPostCode (Required): The postal code of the technical contact. (maximum of 15 characters)
\n
TechCountry (Required): The country of the technical contact. (maximum of 2 characters. See list of valid country codes)
\n
CSR (Required): The certificate signing request for the order. (valid CSR in PEM format with key length of minimum 2048 bits)
\n
DomainName (Required): The domain name for the order.
\n
SpecialInstruction (Optional): Any added notes to the order if needed. (maximum 255 Chars. Valid characters are alphanumeric, ! ” # $ % & ( ) * + , - . : ; = > < ? @ [ ] ^ _ ` { | } ~ and space)
\n
AgreedToTerms (Required): Indicates whether the terms have been agreed to. (required value = 1)
\n
ApproverEmail (Required): The email of the approver. (only valid WHOIS approver E-mail addresses are accepted : admin@example.com, administrator@example.com, webmaster@example.com, hostmaster@example.com, postmaster@example.com)
\n
TechUseReseller (Optional): Indicates whether to use reseller's details as the technical contac details. (required value = 1)
\n
FreeSAN (Optional): If the product support SAN usage, additional domains can be added here. (Multiple domains are seaprated by a comma)
\n
SANPackApprover (Optional): If a product requires individual approver E-Mail Address for each domain in SANPack then add here in the same order SANPack domains (Multiple approvers should be comma separated). You may call ‘GetApproverList’ method to get the allowed Approver E-Mail Addresses for each domain in SANPack.
\n
SANIndividual (Optional): If a product supports SANIndividual then you can put additional domains here. If a product supports Wildcard SAN then you can add it here. (Multiple domains should be comma separated). Please note that if a product supports SANPack and SANIndividual both then you must first use SANPack then for any other additional domains you can user SANIndividual.
\n
SANIndividualApprover (Optional): If a product requires individual approver E-Mail Address for each domain in SANIndividual then add here in the same order SANIndividual domains (Multiple approvers should be comma separated). You may call ‘GetApproverList’ method to get the allowed Approver E-Mail Addresses for each domain in SANIndividual.
\n
DUNSNumber (Optional): The D-U-N-S Number is a unique nine-digit identifier for businesses. Please provide this number if you are ordering OV or EV products.
\n
CouponCode (Optional): tIf you have been provided a Coupon Code, you can apply that code to the CouponCode variable. The coupon will then be applied to your order.
\n

Response

The response is in JSON format and includes the following fields:

SuccessCode (string): The success code for the order placement.
\n
OrderReference (string): The reference code for the placed order.
\n
ProductName (string): The name of the product ordered.
\n
OrderTotal (string): The total amount for the order.
\n
SupplierReference (string): The reference code of the supplier.
\n
ProcessedStatus (string): The status of the order processing.
\n
APIMode (string): The mode of the API.
\n

Example Response

{\n    \"SuccessCode\": \"\",\n    \"OrderReference\": \"\",\n    \"ProductName\": \"\",\n    \"OrderTotal\": \"\",\n    \"SupplierReference\": \"\",\n    \"ProcessedStatus\": \"\",\n    \"APIMode\": \"\"\n}\n\n

POST /v1/order/getapproverlist

This endpoint is used to retrieve the list of available approvers for a domain.

Request Body

DomainName (Required): The domain name for which the approver list is requested.

Response

SuccessCode (string): A code indicating the success status of the request.
\n
ApproverList (object):
\n
- level1 (array): List of level 1 approvers.
  \n
- level2 (object): Object containing level 2 approver emails.
  \n
  - admin@postmantrustico.com
    \n
  - administrator@postmantrustico.com
    \n
  - hostmaster@postmantrustico.com
    \n
  - webmaster@postmantrustico.com
    \n
  - postmaster@postmantrustico.com
    \n
  \n
\n
APIMode (string): The mode of the API operation.
\n

Example Response:

{\n    \"SuccessCode\": \"\",\n    \"ApproverList\": {\n        \"level1\": [],\n        \"level2\": {\n            \"admin@postmantrustico.com\": \"\",\n            \"administrator@postmantrustico.com\": \"\",\n            \"hostmaster@postmantrustico.com\": \"\",\n            \"webmaster@postmantrustico.com\": \"\",\n            \"postmaster@postmantrustico.com\": \"\"\n        }\n    },\n    \"APIMode\": \"\"\n}\n\n

POST /v1/order/getorderstatus

The Get Order Status endpoint is used to retrieve the status of a specific order.

Request Body Parameters

OrderReference (Required): The reference of the order.
\n
PrimaryDomain (Required): The primary domain of the order.
\n
PrimaryDomainApprover (Required): The approver for the primary domain.
\n

Response

The response for this request is a JSON object with the following properties:

SuccessCode (string): The success code for the order status.
\n
OrderStatus (string): The status of the order.
\n
SupplierStatus (string): The status of the supplier.
\n
APIMode (string): The mode of the API.
\n

Example

{\n    \"SuccessCode\": \"\",\n    \"OrderStatus\": \"\",\n    \"SupplierStatus\": \"\",\n    \"APIMode\": \"\"\n}\n\n

POST /v1/order/resendemail

This endpoint allows you to resend an email related to a specific order.

Request Body Parameters

OrderReference (Required): The reference for the order.
\n
EmailType (Required): The type of email to be resent.
\n

Example Response

{\n    \"SuccessCode\": 0,\n    \"ErrorMsg\": {\n        \"1006\": \"\"\n    },\n    \"APIMode\": \"\"\n}\n\n

POST /v1/order/getcertificate

This endpoint allows you to retrieve certificate order details.

Request Body

OrderReference (Required): The reference of the certificate order.

Response

SuccessCode (number): Indicates the success status of the request.
\n
ErrorMsg (object): Contains error messages, if any.
\n
APIMode (string): Indicates the mode of the API.
\n

Example Response

{\n    \"SuccessCode\": 0,\n    \"ErrorMsg\": {\n        \"1008\": \"\"\n    },\n    \"APIMode\": \"\"\n}\n\n

POST /v1/order/getca

This endpoint makes an HTTP POST request to retrieve the Certificate Authority (CA) details for a specific order.

Request Body

OrderReference (Required) - The reference of the order for which CA details are to be retrieved.

Response

An example response for this request:

{\n  \"SuccessCode\": 0,\n  \"ErrorMsg\": {\n    \"1008\": \"\"\n  },\n  \"APIMode\": \"\"\n}\n\n

POST /v1/order/getorderdetails

This endpoint allows you to retrieve the details of a specific order.

Request Body

OrderReference (Required): A reference to the order.

Response

The response for this request can be documented as a JSON schema:

{\n    \"type\": \"object\",\n    \"properties\": {\n        \"SuccessCode\": { \"type\": \"string\" },\n        \"OrderReference\": { \"type\": \"string\" },\n        \"ProductName\": { \"type\": \"string\" },\n        \"ProductValidity\": { \"type\": \"string\" },\n        \"Insurance\": { \"type\": \"string\" },\n        \"Installation\": { \"type\": \"string\" },\n        \"AdminTitle\": { \"type\": \"string\" },\n        \"AdminFirstName\": { \"type\": \"string\" },\n        \"AdminLastName\": { \"type\": \"string\" },\n        \"AdminCompanyName\": { \"type\": \"string\" },\n        \"AdminEmail\": { \"type\": \"string\" },\n        \"AdminPhone\": { \"type\": \"string\" },\n        \"AdminAddress1\": { \"type\": \"string\" },\n        \"AdminAddress2\": { \"type\": \"string\" },\n        \"AdminCity\": { \"type\": \"string\" },\n        \"AdminCounty\": { \"type\": \"string\" },\n        \"AdminCountry\": { \"type\": \"string\" },\n        \"AdminPostcode\": { \"type\": \"string\" },\n        \"AdminTaxNumber\": { \"type\": \"string\" },\n        \"AdminRole\": { \"type\": \"string\" },\n        \"AdminDUNSNumber\": { \"type\": \"string\" },\n        \"TechTitle\": { \"type\": \"string\" },\n        \"TechFirstName\": { \"type\": \"string\" },\n        \"TechLastName\": { \"type\": \"string\" },\n        \"TechCompanyName\": { \"type\": \"string\" },\n        \"TechEmail\": { \"type\": \"string\" },\n        \"TechPhone\": { \"type\": \"string\" },\n        \"TechAddress1\": { \"type\": \"string\" },\n        \"TechAddress2\": { \"type\": \"string\" },\n        \"TechCity\": { \"type\": \"string\" },\n        \"TechCounty\": { \"type\": \"string\" },\n        \"TechPostcode\": { \"type\": \"string\" },\n        \"TechCountry\": { \"type\": \"string\" },\n        \"CSRCountryCode\": { \"type\": \"string\" },\n        \"CSRState\": { \"type\": \"string\" },\n        \"CSRCity\": { \"type\": \"string\" },\n        \"CSRCompany\": { \"type\": \"string\" },\n        \"CSRDivision\": { \"type\": \"string\" },\n        \"DomainName\": { \"type\": \"string\" },\n        \"CSREmail\": { \"type\": \"string\" },\n        \"AuthenticationMethod\": { \"type\": \"string\" },\n        \"ApproverEmail\": { \"type\": \"string\" },\n        \"FreeSANList\": { \"type\": \"string\" },\n        \"SANPackList\": { \"type\": \"string\" },\n        \"SANIndividualList\": { \"type\": \"string\" },\n        \"OrderStatus\": { \"type\": \"string\" },\n        \"SupplierReference\": { \"type\": \"string\" },\n        \"SupplierStatus\": { \"type\": \"string\" },\n        \"OrderDate\": { \"type\": \"string\" },\n        \"CertificateIssueDate\": { \"type\": \"string\" },\n        \"CertificateExpiryDate\": { \"type\": \"string\" },\n        \"APIMode\": { \"type\": \"string\" }\n    }\n}\n\n

POST /v1/order/getuseragreement

This endpoint is used to retrieve user agreement information for a specific product.

Request Body

ProductCode (Required): The code of the product for which the user agreement is being requested.

Response

The response for this request is in JSON format and includes the following fields:

SuccessCode: The success code of the response.
\n
Agreement: The user agreement information.
\n
APIMode: The mode of the API response.
\n

Example Response

{\n    \"SuccessCode\": \"\",\n    \"Agreement\": \"\",\n    \"APIMode\": \"\"\n}\n\n

\n","auth":{"type":"oauth2","oauth2":{},"isInherited":true,"source":{"_postman_id":"fc3101b5-af80-4582-84ea-4a3521c7a291","id":"fc3101b5-af80-4582-84ea-4a3521c7a291","name":"Trustico® API","type":"collection"}},"urlObject":{"protocol":"https","path":["v1","order","getuseragreement"],"host":["api","trustico","com"],"query":[],"variable":[]}},"response":[{"id":"81dc0b8d-5b4d-4ecb-bfbf-ecd5a2f904f8","name":"Get Subscriber Agreement","originalRequest":{"method":"POST","header":[],"body":{"mode":"formdata","formdata":[{"key":"ProductCode","value":"1029","type":"text"}]},"url":"https://api.trustico.com/v1/order/getuseragreement"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[{"key":"x-powered-by","value":"PHP/7.1.33"},{"key":"expires","value":"Thu, 19 Nov 1981 08:52:00 GMT"},{"key":"cache-control","value":"no-store, no-cache, must-revalidate"},{"key":"pragma","value":"no-cache"},{"key":"content-type","value":"application/json; charset=UTF-8"},{"key":"strict-transport-security","value":"max-age=31536000"},{"key":"Content-Length","value":"25726"},{"key":"date","value":"Tue, 18 Jun 2024 04:48:32 GMT"},{"key":"alt-svc","value":"h3=\":443\"; ma=2592000, h3-29=\":443\"; ma=2592000, h3-Q050=\":443\"; ma=2592000, h3-Q046=\":443\"; ma=2592000, h3-Q043=\":443\"; ma=2592000, quic=\":443\"; ma=2592000; v=\"43,46\""},{"key":"via","value":"1.1 google"},{"key":"Alt-Svc","value":"h3=\":443\"; ma=2592000,h3-29=\":443\"; ma=2592000"}],"cookie":[],"responseTime":null,"body":"{\n \"SuccessCode\": \"1\",\n \"Agreement\": \"COMODO CERTIFICATE SUBSCRIBER AGREEMENT\\nIMPORTANT—PLEASE READ THIS CERTIFICATE SUBSCRIBER AGREEMENT CAREFULLY BEFORE APPLYING FOR, ACCEPTING, OR USING A COMODO CERTIFICATE. BY USING, APPLYING FOR, OR ACCEPTING A COMODO CERTIFICATE OR BY CLICKING ON “I AGREE”, YOU ACKNOWLEDGE THAT YOU HAVE READ THIS AGREEMENT, THAT YOU UNDERSTAND IT, AND THAT YOU AGREE TO ITS TERMS. IF YOU DO NOT ACCEPT THIS AGREEMENT, DO NOT APPLY FOR, ACCEPT, OR USE A COMODO CERTIFICATE AND DO NOT CLICK “I AGREE”.\\n\\t\\t\\nThis agreement is between you (“Subscriber”) and Comodo CA Limited (“Comodo”), a United Kingdom company. The agreement governs your application for and use of an SSL Certificate issued from Comodo. You and Comodo agree as follows:\\n\\t\\t\\n1. Subscription Service.\\n\\t\\t\\n1.1. Issuance. Upon Comodo’s acceptance of Subscriber’s application for a Certificate, Comodo shall attempt to validate the application information in accordance with the Comodo CPS and, for EV Certificates, the EV Guidelines. If Comodo chooses to accept the application and can validate Subscriber to Comodo’s satisfaction, Comodo shall issue the ordered Certificate(s)\\nto Subscriber. Comodo may refuse an application for any reason.\\n\\t\\t\\n1.2. Multiple Certificates. This agreement applies to multiple future Certificate request and any resulting Certificates, regardless of when the Certificate is requested or issued.\\n\\t\\t\\n1.3. License. After issuance, Comodo grants Subscriber a revocable, non-exclusive, nontransferable license to use the issued Certificates on the server hosting the domain name(s) listed in the Certificate. Comodo also grants Subscriber a non-exclusive, non-transferable, and revocable license to use Comodo’s EV AUTO-Enhancer and EV Enhancer technology in connection with Comodo EV Certificates. All rights not expressly granted herein to Subscriber are reserved to Comodo.\\n\\t\\t\\n1.4. TrustLogos. Comodo grants Subscriber a license to display purchased TrustLogos on domain(s) secured by a Comodo Certificate. When revoking a Certificate, Comodo may also revoke any TrustLogos issued to the same site. Subscriber shall not modify a TrustLogo in\\nany manner. Subscriber shall not display or use a TrustLogo 1) to represent that Comodo guarantees any non-Comodo products or services, 2) on a site that is misleading, defamatory, libelous, disparaging, obscene or otherwise objectionable to Comodo, or 3) in a\\nway that harms Comodo’s rights to its trademarks or harms Comodo’s business reputation.\\n\\t\\t\\n1.5. Fee. Subscriber shall pay all applicable fees for the Certificate before it issues. Certificate fees are provided to Subscriber during the application process. All payments are nonrefundable, except that the Certificate’s seller will refund a payment if, before twenty (20) business days after the Certificate’s issuance, the Subscriber has 1) not used the Certificate and 2) made a written request to Comodo for the Certificate’s revocation.\\n\\t\\t\\n1.6. Subscriber Obligations. Subscriber shall:\\n\\t\\t\\n(i) use the Certificates only for the purposes listed in the Comodo CPS;\\n(ii) only install an issued Certificate on the servers accessible at the domain name(s) listed in the Certificate and only use an issued Certificate for authorized business of the Subscriber;\\n\\t\\t\\n(iii) be responsible for any computer hardware, telecommunications hardware, and software necessary to use the Certificate;\\n\\t\\t\\n(iv) obtain and maintain any authorization or license necessary to use the Certificate;\\n\\t\\t\\n(v) bind every Relying Party to Comodo’s Relying Party Agreement;\\n\\t\\t\\n(vi) keep Confidential Information confidential and uncompromised, and immediately inform Comodo and request revocation of any affected Certificates if Subscriber reasonably believes that Confidential Information is likely to be disclosed or compromised;\\n\\t\\t\\n(vii) ensure that all information provided to Comodo is complete and accurate and does not include any information that would be unlawful, contrary to public interest, or otherwise likely to damage the business or reputation of Comodo if used in any way;\\n\\t\\t\\n(viii) immediately cease using a Certificate and associated Private Key 1) if the Private Key is compromised or 2) after the Certificate is expired or revoked,\\n\\t\\t\\n(ix) immediately notify Comodo of 1) any a breach of this agreement or 2) any information provided to Comodo changes, ceases to be accurate, or becomes inconsistent with the warranties made by Subscriber herein, and\\n\\t\\t\\n(x) comply with all applicable local and international laws when receiving or using a Certificate, including all export laws. Subscriber shall not export or re-export, either directly or indirectly, any Certificate to a country or entity under United Kingdom or United States restrictions. SUBSCRIBER ASSUMES ALL LIABILITY FOR ITS VIOLATION OF EXPORT LAWS.\\n\\t\\t\\n\\t\\t\\n1.7. Restrictions. Subscriber shall not:\\n\\t\\t\\n(i) impersonate or misrepresent Subscriber’s affiliation with any entity,\\n\\t\\t\\n(ii) modify, license, create a derivative work of, or transfer any Certificate (except as required to use the Certificate) or Private Key;\\n\\t\\t\\n(iii) install or use an issued Certificate until after Subscriber has reviewed and verified the Certificate data’s accuracy;\\n\\t\\t\\n(iv) upload or distribute any files or software that may damage the operation of another’s computer,\\n\\t\\t\\n(v) use the Services to 1) engage in conduct that is offensive, abusive, contrary to public morality, indecent, defamatory, obscene, or menacing, 2) breach the confidence of a third party, 3) cause Comodo or a third party distress, annoyance, denial of any service,\\ndisruption or inconvenience, 4) send or receive unsolicited bulk correspondence or 5) create a Private Key that is substantially similar to a Comodo or third party’s Private Key,\\n\\t\\t\\n(vi) make representations regarding the Service to any third party except as agreed to in writing by Comodo.\\n\\t\\t\\n\\t\\t\\n2. Warranties and Representations. Subscriber warrants that:\\n\\t\\t\\n(i) for EV Certificates, the subject named in the Certificate has exclusive control of the domain name(s) listed in the Certificate;\\n\\t\\t\\n(ii) it has full power and authority to enter into this agreement and perform its obligations hereunder;\\n\\t\\t\\n(iii) for EV Certificates, the individual accepting the Agreement is expressly authorized by Subscriber to sign the agreement for Subscriber.\\n\\t\\t\\n3. Revocation. Comodo may revoke a Certificate if Comodo believes that:\\n\\t\\t\\n(i) Subscriber requested revocation of the Certificate;\\n\\t\\t\\n(ii) Subscriber did not authorize the Certificate and has not retroactively granted authorization;\\n\\t\\t\\n(iii) Subscriber breached this Agreement;\\n\\t\\t\\n(iv) Confidential Information related to the Certificate has been disclosed or compromised;\\n\\t\\t\\n(v) the Certificate has been 1) misused, 2) used contrary to law, rule, or regulation or 3) used, directly or indirectly, for illegal or fraudulent purposes;\\n\\t\\t\\n(vi) information in the Certificate is inaccurate or misleading,\\n\\t\\t\\n(vii) for EV Certificates, Subscriber loses exclusive control over a domain name listed in the Certificate;\\n\\t\\t\\n(viii) the Certificate was not issued or used in accordance with Comodo’s CPS, industry standards, or, for EV Certificates, the EV Guidelines;\\n\\t\\t\\n(ix) Comodo 1) ceased operations or 2) is no longer allowed to issue the Certificate, and no other certificate authority has agreed to provide revocation support for the Certificate;\\n\\t\\t\\n(x) Subscriber is added as a denied party or prohibited person to a blacklist, or is operating from a prohibited destination under the laws of Comodo’s jurisdiction of operation;\\n\\t\\t\\n(xi) the Certificate was issued to publishers of malicious software;\\n\\t\\t\\n(xii) the CPS authorizes revocation of the Certificate; or\\n\\t\\t\\n(xiii) the Certificate, if not revoked, will compromise the trust status of Comodo.\\n\\t\\t\\nAfter revoking the Certificate, Comodo may, in its sole discretion, reissue the Certificate to\\nSubscriber or terminate the agreement.\\n\\t\\t\\n\\t\\t\\n4. Intellectual Property Rights.\\n\\t\\t\\n4.1. Comodo IP Rights. Comodo retains, and Subscriber shall not obtain or claim, all title, interest, and ownership rights in:\\n\\t\\t\\n(i) the Services, including issued Certificates,\\n\\t\\t\\n(ii) all copies or derivative works of the Services, regardless of who produced, requested, or suggested the copy or derivative work,\\n\\t\\t\\n(iii) all documentation and materials provided by Comodo, and\\n\\t\\t\\n(iv) all of Comodo’s copyrights, patent rights, trade secret rights and other proprietary rights.\\n\\t\\t\\n\\t\\t\\n4.2. Trademarks. Subscriber shall not use a Comodo trademark without Comodo’s written consent. Comodo consents to use of trademarks in connection with provided TrustLogos.\\n\\t\\t\\n4.3. Other Rights. EV AUTO-Enhancer™ for Windows uses Microsoft Detours Professional 2.1. Detours is Copyright 1995-2004, Microsoft Corporation. Portions of the Detours package may be covered by patents owned by Microsoft corporation. Microsoft, MS-DOS, Windows, Windows NT, Windows 2000, Windows XP, and DirectX are registered trademarks or trademarks of Microsoft Corporation in the U.S. and other countries.\\n\\t\\t\\n\\t\\t\\n5. Indemnification.\\n\\t\\t\\n5.1. Indemnification. Subscriber shall indemnify Comodo and its affiliates and their respective directors, officers, employees, and agents (each an “Indemnified Person”) against all liabilities, losses, expenses, or costs (including reasonable attorney’s fees) (collectively “Losses”) that, directly or indirectly, are based on Subscriber’s breach of this agreement, information provided by Subscriber, or Subscriber’s or its customers’ infringement on the rights of a third party.\\n\\t\\t\\n5.2. Indemnification Procedure. Comodo shall notify Subscriber promptly of any demand for indemnification. However, Comodo’s failure to notify will not relieve Subscriber from its indemnification obligations except to the extent that the failure to provide timely notice materially prejudices Subscriber. Subscriber may assume the defense of any action, suit, or proceeding giving rise to an indemnification obligation unless assuming the defense would result in potential conflicting interests as determined by the Indemnified Person in good faith. Subscriber may not settle any claim, action, suit or proceeding related to this agreement\\nunless the settlement also includes an unconditional release of all Indemnified Persons from liability.\\n\\t\\t\\n5.3. Additional Liability. The indemnification obligations of Subscriber are not Comodo’s sole remedy for Subscriber’s breach and are in addition to any other remedies Comodo may have against Subscriber under this agreement. Subscriber’s indemnification obligations survive the termination of this agreement.\\n\\t\\t\\n\\t\\t\\n6. Term and Termination.\\n\\t\\t\\n6.1. Term. Unless otherwise terminated as allowed herein, this agreement is effective upon Subscriber’s acceptance and lasts for as long as a Certificate issued under the agreement is valid.\\n\\t\\t\\n6.2. Termination. Either party may terminate the agreement with 20 business days notice for convenience. Comodo may terminate this agreement immediately without notice if\\n\\t\\t\\n(i) Subscriber materially breaches this agreement,\\n\\t\\t\\n(ii) if Comodo revokes a Certificate as allowed herein,\\n\\t\\t\\n(iii) if Comodo rejects Subscriber’s Certificate application,\\n\\t\\t\\n(iv) Comodo cannot satisfactorily validate Subscriber in accordance with section 1.1, or\\n\\t\\t\\n(v) if industry standards change in a way that affects the validity of the Certificates ordered by Subscriber.\\n\\t\\t\\n6.3. Events Upon Termination. After termination, Comodo may revoke any other Certificate’s issued to Subscriber without further notice. Subscriber shall pay any amounts still owed for the Certificates. Comodo is not obligated to refund any payment made by Subscriber upon termination of this Agreement.\\n\\t\\t\\n\\t\\t\\n7. Disclaimers and Limitation of Liability.\\n\\t\\t\\n7.1. Relying Party Warranties. Subscriber acknowledges that the Relying Party Warranty is only for the benefit of Relying Parties. Subscriber does not have rights under the warranty, including any right to enforce the terms of the warranty or make a claim under the warranty.\\n\\t\\t\\n7.2. Exclusion of Warranties. THE SERVICES ARE PROVIDED “AS IS” AND “AS AVAILABLE”. COMODO EXPRESSLY DISCLAIMS ALL IMPLIED AND EXPRESS WARRANTIES IN THE SERVICES. THIS DISCLAIMER INCLUDES ALL WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT AND IS EFFECTIVE TO THE MAXIMUM EXTENT ALLOWED BY LAW. COMODO DOES NOT GUARANTEE THAT 1) THE SERVICES WILL MEET SUBSCRIBER’S REQUIREMENTS OR EXPECTATIONS OR 2) THAT ACCESS TO THE SERVICES WILL BE UNINTERRUPTED, TIMELY, SECURE, OR ERROR-FREE.\\n\\t\\t\\n7.3. Limitation on Liability. SUBJECT TO SECTION 7.4, THE TOTAL LIABILITY OF COMODO AND ITS AFFILIATES, AND EACH OF THEIR OFFICERS, DIRECTORS, PARTNERS, EMPLOYEES, AND CONTRACTORS, RESULTING FROM OR CONNECTED TO THIS AGREEMENT IS LIMITED TO THE AMOUNT PAID BY SUBSCRIBER FOR THE SERVICES GIVING RISE TO THE LIABILITY. SUBSCRIBER WAIVES ALL LIABILITY FOR ANY SPECIAL, INDIRECT, INCIDENTAL OR CONSEQUENTIAL DAMAGES. THIS WAIVER INCLUDES ALL DAMAGES FOR LOST PROFITS, REVENUE, USE, OR DATA AND APPLIES EVEN IF COMODO IS AWARE OF THE POSSIBILITY OF SUCH DAMAGES.\\n\\t\\t\\nThese limitations apply to the maximum extent permitted by law regardless of\\n1) the reason for or nature of the liability, including tort claims,\\n2) the number of any claims,\\n3) the extent or nature of the damages, and\\n4) whether any other provisions of this agreement have been breached or proven ineffective.\\n\\t\\t\\n\\t\\t\\n7.4. Exception. Nothing in this agreement excludes or limits the liability of either party for death or personal injury resulting from the negligence of that party or for any statements made fraudulently by either party.\\n\\t\\t\\n8. Remedy.\\n\\t\\t\\n8.1. Injunctive Relief. Subscriber acknowledges that its breach of this agreement will result in irreparable harm to Comodo that cannot adequately be redressed by compensatory damages. Accordingly, in addition to any other legal remedies which may be available, Comodo may seek and obtain an injunctive order against a breach or threatened breach of the agreement by Subscriber.\\n\\t\\t\\n8.2. Limitation on Actions. Except for actions and claims related to a party’s indemnification and confidentiality obligations, all claims and actions arising from this agreement must be brought within one (1) year from the date when the cause of action occurred.\\n8.3. Remedy. Subscriber’s sole remedy for a defect in the Services is to have Comodo use reasonable efforts to correct the defect.\\n\\t\\t\\n Comodo is not obligated to correct a defect if (i) the Service was misused, damaged, or modified, (ii) Subscriber did not immediately report the defect to Comodo, or (iii) Subscriber breached any provision of this agreement.\\n\\t\\t\\n9. Confidentiality. Except as allowed herein, a party (“Receiving Party”) shall not use or disclose any Confidential Information provided by the other party (the “Disclosing Party”) other than for the purpose of performing its obligations under this agreement.\\n\\t\\t\\nThe Receiving Party shall take reasonable measures to prevent unauthorized disclosure and shall ensure that any person receiving Confidential Information complies with the restrictions in this section. The Receiving Party may disclose Confidential Information if the information:\\n\\t\\t\\n(i) is already possessed by the Receiving Party before receipt from the Disclosing Party;\\n\\t\\t\\n(ii) is or becomes public domain without fault of the Receiving Party;\\n\\t\\t\\n(iii) is received by the Receiving Party from a third party who is not under an obligation of confidentiality or a restriction on the use and disclosure of the information,\\n\\t\\t\\n(iv) is disclosed in response to the requirements of a law, governmental order, regulation, or legal process and the Receiving Party first gives prior notice to the Disclosing Party of the requirement to disclose the information, or\\n\\t\\t\\n(v) is disclosed under operation of law to the public without a duty of confidentiality. A party asserting one of the exceptions to Confidential Information above shall prove the assertion using verifiable documentary evidence. The restrictions contained in this section apply for the duration of the agreement plus five years after its termination.\\n\\t\\t\\n\\t\\t\\n10. Privacy.\\n\\t\\t\\n(i) Comodo shall follow the privacy policy posted on its website when receiving and using information from the Subscriber. Comodo may amend the privacy policy at any time by posting the amended privacy policy on its website. Subject to Section 10(ii), Comodo shall use reasonable efforts in protecting Subscriber’s information. Subscriber acknowledges that risks remain that are beyond Comodo’s reasonable control and waives all liability of Comodo for these risks.\\n\\t\\t\\n(ii) Subscriber consents to 1) Comodo disclosing Subscriber’s information publicly by embedding the information in issued Certificates and 2) Comodo disclosing and transferring Subscriber’s information to third parties located outside of the European Union as necessary to validate and issue Certificates.\\n\\t\\t\\n(iii) Subscriber may opt-out of having information used for purposes not directly related to the Services by emailing a clear notice to optout@comodo.com. By clicking “I AGREE”, Subscriber affirmatively consents to receiving Comodo’s and its affiliates marketing material.\\n\\t\\t\\n\\t\\t\\n11. Miscellaneous.\\n\\t\\t\\n11.1. Force Majeure and Internet Frailties. Other than for payment obligations by Subscriber, neither party will be liable for a delay or failure to perform an obligation to the extent that the delay or failure is caused by an occurrence beyond the party's reasonable control. Each party acknowledges that the operation of the Internet is beyond the other party’s reasonable control, and neither party will be liable for a delay or failure caused by an interruption or failure of telecommunication or digital transmission links, Internet slow-downs or failures, or other such transmission failure.\\n\\t\\t\\n11.2. Notices. You shall send all notices to Comodo by first class mail in English writing, with return receipt requested, to Comodo CA Limited, 26 Office Village, 3rd Floor, Exchange Quay, Trafford Road, Salford, Manchester M5 3EQ, United Kingdom. Comodo shall send all notices to Subscriber’s contact information listed on its Certificate application. Comodo may send notices by mail, email, or facsimile.\\n\\t\\t\\n11.3. Entire Agreement. This agreement and all documents referred to herein constitutes the entire agreement between the parties, superseding all other agreements that may exist with respect to the subject matter. Section headings are for reference and convenience only and are not part of the interpretation of this agreement.\\n\\t\\t\\n11.4. Amendments. Comodo may amend this agreement, the CPS, the Relying Party Agreement, the Relying Party Warranty, its website, and any documents listed in its Repository at any time by posting either the amendment or the amended document in the Repository.\\nSubscriber shall periodically review the Repository to be aware of any changes. Subscriber may terminate the agreement if Subscriber does not agree to the amendment. Subscriber’s continued use of the Services after an amendment is posted constitutes Subscriber’s\\nacceptance of the amendment.\\n\\t\\t\\n11.5. Waiver. A party’s failure to enforce a provision of this agreement will not waive the party’s right to enforce the same provision later or right to enforce any other provision of this agreement. To be effective, all waivers must be both in writing and signed by the party benefiting form the waived provision.\\n\\t\\t\\n11.6. Assignment. Subscriber may not assign any of its rights or obligations under this agreement without the prior written consent of Comodo. Any transfer without consent is void. Comodo may assign its rights and obligations without Subscriber’s consent.\\n\\t\\t\\n11.7. Governing Law and Venue. The laws of England and Wales govern the interpretation, construction, and enforcement of this agreement and all proceedings arising out of it, including tort claims, without regard to any conflicts of law principles. All proceedings or legal action arising from this agreement must be commenced in the courts of England and Wales. Both parties agree to the exclusive venue and jurisdiction of these courts.\\n\\t\\t\\n11.8. Severability. Any provision determined invalid or unenforceable by rule of law will be reformed to the minimum extent necessary to make the provision valid and enforceable. If reformation is not possible, the provision is deemed omitted and the balance of the\\nagreement remains valid and enforceable.\\n\\t\\t\\n11.9. Survival. All provisions of the agreement related to confidentiality, proprietary rights, indemnification, and limitations of liability survive the termination of the agreement.\\n\\t\\t\\n11.10. Rights of Third Parties. The Certificate Beneficiaries are express third party beneficiaries of Subscriber’s obligations and warranties in this agreement.\\n\\t\\t\\n\\t\\t\\n12. Definitions.\\n\\t\\t\\n12.1. “Certificate” means a digitally signed electronic data file issued by Comodo to a person or entity seeking to conduct business over a communications network which contains the identity of the person authorized to use the Digital Signature, a copy of their Public Key, a serial number, a time period during which the data file may be used, and a Digital Signature issued by Comodo.\\n\\t\\t\\n12.2. “CPS” refers to the documents explaining Comodo’s polices and procedures when operating its PKI infrastructure.\\n\\t\\t\\n12.3. “Confidential Information” means all material, data, systems, technical operations, and other information concerning Comodo’s business operations that is not known to the general public, including all information about the Certificate issuance services (such as all Private Keys, personal identification numbers and passwords).\\n\\t\\t\\n12.4. “Certificate Beneficiaries” means the Subscriber, the Subject named in the Certificate, any third parties with whom Comodo has entered into a contract for inclusion of its root certificate, and all Relying Parties that actually rely on such Certificate during the period when it is valid.\\n\\t\\t\\n12.5. “Digital Signature” means an encrypted electronic data file which is attached to or logically associated with other electronic data and which identifies and is uniquely linked to the signatory of the electronic data, is created using the signatory's Private Key and is linked in a way so as to make any subsequent changes to the electronic data detectable.\\n\\t\\t\\n12.6. “EV AUTO-Enhancer” means Comodo’s patent-pending process and software to enable EV functionality on web browsing computers using a modified Apache configuration file or the Comodo developed IIS plug-in.\\n\\t\\t\\n12.7. “EV Certificate” means a Certificate signed to Comodo’s EV root certificate that is designed for use with an SSL v3 or TLS v 1.0 enabled web browse and that complies with the EV Guidelines.\\n\\t\\t\\n12.8. “EV Enhancer” means the process and software used by Comodo to enable EV functionality on web browsing computers by pointing the web browser on the web browsing computer to a beacon website designed to download and install a new EV root certificate.\\n\\t\\t\\n12.9. “EV Guidelines” refers to the official, adopted guidelines governing EV Certificates as established by the CA/Browser Forum that are available online at http://www.cabforum.org.\\n\\t\\t\\n12.10. “Private Key” means a confidential encrypted electronic data file designed to interface with a Public Key using the same encryption algorithm and which may be used to create Digital Signatures, and decrypt files or messages which have been encrypted with a Public Key.\\n\\t\\t\\n12.11. “Public Key” means a publicly available encrypted electronic data file designed to interface with a Private Key using the same encryption algorithm and which may be used to verify Digital Signatures and encrypt files or messages.\\n\\t\\t\\n12.12. “Relying Party” means an entity that acts in reliance on a Certificate or a Digital Signature.\\n\\t\\t\\n12.13. “Relying Party Agreement” refers to an agreement located on the Comodo Repository that governs a Relying Party’s use of the Certificate when transacting business with the Subscriber’s website.\\n\\t\\t\\n12.14. “Relying Party Warranty” refers to a warranty offered by Comodo to a Relying Party under the terms and conditions found in the Comodo Relying Party Agreement in connection with the Relying Party’s use of a Certificate.\\n\\t\\t\\n12.15. “Repository” means a publicly available collection of information and databases relating to Comodo’s Certificate practices and which is available at http://www.comodo.com/repository.\\n\\t\\t\\n12.16. “Services” means the Certificates ordered hereunder along with any related TrustLogos, software, and documentation.\\n\\t\\t\\n12.17. “TrustLogo” means a logo provided by Comodo for use on a Subscriber’s site in connection with an issued Certificate.\\n\\t\\t\\n\\t\\t\\nACCEPTANCE\\n\\t\\t\\nBY CLICKING “I AGREE”, YOU ACKNOWLEDGE THAT YOU HAVE READ AND UNDERSTAND THIS AGREEMENT AND THAT YOU AGREE TO COMPLY WITH ITS TERMS. DO NOT CLICK “I AGREE” IF YOU DO NOT ACCEPT THIS AGREEMENT. \",\n \"APIMode\": \"Your API is working in TEST mode\"\n}"}],"_postman_id":"af89dc83-a24b-41e8-9095-cd1a0c454c02"},{"name":"Reissue Order","id":"d7088b85-c081-4b6e-9c37-b1cbda87f46d","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"formdata","formdata":[{"key":"OrderReference","value":"11669682","type":"text"}]},"url":"https://api.trustico.com/v1/order/reissueorder","description":"

POST /v1/order/reissueorder

This endpoint allows you to reissue an order. The request should be sent as an HTTP POST to the specified URL.

Request Body

OrderReference (Required): This parameter specifies the order reference.

Response

Upon successful execution, the response will include:

SuccessCode (number): A code indicating the success of the operation.
\n
ErrorMsg (object): An object containing any error messages, if applicable.
\n
APIMode (string): The mode of the API operation.
\n

Example response:

{\n    \"SuccessCode\": 0,\n    \"ErrorMsg\": {\n        \"1006\": \"\"\n    },\n    \"APIMode\": \"\"\n}\n\n

POST /v1/order/cancelorder

This endpoint is used to cancel an order. It makes an HTTP POST request to the specified URL.

Request Body

OrderReference (Required): The reference of the order to be cancelled.

Response

Status: 200
\n
Content-Type: application/json
\n
SuccessCode (integer): Indicates the success status of the cancellation.
\n
ErrorMsg (object): Provides error messages, if any, with corresponding error codes.
\n
APIMode (string): Indicates the mode of the API.
\n

Example Response

{\n    \"SuccessCode\": 0,\n    \"ErrorMsg\": {\n        \"1006\": \"\"\n    },\n    \"APIMode\": \"\"\n}\n\n

POST /v1/order/markasrefunded

This API endpoint is used to mark an order as refunded. It is an HTTP POST request to the specified URL.

Request Body

form-data
\n
- OrderReference: (Required) - The reference of the order to be marked as refunded.
\n

Response

Upon successful execution, the response will contain the following details:

{\n  \"SuccessCode\": 0,\n  \"ErrorMsg\": {\n    \"1003\": \"\"\n  }\n}\n\n

All API endpoints regarding order management can be found in this section below. This includes placing and cancelling orders, reissuing, resending certificate to customerse, retreiving order details etc.

List of APIs in this collection:

Parse a CSR
\n
Get Reseller Balance
\n
Get Reseller Product Pricing
\n
Place New Order
\n
Get an Existing Order's Valid Approver E-Mail List
\n
Get an Existing Order's Status
\n
Resend an Approver / Fulfillment E-Mail
\n
Get Certificate of a Completed Order
\n
Get Intermediates of a Completed Order
\n
Get Details of an Exisiting Order
\n
Get Subscriber Agreement for a Valid Product
\n
Reissue a Valid Order
\n
Cancel an Order
\n
Mark an Order as Refunded
\n

\n","_postman_id":"9454ecd5-d19e-4181-9c99-35d66c7e4c4a","auth":{"type":"oauth2","oauth2":{},"isInherited":true,"source":{"_postman_id":"fc3101b5-af80-4582-84ea-4a3521c7a291","id":"fc3101b5-af80-4582-84ea-4a3521c7a291","name":"Trustico® API","type":"collection"}}}],"auth":{"type":"oauth2","oauth2":{}},"event":[{"listen":"prerequest","script":{"id":"146c7d40-a899-4ce2-a34d-ec4b49ae1512","type":"text/javascript","packages":{},"exec":[""]}},{"listen":"test","script":{"id":"fe12d317-ba41-4b60-bcdb-de6b15f9576c","type":"text/javascript","packages":{},"exec":[""]}}]}