Mark Certificates API Requests

<UserName>

*Required

Input your user ID this is same for your GCC User Interface

<Password>

Input your password this is same for your GCC User Interface

<ProductCode>

See section 2 and basis the same you can add Product Code like MMC, VMC, GMC, CMC

<OrderKind>

New / Renewal: indicates the order type

<Licenses>

1 : as this Retail certificates so this depicts the license number as 1.

<ValidityPeriod><Months></Months></ValidityPeriod>

The number of months that a certificate will be valid for. Set it to 12.

<SvgLogoBase64>

For all mark types. Provide the base64 file of the SVG you want to use in your certificate.

<MarkLicenseExpiryDate>

Optional

Please select input the date of the license expiry of your Trademark. If you are not sure, then please leave this blank. Our vetting team will find this out for you.

<TrademarkIdentifier>

Optional

For VMC and MMC only. Enter the trademark license identifier/unique license number.

<TrademarkCountryOrRegionName>

*Required

For VMC and MMC only. Enter the Two Digit Country code.

<TrademarkOfficeName>

*Required

For VMC and MMC only. Select the trademark office where your trademark logo is registered.

<CommonNameSAN>

*Required

For alL Mark Type. Enter your domain name like example.com

<Organization>

*Required

Enter the organization name.

<Locality>

Optional

Enter the locality name

<StateOrProvince>

Optional

<Country>

Enter the Two Digit Country code.

<ContactInfo>
<FirstName></FirstName> <FirstNameNative</FirstNameNative>
<LastName></LastName> <LastNameNative</LastNameNative>
<Phone></Phone>
<Email></Email> <OrganizationNameNative>
</OrganizationNameNative>
</ContactInfo>

*Required
1. <FirstName>
2. <LastName>
3. <Phone>
4. <Email>

Primary Contact Information of for a certificate request

<Coupon>

Optional

Coupons can be used for payment

<Campaign>

Optional

Campaign can be used for payment

<StatuteCitation>

Optional

For GMC only. If you have some reference link that you can provide for the reference that can help us identify the legal status of the logo being used i.e. some legal statue reference or article. If not sure, leave it blank.

<StatuteStateOrProvinceName>

Optional

For GMC only. Enter the state or province name

<StatuteCountryName>

Optional

For GMC only. Enter the country name

<PriorUseMarkSourceURL>

Optional

For CMC only. If you are sure of the archive URL of the logo display from past 12 months then please enter it here.

<SecondContactInfo>

<FirstName></FirstName>

<LastName></LastName>
       <Email></Email>
   </SecondContactInfo>

Optional

Secondary contact for this order.

<SANEntries> <SANEntry>
<SANOptionType>
      </SANOptionType>
<SubjectAltName>
</SubjectAltName>
</SANEntry>
</SANEntries>

Optional

<SANEntries> parameters should be set to what the SubjectAltName(s) will be after the change. GlobalSign will do a manual review of the change for Mark Certificates. New certificates with updated SANs will be issued and queriable after vetting has been completed.

<OrganizationInfoEV>
<BusinessAssumedName>?

</BusinessAssumedName>
<CreditAgency>?
</CreditAgency>
<OrganizationCode>?
</OrganizationCode>

<OrganizationNameNative>
</OrganizationNameNative>

<BusinessCategoryCode>?

</BusinessCategoryCode>
<OrganizationAddress>
<AddressLine1>?
</AddressLine1>
<AddressLine1Native>?
</AddressLine1Native>
<AddressLine2>?
</AddressLine2>
<AddressLine2Native>?
</AddressLine2Native>
<AddressLine3>?
</AddressLine3>
<City>?</City>
<CityNative>?
</CityNative>
<Region>?
</Region>
<RegionNative>?
</RegionNative>
<PostalCode>?
</PostalCode>
<Country>?
</Country>
<Phone>?
</Phone>
<Fax>?
</Fax>
</OrganizationAddress>
</OrganizationInfoEV>

<ApproverInfo>
<FirstName>?</FirstName>
<FirstNameNative>
</FirstNameNative>
<LastName>?</LastName>
<LastNameNative>?
</LastNameNative>
<Function>?</Function>
<OrganizationName>
</OrganizationName>
<OrganizationNameNative>
</OrganizationNameNative>
<OrganizationUnitNative>
</OrganizationUnitNative>
<Phone>?</Phone>
<Email>?</Email>
</ApproverInfo>

Mandatory
1. <OrganizationName>
2. <FirstName>
3. <LastName>
4. <Phone>
5. <Email>

A Certificate Approver is a natural person who is Applicant, employed by Applicant, or an authorized agent who has express authority to represent Applicant to (i) act as a Certificate Requester and to authorize other employees or third parties to act as a Certificate Requester, and (ii) to approve Certificate Requests submitted by other Certificate Requesters.

<AuthorizedSignerInfo>
<OrganizationName>?
</OrganizationName>
<OrganizationNameNative>
</OrganizationNameNative>
<FirstName>?</FirstName>
<FirstNameNative>
</FirstNameNative>
<LastName>?</LastName>
<LastNameNative>
</LastNameNative>
<Function>?</Function>
<OrganizationUnitNative>
</OrganizationUnitNative>
<Phone>?</Phone>
<Email>?</Email>
</AuthorizedSignerInfo>

Mandatory
1. <OrganizationName>
2. <FirstName>
3. <LastName>
4. <Phone>
5. <Email>

A Contract Signer is a natural person who is Applicant, employed by Applicant, or an authorized agent who has express authority to represent Applicant who has authority on behalf of Applicant to sign Subscriber Agreements on behalf of Applicant.

<JurisdictionInfo>
<JurisdictionCountry>
</JurisdictionCountry>
<JurisdictionState>
</JurisdictionState>
<JurisdictionLocality>
</JurisdictionLocality>
<IncorporationAgency
RegistrationNumber>
</IncorporationAgency
RegistrationNumber>
</JurisdictionInfo>

Mandatory
1. <JurisdictionCountry>

Jurisdiction of Incorporation Details.

<UserName>

Input your user ID this is same for your GCC User Interface

<Password>

Input your password this is same for your GCC User Interface

<TargetOrderID>

This is certificate order number for which your want to add/change new SAN

<SANOptionType>

Keep it as 7 : this is let system know that you are request change SAN option

<SubjectAltName>

 In API request please add all additional SANs that you need to be in certificate, even the one that are existing now in the certificate if you want that domain as well. Otherwise, you can specify the new one also. All added primary commonname/san need not be added only additional SANs should be specified again.

<OrderID>

Once your request is approved, this will provide the ID for the new certificate order.

<SuccessCode>

0 means your request has been accepted for processing. For detailed information visit XML Definition section

<UserName>

Input your user ID this is same for your GCC User Interface

<Password>

Input your password this is same for your GCC User Interface

<ProductCode>

See section 2 and basis the same you can add Product Code like MMC, VMC, GMC, CMC

<AgreementVersion>

This depicts the current version of the Service Agreement

<AgreementText>

This field presents the complete Service Agreement text.

<SuccessCode>

0 means its successful. For detailed information please visit XML Definition section

<UserName>

Input your user ID this is same for your GCC User Interface

<Password>

Input your password this is same for your GCC User Interface

<OrderID>

Please enter the order ID for the PEM file you wish to receive.

<MCHostingPEM>

This field will return the PEM Encoded Certificate chain file.

<AgreementVersion>

This depicts the current version of the Service Agreement

<SuccessCode>

0 means its successful. For more information please visit XML Definition section

<UserName>

Input your user ID this is same for your GCC User Interface

<Password>

Input your password this is same for your GCC User Interface

<OrderID>

Please enter the order ID for the PEM file you wish to receive.

<ReturnFulfillment>

TRUE / FALSE : Use TRUE in case you wish to receive the PEM End Entity file

IF This is kept as empty then you will not receive the PEM File so we request you to keep this as TRUE

<ReturnCACerts>

TRUE / FALSE : Use TRUE in case you wish to receive the PEM Encoded chain file which contains both Intermediate Certificate Authority (ICA) and Root. This is the file that you can place directly on your public facing server

Use FALSE , in case you wish to just receive the End Entity PEM file

<SuccessCode>

0 means your request has been accepted and is successful

<Timestamp>

Time when the request tis processed

<ProductCode>

This will return the code of the Mark Certificate : Please have a look at section 2 to understand this.

<OrderKind>

New  / Renewal: indicates the order type

<Licenses>

1 : as this Retail certificates so this depicts the license number as 1.

<DomainName>

Depicts the primary domain added in Mark Certificate

<OrderDate>

The date on which this order was initiated to be placed

<OrderCompleteDate>

The date on which this order is completed.

<OrderStatus>

4 : Please look at XML Fields Definitions :-> Data Definitions

<Price>

Certificate price

<Currency>

Currency for your Order Price

<ValidityPeriod>

To know for how many months is this certificate valid

<OrganizationInfo>

This structure will return your organization details as parsed in the certificates.

<RequestorInfo>

 A Certificate Requester is a natural person who is Applicant, employed by Applicant, or an authorized agent who has express authority to represent Applicant or a third party (such as an ISP or hosting company) that completes and submits a Certificate Request on behalf of Applicant.

<ApproverInfo>

 A Certificate Approver is a natural person who is Applicant, employed by Applicant, or an authorized agent who has express authority to represent Applicant to (i) act as a Certificate Requester and to authorize other employees or third parties to act as a Certificate Requester, and (ii) to approve Certificate Requests submitted by other Certificate Requesters.

<AuthorizedSignerInfo>

A Contract Signer is a natural person who is Applicant, employed by Applicant, or an authorized agent who has express authority to represent Applicant who has authority on behalf of Applicant to sign Subscriber Agreements on behalf of Applicant.

<JurisdictionInfo>

Jurisdiction of Incorporation Details.

<ContactInfo>

Primary Contact Information of for a certificate request.

<CertificateInfo>

This structure contains information stored related to the certificate in various Query operations.

<CACertificates>

This is the list of CA certificates associated with the server / mark certificate. If present, there must be one or more <CACertificate> fields in this structure. The Root certificate will always be present in this structure, and there may be one or more intermediate CA certificates.

<CACertType>

ROOT/INTER Type of PEM file

<CACert>

ROOT/INTER Certificate PEM file

<X509Cert>

End Entity Certificate PEM file

<OriginalCSR>

In Mark Certificates, user do not have to provide the CSR; but our system automatically creates one for the user in the backend: this displays the CSR created

<ModificationEvents>

See the Data Definitions section in the XML Fields Definitions

<UserName>

Input your user ID this is same for your GCC User Interface

<Password>

Input your password this is same for your GCC User Interface

<OrderID>

Please enter the order ID for the PEM file you wish to receive.

<RevokeReason>

0 : unspecified

3 : affiliationChanged

4 : superseded

5 : cessationOfOperation

<SuccessCode>

0 means your request has been accepted and is successful