{"info":{"_postman_id":"020cb87e-acec-4379-b2ae-635c8018a3eb","name":"emCA REST API V4.3.1","description":"<html><head></head><body><p>emCA provides an open API (Application Programming Interface) for integrating signature modules with third party applications, portals, or websites, and to customize as per your needs. With the emCA REST API, you can extract Recruit data in JSON format and develop new applications or integrate with your existing business applications. As the emCA API is independent of programming languages, you can develop applications in any programming language (Java, .Net etc.).</p>\n</body></html>","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","toc":[],"owner":"40123569","collectionId":"020cb87e-acec-4379-b2ae-635c8018a3eb","publishedId":"2sB34imfqj","public":true,"customColor":{"top-bar":"FFFFFF","right-sidebar":"303030","highlight":"FF6C37"},"publishDate":"2025-07-18T06:03:11.000Z"},"item":[{"name":"CA Management","item":[{"name":"getKeyProfiles","id":"14fde21d-6d82-4162-88f6-408b107c8b3a","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"}],"url":"https://appemca.emudhra.com/emCAServices431/rest/get-keyProfiles/certinext","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The \"getKeyProfiles\" API is used to retrieve the list of available key profiles that have been created in the CA system.</p>\n<p><strong>URL</strong></p>\n<p><a href=\"https://appemca.emudhra.com/emCAServices431/rest/get-keyProfiles/certinext\">https://appemca.emudhra.com/emCAServices431/rest/get-keyProfiles</a><a href=\"https://appemca.emudhra.com/emCAServices/rest/getCAs/924e0d30-8cea-4bf4-be77-4b0e160dbaf9\">/{appCode}</a></p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<p><strong>Table no 1</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>appCode*</td>\n<td>String</td>\n<td><strong>appCode</strong> is used as part of External Application Registration at emCA and needs to be passed in the path variable.  <br />  <br />Ex :- “MyApp”</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","get-keyProfiles","certinext"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"14fde21d-6d82-4162-88f6-408b107c8b3a"},{"name":"createCA","id":"a23dbdd0-3c64-4990-93a2-ec78d3a05593","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"}],"body":{"mode":"raw","raw":"{\r\n    \"meta\": {\r\n        \"ver\": \"1.0\",\r\n        \"ts\": \"2024-06-04T11:40:15+05:30\",\r\n        \"txn\": \"3473283142736543345\",\r\n        \"appCode\": \"certinext\",\r\n        \"authKey\": \"702e3cf0a395063f654cbce7b71d0d647fc8816eabeb353170caaab3b3146dd4\"\r\n    },\r\n    \"certificateRequestDetails\": {\r\n        \"caType\": \"subCA\",\r\n        \"parentCAID\": \"3\",\r\n        \"validityCriteria\": \"d\",\r\n        \"validityValue\": \"3000\",\r\n        \"keyAlgorithm\": \"RSA2048\",\r\n        \"signingAlgorithm\": \"SHA256WithRSA\",\r\n        \"caSubjectAttributes\": [\r\n            {\r\n                \"dataType\": \"PrintableString\",\r\n                \"oid\": \"2.5.4.3\",\r\n                \"value\": \"SUB TEST 2024\"\r\n            }\r\n        ],\r\n        \"caExtensions\": {\r\n            \"basicConstraints\": {\r\n                \"isEnabled\": \"1\",\r\n                \"isCritical\": \"1\",\r\n                \"type\": \"CA\",\r\n                \"pathLength\": \"0\",\r\n                \"sortOrder\": \"2\"\r\n            },\r\n            \"authInfoAccess\": {\r\n                \"isEnabled\": \"0\",\r\n                \"isCritical\": \"0\",\r\n                \"ocspURL\": \"\",\r\n                \"crtURL\": \"\",\r\n                \"sortOrder\": \"1\"\r\n            },\r\n            \"crlDistribution\": {\r\n                \"isEnabled\": \"0\",\r\n                \"isCritical\": \"0\",\r\n                \"crlURL\": \"http://www.example.com/repository/crls/test.crl\",\r\n                \"sortOrder\": \"4\"\r\n            },\r\n            \"keyUsageAttributes\": {\r\n                \"encipherOnly\": \"0\",\r\n                \"isEnabled\": \"1\",\r\n                \"isCritical\": \"1\",\r\n                \"nonRepudiation\": \"0\",\r\n                \"digitalSignature\": \"0\",\r\n                \"keyEncipherment\": \"0\",\r\n                \"dataEncipherment\": \"0\",\r\n                \"keyAgreement\": \"0\",\r\n                \"keyCertSign\": \"1\",\r\n                \"crlSign\": \"1\",\r\n                \"decipherOnly\": \"0\",\r\n                \"sortOrder\": \"5\"\r\n            },\r\n            \"extendedKeyUsageAttributes\": {\r\n                \"isEnabled\": \"0\",\r\n                \"isCritical\": \"0\",\r\n                \"serverAuthentication\": \"0\",\r\n                \"clientAuthentication\": \"0\",\r\n                \"codeSigning\": \"0\",\r\n                \"emailProtection\": \"0\",\r\n                \"timeStamping\": \"0\",\r\n                \"ocspSigning\": \"0\",\r\n                \"msftDocumentSigning\": \"0\",\r\n                \"smartCardLogon\": \"0\",\r\n                \"adobeCertifiedDocumentSigning\": \"0\",\r\n                \"encryptionFileSystem\": \"0\",\r\n                \"sortOrder\": \"6\"\r\n            },\r\n            \"subjectKeyIdentifier\": {\r\n                \"isEnabled\": \"1\",\r\n                \"isCritical\": \"0\",\r\n                \"sortOrder\": \"7\"\r\n            },\r\n            \"authorityKeyIdentifier\": {\r\n                \"isEnabled\": \"1\",\r\n                \"isCritical\": \"0\",\r\n                \"sortOrder\": \"8\"\r\n            }\r\n        }\r\n    }\r\n}","options":{"raw":{"language":"json"}}},"url":"https://appemca.emudhra.com/emCAServices431/rest/create/ca","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The \"<strong>createCA</strong>\" API is used to generate a Certificate Authority (CA) certificate based on the provided input parameters. This API can generate both self-signed CA certificates and sub CA certificates by specifying the parent CA ID. The generated CA certificate is returned in base64 encoded X509 format.</p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>meta*</td>\n<td>JSON</td>\n<td>The <strong>meta</strong> parameter is a required JSON object that contains external user details necessary for processing the request.  <br />  <br />please refer table <strong>Meta Object Fields</strong> from above  <br />  <br />ex:-  <br />{  <br />\"ver\": \"1.0\",  <br />\"ts\": \"2024-01-01T11:40:15+05:30\",  <br />\"txn\": \"347328314273\",  <br />\"appCode\": \"TestApp\",  <br />\"authKey\": \"0e56ea59a73102605346cdb2a6ee61e1ab6ddb1d4785d8d5f16401bfa03516a7\"  <br />}</td>\n</tr>\n<tr>\n<td>certificateRequestDetails*</td>\n<td>JSON</td>\n<td>The certificateRequestDetails parameter is a required JSON object that contains specific details about the certificate to be generated.  <br />  <br />refer <strong>Table no 1</strong></td>\n</tr>\n</tbody>\n</table>\n</div><p><strong>Table no 1</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>caType*</td>\n<td>String</td>\n<td>Specifies the type of CA certificate being generated. Possible values include \"root\" for a self-signed root CA certificate and \"subCA\" for a sub CA certificate.  <br />  <br />ex:- \"root\" or \"subCA\"</td>\n</tr>\n<tr>\n<td>parentCAID</td>\n<td>String</td>\n<td>The ID of the parent CA. Required if generating a sub CA certificate.  <br />  <br />ex:- \"2\", \"5\"</td>\n</tr>\n<tr>\n<td>validityCriteria*</td>\n<td>String</td>\n<td><strong>validityCriteria (String, required)</strong>: The criteria for the certificate's validity (e.g., \"days\", \"months\", \"years\").  <br />  <br />ex:- \"days\"</td>\n</tr>\n<tr>\n<td>validityValue*</td>\n<td>String</td>\n<td><strong>validityValue :</strong> The value corresponding to the validity criteria (e.g., 365 for 365 days).  <br />  <br />ex:-\"365\"</td>\n</tr>\n<tr>\n<td>keyAlgorithm*</td>\n<td>String</td>\n<td>The key algorithm and size used to generate the key.  <br />refer <strong>Table no 2</strong> for supported algorithm below for more info.  <br />  <br />ex:- \"RSA2048\"</td>\n</tr>\n<tr>\n<td>signingAlgorithm*</td>\n<td>String</td>\n<td>The algorithm used to sign the certificate.  <br />  <br />refer <strong>Table no 2</strong> for supported algorithm below for more info.  <br />  <br />ex:- \"SHA256WithRSA\"</td>\n</tr>\n<tr>\n<td>keyProfile</td>\n<td>String</td>\n<td>This is created from emCA by the administrator and specifies the key profile name, indicating whether keys are created for a particular device such as HSM or PKCS12.  <br />  <br />Ex:- \"HSMProfile\"</td>\n</tr>\n<tr>\n<td>caSubjectAttributes*</td>\n<td>ArrayList of Object</td>\n<td><strong>caSubjectAttributes (Array, required)</strong>: An array of objects containing the subject attributes of the CA certificate. Each object includes:  <br /><strong>dataType</strong> (String, required): The data type of the attribute (e.g., \"PrintableString\").  <br /><strong>oid</strong> (String, required): The Object Identifier (OID) for the attribute.  <br /><strong>value</strong> (String, required): The value of the attribute.  <br />  <br />ex:-  <br />[  <br />{  <br />\"dataType\": \"PrintableString\",  <br />\"oid\": \"2.5.4.3\",  <br />\"value\": \"common name\"  <br />},  <br />\"dataType\": \"Utif8String\",  <br />\"oid\": \"2.5.4.6\",  <br />\"value\": \"IN\"  <br />}  <br />]</td>\n</tr>\n<tr>\n<td>caExtensions*</td>\n<td>JSON</td>\n<td><strong>caExtensions</strong> (Object, optional): A JSON object containing additional X509 extensions for the certificate such as keyUsage, authInfoAccess, certificatePolicy etc  <br />refer Table no 3  <br />  <br />ex:-  <br />\"basicConstraints\": {  <br />\"isEnabled\": \"0\",  <br />\"isCritical\": \"0\",  <br />\"type\": \"root\",  <br />\"pathLength\": \"none\",  <br />\"sortOrder\": \"2\"  <br />},  <br />\"authInfoAccess\": {  <br />\"isEnabled\": \"0\",  <br />\"isCritical\": \"0\",  <br />\"ocspURL\": \"<a href=\"http://example.com/ocsp\">http://example.com/ocsp\"</a>,  <br />\"cAIssuerURL\": \"<a href=\"http://example.com/ca/testca.cer\">http://example.com/ca/testca.cer\"</a>,  <br />\"sortOrder\": \"1\"  <br />}</td>\n</tr>\n</tbody>\n</table>\n</div><p><strong>Table no 2</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Type of Key algorithm</th>\n<th>Supported key algorithm and Sizes</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>RSA</td>\n<td>RSA1024, RSA2048, RSA3072, RSA4096, and RSA8192</td>\n</tr>\n<tr>\n<td>ECDSA secp</td>\n<td>ECC256, ECC384 and ECC521</td>\n</tr>\n<tr>\n<td>ECDSA Brainpool</td>\n<td>B-ECDSA-256, B-ECDSA-384 and B-ECDSA-512</td>\n</tr>\n<tr>\n<td>ECDSA Prime</td>\n<td>P-ECDSA-256, P-ECDSA-384 and P-ECDSA-521</td>\n</tr>\n<tr>\n<td>EDDSA</td>\n<td>Ed25519</td>\n</tr>\n<tr>\n<td>PQC</td>\n<td>DILITHIUM2, DILITHIUM3, DILITHIUM5, FALCON-512, FALCON-1024, sha2_256f, sha2_256s, sha2_128f, sha2_128s, sha2_192f, sha2_192s, shake_128f, shake_128s, shake_192f, hake_192s, shake_256f, shake_256s, haraka_192f, haraka_192s, haraka_256f, haraka_256s and haraka_128f</td>\n</tr>\n</tbody>\n</table>\n</div><p><strong>Table no 3</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>basicConstraints*</td>\n<td>JSON</td>\n<td><strong>basicConstraints</strong>: Specifies whether the certificate is a CA certificate and its criticality, including type and path length constraints.  <br />this parameter is a required JSON object that contains specific details such as below  <br />  <br /><strong>isEnabled</strong> (String, required): Indicates if the basic constraints extension is enabled (\"1\" for enabled, \"0\" for disabled).  <br /><strong>isCritical</strong> (String, required): Indicates if the basic constraints extension is critical (\"1\" for enabled, \"0\" for disabled).  <br /><strong>type</strong> (String, required): Specifies the type of CA (e.g., \"root\", \"subCA\").  <br /><strong>pathLength</strong> (String, required): Specifies the maximum depth of valid certification paths that include this certificate.  <br />sortOrder (String, required): Specifies the order in which this extension is processed.  <br />  <br />ex:-  <br />{  <br />\"isEnabled\": \"0\",  <br />\"isCritical\": \"0\",  <br />\"type\": \"root\",  <br />\"pathLength\": \"none\",  <br />\"sortOrder\": \"2\"  <br />}</td>\n</tr>\n<tr>\n<td>authInfoAccess</td>\n<td></td>\n<td><strong>authInfoAccess</strong>: Contains URLs for OCSP responder and CA issuer, providing authority information access.  <br />  <br />this parameter is a required JSON object that contains specific details such as below  <br />  <br /><strong>isEnabled</strong> (String, required): Indicates if the authority information access extension is enabled (\"1\" for enabled, \"0\" for disabled).  <br /><strong>isCritical</strong> (String, required): Indicates if the authority information access extension is critical (\"1\" for enabled, \"0\" for disabled).  <br /><strong>ocspURL</strong> (String, required): URL of the OCSP responder.  <br />cAIssuerURL (String, required): URL of the CA issuer certificate.  <br /><strong>sortOrder</strong> (String, required): Specifies the order in which this extension is processed.  <br />  <br />{  <br />\"isEnabled\": \"0\",  <br />\"isCritical\": \"0\",  <br />\"ocspURL\": \"<a href=\"http://example.com/ocsp\">http://example.com/ocsp\"</a>,  <br />\"cAIssuerURL\": \"<a href=\"http://example.com/ca/testca.cer\">http://example.com/ca/testca.cer\"</a>,  <br />\"sortOrder\": \"1\"  <br />}</td>\n</tr>\n<tr>\n<td>certificatePolicy</td>\n<td>JSON</td>\n<td><strong>certificatePolicy</strong>: Defines policies under which the certificate was issued, including policy OIDs and CPS URLs.  <br />this parameter is a required JSON object that contains specific details such as below  <br />  <br /><strong>isEnabled</strong> (String, required): Indicates if the certificate policy extension is enabled (\"1\" for enabled, \"0\" for disabled).  <br /><strong>isCritical</strong> (String, required): Indicates if the certificate policy extension is critical (\"1\" for enabled, \"0\" for disabled).  <br />policyOID (Array, required): An array of objects defining policy OIDs and optional user notice texts.  <br />oid (String, required): The Object Identifier for the policy.  <br />noticeText (String, required): Optional text notice for the policy.  <br />cpsURL (String, required): URL of the Certification Practice Statement.  <br />cpsPolicyOID (String, required): OID for the CPS policy.  <br />sortOrder (String, required): Specifies the order in which this extension is processed.  <br />  <br />ex:-  <br />{  <br />\"isEnabled\": \"0\",  <br />\"isCritical\": \"0\",  <br />\"policyOID\": [  <br />{  <br />\"oid\": \"1.3.24.33.34.34\",  <br />\"noticeText\": \"User Notice\"  <br />}  <br />],  <br />\"cpsURL\": \"<a href=\"http://www.example.com/repository/cps/test.pdf\">http://www.example.com/repository/cps/test.pdf\"</a>,  <br />\"cpsPolicyOID\": \"2.16.356.100.1.8.2\",  <br />\"sortOrder\": \"3\"  <br />}</td>\n</tr>\n<tr>\n<td>crlDistribution</td>\n<td></td>\n<td><strong>crlDistribution</strong>: Provides URLs where the CRL (Certificate Revocation List) can be accessed.  <br />this parameter is a required JSON object that contains specific details such as below  <br />  <br /><strong>isEnabled</strong> (String, required): Indicates if the CRL distribution points extension is enabled (\"1\" for enabled, \"0\" for disabled).  <br /><strong>isCritical</strong> (String, required): Indicates if the CRL distribution points extension is critical (\"1\" for enabled, \"0\" for disabled).  <br /><strong>crlURL</strong> (String, required): URL of the CRL.  <br /><strong>sortOrder</strong> (String, required): Specifies the order in which this extension is processed.  <br />  <br />ex:-  <br />{  <br />\"isEnabled\": \"0\",  <br />\"isCritical\": \"0\",  <br />\"crlURL\": \"<a href=\"http://www.example.com/repository/crls/test.crl\">http://www.example.com/repository/crls/test.crl\"</a>,  <br />\"sortOrder\": \"4\"  <br />}</td>\n</tr>\n<tr>\n<td>keyUsageAttributes*</td>\n<td>JSON</td>\n<td><strong>keyUsageAttributes</strong>: Defines the purpose of the key contained in the certificate, such as signing or enciphering.  <br />this parameter is a required JSON object that contains specific details.  <br />  <br /><strong>isEnabled</strong> (String, required): Indicates if the key usage extension is enabled (\"1\" for enabled, \"0\" for disabled).  <br />  <br /><strong>isCritical</strong> (String, required): Indicates if the key usage extension is critical (\"1\" for enabled, \"0\" for disabled).  <br />  <br /><strong>encipherOnly</strong> (String, required): Indicates if the key is used for enciphering only.  <br />  <br /><strong>nonRepudiation</strong> (String, required): Indicates if the key is used for non-repudiation.  <br />  <br /><strong>digitalSignature</strong> (String, required): Indicates if the key is used for digital signatures.  <br />  <br /><strong>keyEncipherment</strong> (String, required): Indicates if the key is used for key encipherment.  <br />dataEncipherment (String, required): Indicates if the key is used for data encipherment.  <br />  <br /><strong>keyAgreement</strong> (String, required): Indicates if the key is used for key agreement.  <br />keyCertSign (String, required): Indicates if the key is used for signing certificates.  <br />  <br /><strong>crlSign</strong> (String, required): Indicates if the key is used for signing CRLs.  <br />  <br /><strong>decipherOnly</strong> (String, required): Indicates if the key is used for deciphering only.  <br />  <br /><strong>sortOrder</strong> (String, required): Specifies the order in which this extension is processed.  <br />ex:-  <br />{  <br />\"isEnabled\": \"0\",  <br />\"encipherOnly\": \"0\",  <br />\"isCritical\": \"0\",  <br />\"nonRepudiation\": \"0\",  <br />\"digitalSignature\": \"0\",  <br />\"keyEncipherment\": \"0\",  <br />\"dataEncipherment\": \"0\",  <br />\"keyAgreement\": \"0\",  <br />\"keyCertSign\": \"0\",  <br />\"crlSign\": \"0\",  <br />\"decipherOnly\": \"0\",  <br />\"sortOrder\": \"5\"  <br />}</td>\n</tr>\n<tr>\n<td>extendedKeyUsageAttributes</td>\n<td></td>\n<td><strong>extendedKeyUsageAttributes</strong>: Specifies additional key usages for the certificate, such as server authentication or email protection.  <br />  <br />this parameter is a required JSON object that contains specific details.  <br />  <br /><strong>isEnabled</strong> (String, required): Indicates if the extended key usage extension is enabled (\"1\" for enabled, \"0\" for disabled).  <br />  <br /><strong>isCritical</strong> (String, required): Indicates if the extended key usage extension is critical (\"1\" for enabled, \"0\" for disabled).  <br />  <br /><strong>serverAuthentication</strong> (String, required): Indicates if the key is used for server authentication.  <br />  <br /><strong>clientAuthentication</strong> (String, required): Indicates if the key is used for client authentication.  <br />  <br /><strong>codeSigning</strong> (String, required): Indicates if the key is used for code signing.  <br />  <br /><strong>emailProtection</strong> (String, required): Indicates if the key is used for email protection.  <br />  <br /><strong>timeStamping</strong> (String, required): Indicates if the key is used for timestamping.  <br />  <br /><strong>ocspSigning</strong> (String, required): Indicates if the key is used for OCSP signing.  <br />  <br /><strong>msftDocumentSigning</strong> (String, required): Indicates if the key is used for Microsoft document signing.  <br />  <br />smartCardLogon (String, required): Indicates if the key is used for smart card logon.  <br />  <br /><strong>adobeCertifiedDocumentSigning</strong> (String, required): Indicates if the key is used for Adobe certified document signing.  <br />  <br /><strong>encryptionFileSystem</strong> (String, required): Indicates if the key is used for the encryption file system.  <br /><strong>sortOrder</strong> (String, required): Specifies the order in which this extension is processed.  <br />  <br />ex:-  <br />{  <br />\"isEnabled\": \"0\",  <br />\"isCritical\": \"0\",  <br />\"serverAuthentication\": \"0\",  <br />\"clientAuthentication\": \"0\",  <br />\"codeSigning\": \"0\",  <br />\"emailProtection\": \"0\",  <br />\"timeStamping\": \"0\",  <br />\"ocspSigning\": \"0\",  <br />\"msftDocumentSigning\": \"0\",  <br />\"smartCardLogon\": \"0\",  <br />\"adobeCertifiedDocumentSigning\": \"0\",  <br />\"encryptionFileSystem\": \"0\",  <br />\"sortOrder\": \"6\"  <br />}</td>\n</tr>\n<tr>\n<td>subjectKeyIdentifier*</td>\n<td></td>\n<td><strong>subjectKeyIdentifier</strong>: Provides a unique identifier for the certificate's public key.  <br />  <br /><strong>isEnabled</strong> (String, required): Indicates if the subject key identifier extension is enabled (\"1\" for enabled, \"0\" for disabled).  <br /><strong>isCritical</strong> (String, required): Indicates if the subject key identifier extension is critical (\"1\" for enabled, \"0\" for disabled).  <br /><strong>sortOrder</strong> (String, required): Specifies the order in which this extension is processed.  <br />  <br />ex:-  <br />{  <br />\"isEnabled\": \"0\",  <br />\"isCritical\": \"0\",  <br />\"sortOrder\": \"6\"  <br />}</td>\n</tr>\n<tr>\n<td>authorityKeyIdentifier*</td>\n<td></td>\n<td><strong>authorityKeyIdentifier</strong>: Provides a unique identifier for the key used to sign the certificate.  <br />  <br /><strong>isEnabled</strong> (String, required): Indicates if the authority key identifier extension is enabled (\"1\" for enabled, \"0\" for disabled).  <br /><strong>isCritical</strong> (String, required): Indicates if the authority key identifier extension is critical (\"1\" for enabled, \"0\" for disabled).  <br /><strong>sortOrder</strong> (String, required): Specifies the order in which this extension is processed.  <br />  <br />{  <br />\"isEnabled\": \"0\",  <br />\"isCritical\": \"0\",  <br />\"sortOrder\": \"7\"  <br />}</td>\n</tr>\n<tr>\n<td>sanDetails</td>\n<td></td>\n<td><strong>sanDetails</strong>: Specifies the Subject Alternative Name (SAN) attributes, including types and values.  <br />  <br /><strong>isCritical</strong> (String, required): Indicates if the SAN extension is critical (\"1\" for enabled, \"0\" for disabled).  <br />  <br /><strong>isEnabled</strong> (String, required): Indicates if the SAN extension is enabled (\"1\" for enabled, \"0\" for disabled).  <br />  <br /><strong>sortOrder</strong> (String, required): Specifies the order in which this extension is processed.  <br />  <br /><strong>attri</strong>butes (Array, required): An array of objects specifying SAN attributes, each containing:  <br />  <br /><strong>type</strong> (String, required): The type of SAN (e.g., \"rfc822Name\").  <br />  <br /><strong>value</strong> (String, required): The value of the SAN attribute.  <br />  <br /><strong>isMandatory</strong> (String, required): Indicates if the SAN attribute is mandatory.  <br />  <br />ex:-  <br />{  <br />\"isCritical\": \"0\",  <br />\"isEnabled\": \"0\",  <br />\"sortOrder\": \"1\",  <br />\"attributes\": [  <br />{  <br />\"type\": \"rfc822Name\",  <br />\"value\": \"<a href=\"https://mailto:test@test.com\">test@test.com</a>\",  <br />\"isMandatory\": \"0\"  <br />}  <br />]  <br />}</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","create","ca"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"a23dbdd0-3c64-4990-93a2-ec78d3a05593"},{"name":"createCSR","id":"24daaaa6-fdad-4c75-bfd7-e978a61a9218","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"}],"body":{"mode":"raw","raw":"{\r\n  \"meta\": {\r\n        \"ver\": \"1.0\",\r\n        \"ts\": \"2024-06-04T11:40:15+05:30\",\r\n        \"txn\": \"3473283142736543345\",\r\n        \"appCode\": \"certinext\",\r\n        \"authKey\": \"702e3cf0a395063f654cbce7b71d0d647fc8816eabeb353170caaab3b3146dd4\"\r\n    },\r\n  \"certificateRequestDetails\": {\r\n    \"keyAlgorithm\": \"RSA2048\",\r\n    \"signingAlgorithm\": \"SHA256WithRSA\",\r\n    \"caSubjectAttributes\": [\r\n      {\r\n        \"dataType\": \"PrintableString\",\r\n        \"oid\": \"2.5.4.3\",\r\n        \"value\": \"TEST CSR CA1\"\r\n      }\r\n    ]\r\n  }\r\n}","options":{"raw":{"language":"json"}}},"url":"https://appemca.emudhra.com/emCAServices431/rest/create/csr","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The \"<strong>createCSR</strong>\" API is used to generate a Certificate Signing Request (CSR) for requesting a CA certificate to be signed by an issuing Certificate Authority (CA). The generated CSR includes necessary information about the certificate and is used to apply for a CA certificate from the issuing CA.</p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>meta*</td>\n<td>JSON</td>\n<td>The <strong>meta</strong> parameter is a required JSON object that contains external user details necessary for processing the request.  <br />  <br />please refer table <strong>Meta Object Fields</strong> from above  <br />  <br />ex:-  <br />{  <br />\"ver\": \"1.0\",  <br />\"ts\": \"2024-01-01T11:40:15+05:30\",  <br />\"txn\": \"347328314273\",  <br />\"appCode\": \"TestApp\",  <br />\"authKey\": \"0e56ea59a73102605346cdb2a6ee61e1ab6ddb1d4785d8d5f16401bfa03516a7\"  <br />}</td>\n</tr>\n<tr>\n<td>certificateRequestDetails*</td>\n<td>JSON</td>\n<td>The <strong>certificateRequestDetails</strong> parameter is a required JSON object that contains specific details about the certificate to be generated.  <br />  <br />refer <strong>Table no 1</strong></td>\n</tr>\n</tbody>\n</table>\n</div><p><strong>Table no 1</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>keyAlgorithm*</td>\n<td>String</td>\n<td>The key algorithm and size used to generate the key.  <br />refer <strong>Table no 2</strong> for supported algorithm below for more info.  <br />  <br />ex:- \"RSA2048\", \"ECC256\"</td>\n</tr>\n<tr>\n<td>signingAlgorithm*</td>\n<td>String</td>\n<td>The algorithm used to sign the certificate.  <br />  <br />refer <strong>Table no 2</strong> for supported algorithm below for more info.  <br />  <br />ex:- \"SHA256WithRSA\"</td>\n</tr>\n<tr>\n<td>keyProfile</td>\n<td>String</td>\n<td>This is created from emCA by the administrator and specifies the key profile name, indicating where keys are created for a particular device such as HSM or PKCS12.  <br />  <br />Ex:- \"HSMProfile\"</td>\n</tr>\n<tr>\n<td>caSubjectAttributes*</td>\n<td>ArrayList of Object</td>\n<td><strong>caSubjectAttributes (Array, required)</strong>: An array of objects containing the subject attributes of the CA certificate. Each object includes:  <br /><strong>dataType</strong> (String, required): The data type of the attribute (e.g., \"PrintableString\").  <br /><strong>oid</strong> (String, required): The Object Identifier (OID) for the attribute.  <br /><strong>value</strong> (String, required): The value of the attribute.  <br />  <br />ex:-  <br />[  <br />{  <br />\"dataType\": \"PrintableString\",  <br />\"oid\": \"2.5.4.3\",  <br />\"value\": \"common name\"  <br />},  <br />\"dataType\": \"Utif8String\",  <br />\"oid\": \"2.5.4.6\",  <br />\"value\": \"IN\"  <br />}  <br />]</td>\n</tr>\n<tr>\n<td>sanDetails</td>\n<td>ArrayList of Object</td>\n<td><strong>sanDetails</strong> (Object, optional): A JSON object containing Subject Alternative Name (SAN) details:  <br />attributes (Array, required): An array of objects specifying SAN attributes. Each object includes:  <br />type (String, required): The type of SAN attribute, such as \"rfc822Name\".  <br />value (String, required): The value of the SAN attribute, such as \"<a href=\"https://mailto:test@test.com\">test@test.com</a>\".  <br />  <br />ex:-  <br />{  <br />\"attributes\": [  <br />{  <br />\"type\": \"rfc822Name\",  <br />\"value\": \"<a href=\"https://mailto:test@test.com\">test@test.com</a>\"  <br />},  <br />{  <br />\"type\": \"dnsName\",  <br />\"value\": \"<a href=\"https://mailto:test@test.com\">www.example.com</a>\"  <br />},  <br />]  <br />}</td>\n</tr>\n</tbody>\n</table>\n</div><p><strong>Table no 2</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Type of Key algorithm</th>\n<th>Supported key algorithm and Sizes</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>RSA</td>\n<td>RSA1024, RSA2048, RSA3072, RSA4096, and RSA8192</td>\n</tr>\n<tr>\n<td>ECDSA secp</td>\n<td>ECC256, ECC384 and ECC521</td>\n</tr>\n<tr>\n<td>ECDSA Brainpool</td>\n<td>B-ECDSA-256, B-ECDSA-384 and B-ECDSA-512</td>\n</tr>\n<tr>\n<td>ECDSA Prime</td>\n<td>P-ECDSA-256, P-ECDSA-384 and P-ECDSA-521</td>\n</tr>\n<tr>\n<td>EDDSA</td>\n<td>Ed25519</td>\n</tr>\n<tr>\n<td>PQC</td>\n<td>DILITHIUM2, DILITHIUM3, DILITHIUM5, FALCON-512, FALCON-1024, sha2_256f, sha2_256s, sha2_128f, sha2_128s, sha2_192f, sha2_192s, shake_128f, shake_128s, shake_192f, hake_192s, shake_256f, shake_256s, haraka_192f, haraka_192s, haraka_256f, haraka_256s and haraka_128f</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","create","csr"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"24daaaa6-fdad-4c75-bfd7-e978a61a9218"},{"name":"importCertificate","id":"a50ec951-bca8-435c-be7e-6c49e52448c3","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"}],"body":{"mode":"raw","raw":"{\r\n    \"meta\": {\r\n        \"ver\": \"1.0\",\r\n        \"ts\": \"2024-06-04T11:40:15+05:30\",\r\n        \"txn\": \"3473283142736543345\",\r\n        \"appCode\": \"certinext\",\r\n        \"authKey\": \"702e3cf0a395063f654cbce7b71d0d647fc8816eabeb353170caaab3b3146dd4\"\r\n    },\r\n    \"importType\": \"CA\",\r\n    \"caId\": \"4\",\r\n    \"certData\": \"MIIDmzCCAgOgAwIBAgIRAISAcEvGJRDD7pbBvrPb8zAwDQYJKoZIhvcNAQELBQAwHTEbMBkGA1UEAxMSRWxpbmF0aC1Sb3NlIE1vc2hpMB4XDTI0MDUxNzExNTQzNFoXDTI1MDEyMjE4Mjk1OVowFjEUMBIGA1UEAxMLVEVTVCBDU1IgQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCndPrua9PateFtRxwCr9/MEDVWW4NS6u4M+T3VYfqsciBFcNAxzY+v5pcWbXC1EbV8PZtOodFBwpCMRRSNuI6/y79QpV/c39SrAMfvfKZAW5aRxlaqTCQAlEzQQo+c0CZtG/QooBqkUKACHn7j7Zk1jQyzXZDe3iLlMfgMqWkK63VeFQQnSFI8oK+QYRyP/UFT5aO/VUFYbfmLWWpptpQAuNJX/53skmpu2o+k7B8cP/VE2gjNUJx4e2rX3EP+K2rdI+abr0Kr1VRNrOB5UQGcUrBIQ6XXjL7qUohD3pZR3bSOpiB6qJivkZ31zMQpUmISVA/H061knvjC6nmENVIRAgMBAAGjXTBbMAwGA1UdEwQFMAMBAf8wCwYDVR0PBAQDAgbAMB8GA1UdIwQYMBaAFLyIjEk3G0Wxm2+lF9OD2WrKUoTgMB0GA1UdDgQWBBQchzKxYzUf+JLAb/YLTFh1MewDXzANBgkqhkiG9w0BAQsFAAOCAYEAuBrsCwOQt/uY54uawPCqgzQqK54eG2bvKFGGROJZFRazyoF1uIMZoOCrcDeRveX8GhVs1Q/yH1wbx7xwwlwRCBKKU/uIn5QxwfulGdjdVjsoNHacJFjeN5P2RGHZYuRstJEsn0MllsUDWk+b8BexcxWKy3A5CqDO1l422S5XLCakiGKUJXVJqndEle0wSCAnVA1gcXzpQOu7zPKElWNm5US0v+/tjF712GY0FNmlLAxmFqyTlpH7WlgUix5OKOyCIgErPAoKeVIqgSAgdK7By/XrejPtWobUAH/tYSS46AwEoEn7+55A6DFkUiCE2uCe94zVOhOnAkmjxV/wL0PqaLwQUq32XutXtJg3Gar3KD3fH1um+ZtcZKKu80n86hlGmZjGiio+t3Q1ZStgXfnR5QvLBUW/1tnftzuHWmNgRS/YuEwU2eRy50BUVfdvL+8gKQnMUGHPPtCiNsvaWIQV/AWPc44JHCcghwYlLHCk3qxZdt1uqLAy8N37eyN2ss9D\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://appemca.emudhra.com/emCAServices431/rest/import/certificate","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The \"<strong>importCertificate</strong>\" API is used to import a signed certificate or an issuer certificate into the system. This allows the system to recognize and use the imported certificate for various cryptographic operations and verifications.</p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>meta*</td>\n<td>JSON</td>\n<td>The <strong>meta</strong> parameter is a required JSON object that contains external user details necessary for processing the request.  <br />  <br />please refer table <strong>Meta Object Fields</strong> from above  <br />  <br />ex:-  <br />{  <br />\"ver\": \"1.0\",  <br />\"ts\": \"2024-01-01T11:40:15+05:30\",  <br />\"txn\": \"347328314273\",  <br />\"appCode\": \"TestApp\",  <br />\"authKey\": \"0e56ea59a73102605346cdb2a6ee61e1ab6ddb1d4785d8d5f16401bfa03516a7\"  <br />}</td>\n</tr>\n<tr>\n<td>importType*</td>\n<td>String</td>\n<td><strong>importType</strong> (String, required): Specifies the type of certificate being imported. Possible values are \"CA\" for a Certificate Authority certificate or \"Issuer\" for an issuer certificate.  <br />  <br />ex: \"CA\"</td>\n</tr>\n<tr>\n<td>caId*</td>\n<td>Integer</td>\n<td><strong>caId</strong> (Integer, required): The identifier of the ca certificate associated with the certificate being imported.  <br />  <br />ex:-4</td>\n</tr>\n<tr>\n<td>certData*</td>\n<td>String</td>\n<td><strong>certData</strong> (String, required): The base64 encoded certificate data.  <br />  <br />ex:-  <br />\"MIICdzCCAeCgAwIBAgIJALkYTrIoPo..........Rlc3QgQ0EwHhcNMjIwNzA1MDI0NzAwWhcNMjMwNzA1N1mkI5eNFP8Q==\"</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","import","certificate"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"a50ec951-bca8-435c-be7e-6c49e52448c3"},{"name":"createOrUpdateCRLProfile","id":"b9ccf547-8133-42df-9816-4f9aeb6fe0e0","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"}],"body":{"mode":"raw","raw":"{\r\n  \"meta\": {\r\n        \"ver\": \"1.0\",\r\n        \"ts\": \"2024-06-04T11:40:15+05:30\",\r\n        \"txn\": \"3473283142736543345\",\r\n        \"appCode\": \"certinext\",\r\n        \"authKey\": \"702e3cf0a395063f654cbce7b71d0d647fc8816eabeb353170caaab3b3146dd4\"\r\n    },\r\n  \"crlProfileRequestDetails\": {\r\n    \"crlProfileID\": 0,\r\n    \"profileName\": \"CRL PRofile1\",\r\n    \"validity\": 15,\r\n    \"customCRLNumber\": 1,\r\n    \"isCRLAutoGeneration\": \"1\",\r\n    \"crlFrequency\": 1,\r\n    \"extensions\": {\r\n      \"authorityInformationAccess\": {\r\n        \"isEnabled\": \"0\",\r\n        \"sortOrder\": 0\r\n      },\r\n      \"deltaCRL\": {\r\n        \"baseCRLNumber\": 0,\r\n        \"isEnabled\": \"string\",\r\n        \"sortOrder\": 0\r\n      },\r\n      \"freshestCRL\": {\r\n        \"deltaCRLDistributionPoint\": \"string\",\r\n        \"isEnabled\": \"string\",\r\n        \"sortOrder\": 0\r\n      },\r\n      \"issuerAlternateName\": {\r\n        \"isEnabled\": \"string\",\r\n        \"sortOrder\": 0\r\n      },\r\n      \"issusingDistributionPoint\": {\r\n        \"certificateCount\": 0,\r\n        \"distributionPointUrl\": \"string\",\r\n        \"inDirectCRL\": \"string\",\r\n        \"isEnabled\": \"string\",\r\n        \"onlyContainsCACerts\": \"string\",\r\n        \"onlyContainsUserCert\": \"string\",\r\n        \"partitionCount\": 0,\r\n        \"sortOrder\": 0\r\n      }\r\n    }\r\n  }\r\n}","options":{"raw":{"language":"json"}}},"url":"https://appemca.emudhra.com/emCAServices431/rest/create/update/crl-profile","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The \"<strong>createOrUpdateCRLProfile</strong>\" API is used to create or update a Certificate Revocation List (CRL) template. The createOrUpdateCRLProfile API is used to create or update a Certificate Revocation List (CRL) template.</p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>meta*</td>\n<td>JSON</td>\n<td>The <strong>meta</strong> parameter is a required JSON object that contains external user details necessary for processing the request.  <br />  <br />please refer table <strong>Meta Object Fields</strong> from above  <br />  <br />ex:-  <br />{  <br />\"ver\": \"1.0\",  <br />\"ts\": \"2024-01-01T11:40:15+05:30\",  <br />\"txn\": \"347328314273\",  <br />\"appCode\": \"TestApp\",  <br />\"authKey\": \"0e56ea59a73102605346cdb2a6ee61e1ab6ddb1d4785d8d5f16401bfa03516a7\"  <br />}</td>\n</tr>\n<tr>\n<td>crlProfileRequestDetails*</td>\n<td>JSON</td>\n<td>The crlProfileRequestDetails parameter is a required JSON object that contains specific details about the crl template to be generated.  <br />  <br />refer <strong>Table no 1</strong></td>\n</tr>\n</tbody>\n</table>\n</div><p><strong>Table no 1</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>crlProfileID*</td>\n<td>Integer</td>\n<td><strong>crlProfileID</strong> (Integer, optional): The unique identifier for the CRL profile. If provided, updates the existing profile; if not provided (or set to 0), creates a new profile.  <br />  <br />ex:- 4</td>\n</tr>\n<tr>\n<td>profileName</td>\n<td>String</td>\n<td>profileName (String, required): The name of the CRL profile.  <br />  <br />ex:- \"sub ca crl profile\"</td>\n</tr>\n<tr>\n<td>validity*</td>\n<td>Integer</td>\n<td><strong>validity</strong> (Integer, required): The validity period of the CRL in days.  <br />  <br />ex:-365</td>\n</tr>\n<tr>\n<td>customCRLNumber*</td>\n<td>Integer</td>\n<td><strong>customCRLNumber</strong> (Integer, required): Custom CRL number for the CRL.  <br />  <br />ex:- 1</td>\n</tr>\n<tr>\n<td>isCRLAutoGeneration*</td>\n<td>String</td>\n<td><strong>isCRLAutoGeneration</strong> (String, required): Indicates whether CRL auto-generation is enabled ( \"1\" - \"true\", \"0\"- false\").  <br />  <br />ex:- \"1\"</td>\n</tr>\n<tr>\n<td>crlFrequency</td>\n<td>Integer</td>\n<td><strong>crlFrequency</strong> (Integer, required): Frequency of CRL generation.  <br />  <br />Ex:- \"1\"</td>\n</tr>\n<tr>\n<td>extensions*</td>\n<td>JSON</td>\n<td><strong>extensions</strong> (Object, required): Contains extension settings for the CRL profile, including:  <br />authorityInformationAccess: Settings for Authority Information Access.  <br />deltaCRL: Settings for Delta CRL.  <br />freshestCRL: Settings for Freshest CRL.  <br />issuerAlternateName: Settings for Issuer Alternate Name.  <br />issuingDistributionPoint: Settings for Issuing Distribution Point.  <br />  <br />ex:-  <br />{ \"authorityInformationAccess\": {  <br />\"isEnabled\": \"0\",  <br />\"sortOrder\": 0  <br />},  <br />\"deltaCRL\": {  <br />\"baseCRLNumber\": 0,  <br />\"isEnabled\": \"0\",  <br />\"sortOrder\": 0  <br />},  <br />\"issuerAlternateName\": {  <br />\"isEnabled\": \"0\",  <br />\"sortOrder\": 0  <br />},  <br />}</td>\n</tr>\n</tbody>\n</table>\n</div><p><strong>Table no 2</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>authorityInformationAccess</td>\n<td>JSON</td>\n<td><strong>authInfoAccess</strong>: Contains URLs for OCSP responder and CA issuer, providing authority information access.  <br />  <br />this parameter is a required JSON object that contains specific details such as below  <br />  <br /><strong>isEnabled</strong> (String, required): Indicates if the authority information access extension is enabled (\"1\" for enabled, \"0\" for disabled).  <br /><strong>isCritical</strong> (String, required): Indicates if the authority information access extension is critical (\"1\" for enabled, \"0\" for disabled).  <br />  <br />{  <br />\"isEnabled\": \"0\",  <br />\"isCritical\": \"0\"  <br />}</td>\n</tr>\n<tr>\n<td>deltaCRL</td>\n<td></td>\n<td><strong>deltaCRL</strong>: Configures Delta CRL settings, including \"baseCRLNumber\" for the base CRL number, \"isEnabled\" (\"1\" for enabled, \"0\" for disabled) to activate Delta CRL, and \"sortOrder\" for prioritization.  <br />  <br />{  <br />\"baseCRLNumber\": 0,  <br />\"isEnabled\": \"0\",  <br />\"sortOrder\": 0  <br />}</td>\n</tr>\n<tr>\n<td>freshestCRL</td>\n<td>JSON</td>\n<td><strong>freshestCRL</strong>: Handles Freshest CRL settings, with \"<strong>deltaCRLDistributionPoint</strong>\" for Delta CRL distribution, \"<strong>isEnabled</strong>\" (\"1\" for enabled, \"0\" for disabled) to activate Freshest CRL, and \"<strong>sortOrder</strong>\" for ordering.  <br />  <br />ex:-  <br />{  <br />\"deltaCRLDistributionPoint\": \"string\",  <br />\"isEnabled\": \"0\",  <br />\"sortOrder\": 0  <br />}</td>\n</tr>\n<tr>\n<td>issuerAlternateName</td>\n<td></td>\n<td><strong>issuerAlternateName</strong>: Controls Issuer Alternate Name settings, using \"<strong>isEnabled</strong>\" (\"1\" for enabled, \"0\" for disabled) to activate this feature and \"<strong>sortOrder</strong>\" to define its order.  <br />  <br />ex:-  <br />{  <br />\"isEnabled\": \"0\",  <br />\"sortOrder\": 0  <br />}</td>\n</tr>\n<tr>\n<td>issusingDistributionPoint</td>\n<td>JSON</td>\n<td><strong>issuingDistributionPoint</strong>: Manages Issuing Distribution Point attributes, including \"<strong>inDirectCRL</strong>\" for indirect CRLs, \"<strong>onlyContainsCACerts</strong>\" and \"<strong>onlyContainsUserCert</strong>\" for certificate types, \"<strong>isEnabled</strong>\" (\"1\" for enabled, \"0\" for disabled) to activate this feature, \"<strong>distributionPointUrl</strong>\" for URL, \"<strong>partitionCount</strong>\", \"<strong>certificateCount</strong>\", and \"<strong>sortOrder</strong>\" for ordering attributes.  <br />  <br />ex:-  <br />{  <br />\"inDirectCRL\": \"0\", \"onlyContainsCACerts\": \"0\", \"onlyContainsUserCert\": \"0\",  <br />\"isEnabled\": \"0\",  <br />\"distributionPointUrl\": \"<a href=\"https://emca-vapt.emudhra.net/repository:8443/crl/RootCertificate2024.crl\">http://l127.0.0./crl/test.cr</a>\",  <br />\"partitionCount\": 0,  <br />\"certificateCount\": 0,  <br />\"sortOrder\": 5  <br />}</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","create","update","crl-profile"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"b9ccf547-8133-42df-9816-4f9aeb6fe0e0"},{"name":"createOrUpdateCRL","id":"bbb27187-554f-4708-8ecf-c6c993bfe095","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"}],"body":{"mode":"raw","raw":"{\r\n  \"meta\": {\r\n        \"ver\": \"1.0\",\r\n        \"ts\": \"2024-06-04T11:40:15+05:30\",\r\n        \"txn\": \"3473283142736543345\",\r\n        \"appCode\": \"certinext\",\r\n        \"authKey\": \"702e3cf0a395063f654cbce7b71d0d647fc8816eabeb353170caaab3b3146dd4\"\r\n    },\r\n  \"cRLRequestDetails\": {\r\n    \"caId\": 1,\r\n    \"signingAlgorithm\": \"SHA256WithRSA\",\r\n    \"crlProfileId\": 1\r\n  }\r\n}","options":{"raw":{"language":"json"}}},"url":"https://appemca.emudhra.com/emCAServices431/rest/create/update/crl","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The \"<strong>createOrUpdateCRL</strong>\" API is used to generate a new Certificate Revocation List (CRL) or update an existing CRL. The request includes the following parameters within the cRLRequestDetails object:</p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>meta*</td>\n<td>JSON</td>\n<td>The <strong>meta</strong> parameter is a required JSON object that contains external user details necessary for processing the request.  <br />  <br />please refer table <strong>Meta Object Fields</strong> from above  <br />  <br />ex:-  <br />{  <br />\"ver\": \"1.0\",  <br />\"ts\": \"2024-01-01T11:40:15+05:30\",  <br />\"txn\": \"347328314273\",  <br />\"appCode\": \"TestApp\",  <br />\"authKey\": \"0e56ea59a73102605346cdb2a6ee61e1ab6ddb1d4785d8d5f16401bfa03516a7\"  <br />}</td>\n</tr>\n<tr>\n<td>cRLRequestDetails*</td>\n<td>JSON</td>\n<td>The <strong>cRLRequestDetails</strong> parameter is a required JSON object that contains specific details about the crl template to be generated.  <br />  <br />refer <strong>Table no 1</strong></td>\n</tr>\n</tbody>\n</table>\n</div><p><strong>Table no 1</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>caId*</td>\n<td>Integer</td>\n<td>caId (Integer, required): The Id of the CA certificate that is generated from the <strong>createCA</strong> API.  <br />  <br />ex:- 4</td>\n</tr>\n<tr>\n<td>signingAlgorithm*</td>\n<td>String</td>\n<td><strong>signingAlgorithm</strong> (String, required): The algorithm used to sign the CRL, which should match the CA certificate's signing algorithm  <br />  <br />ex:- \"SHA256WithRSA\"</td>\n</tr>\n<tr>\n<td>crlProfileId*</td>\n<td>Integer</td>\n<td><strong>crlProfileId</strong> (Integer, required): The ID of the CRL profile that is generated from the <strong>createOrUpdateCRLProfile</strong> API.  <br />  <br />ex:-\"crl profile\"</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","create","update","crl"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"bbb27187-554f-4708-8ecf-c6c993bfe095"},{"name":"getCRL","id":"cdd170c3-04f1-40e6-9025-b3ec4e213068","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"}],"body":{"mode":"raw","raw":"{\r\n  \"meta\": {\r\n        \"ver\": \"1.0\",\r\n        \"ts\": \"2024-06-04T11:40:15+05:30\",\r\n        \"txn\": \"3473283142736543345\",\r\n        \"appCode\": \"certinext\",\r\n        \"authKey\": \"702e3cf0a395063f654cbce7b71d0d647fc8816eabeb353170caaab3b3146dd4\"\r\n    },\r\n  \"caSerialNo\": \"e78b0b75a0fcaf2a7d2fc0aca01ae1d\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://appemca.emudhra.com/emCAServices431/rest/get-crl","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The \"<strong>getCRL</strong>\" API is used to download a Certificate Revocation List (CRL) by providing the CA's certificate serial number and app code.</p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<p><strong>Table no 1</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>caSerialNo*</td>\n<td>String</td>\n<td>Certificate serial number  <br />  <br />Ex :- “b4cb23a4b97g5d0c12f2641c1fc49d9ba7”</td>\n</tr>\n<tr>\n<td>appCode*</td>\n<td>String</td>\n<td><strong>appCode</strong> is used as part of External Application Registration at emCA.  <br />  <br />Ex :- “MyApp”</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","get-crl"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"cdd170c3-04f1-40e6-9025-b3ec4e213068"},{"name":"getCRL","id":"cf6b31e9-99b0-4471-9397-074b024221fa","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[],"url":"https://appemca.emudhra.com/emCAServices431/rest/get-crl/{{x_client_id}}/TestUser","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The \"<strong>getCRL</strong>\" GET supported API is used to download a Certificate Revocation List (CRL) by providing the CA's serial number and app code.  </p>\n<p><strong>URL</strong></p>\n<p><a href=\"https://appemca.emudhra.com/emCAServices/rest/get-crl/%7BcaSerialNo%7D/%7BappCode%7D\">https://appemca.emudhra.com/emCAServices/rest/get-crl/{caSerialNo}/{appCode}</a></p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<p><strong>Table no 1</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>caSerialNo*</td>\n<td>String</td>\n<td>Certificate serial number need to pass in path variable  <br />  <br />Ex :- “b4cb23a4b97g5d0c12f2641c1fc49d9ba7”</td>\n</tr>\n<tr>\n<td>appCode*</td>\n<td>String</td>\n<td><strong>appCode</strong> is used as part of External Application Registration at emCA and needs to be passed in the path variable.  <br />  <br />Ex :- “MyApp”</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","get-crl","{{x_client_id}}","TestUser"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"cf6b31e9-99b0-4471-9397-074b024221fa"},{"name":"revoke/suspend","id":"a2999337-c571-49f9-94d8-e243103cbb40","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"}],"body":{"mode":"raw","raw":"{\r\n  \"meta\": {\r\n        \"ver\": \"1.0\",\r\n        \"ts\": \"2024-06-04T11:40:15+05:30\",\r\n        \"txn\": \"3473283142736543345\",\r\n        \"appCode\": \"certinext\",\r\n        \"authKey\": \"702e3cf0a395063f654cbce7b71d0d647fc8816eabeb353170caaab3b3146dd4\"\r\n    },\r\n  \"revokeDetails\": {\r\n    \"serialNo\": \"67b3725c49a2e7e5ab13f82effe7f8e9\",\r\n    \"remarks\": \"test\",\r\n    \"reason\": 1\r\n  }\r\n}","options":{"raw":{"language":"json"}}},"url":"https://appemca.emudhra.com/emCAServices431/rest/revoke/suspend/ca","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The <strong>\"revoke/suspend/ca\"</strong> API facilitates the <strong>revocation</strong> or <strong>suspension</strong> of a CA Certificate based on its <strong>serial number</strong> and <strong>reason code</strong>. This functionality is crucial for invalidating certificates that are <strong>compromised</strong> or <strong>no longer trusted</strong>.</p>\n<p>By specifying the serial number of the certificate, this API ensures <strong>immediate termination or suspension</strong> of its validity, thereby maintaining <strong>security</strong> and <strong>compliance</strong> with organizational policies regarding CA management.</p>\n<p>If the <strong>reason code is</strong> <strong><code>6</code></strong>, the certificate is treated as <strong>suspended</strong> (typically for temporary hold).</p>\n<p>For <strong>all other reason codes</strong>, the certificate is treated as <strong>revoked</strong>.</p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<p>Table no 1</p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>serialNo*</td>\n<td>String</td>\n<td>Certificate serial number for which revoke or suspend is initiated.  <br />  <br />Ex :- “b4cb23a4b97g5d0c12f2641c1fc49d9ba7”</td>\n</tr>\n<tr>\n<td>reason*</td>\n<td>Integer</td>\n<td>0 (Unspecified): Reason not specified or unknown.  <br />  <br />1 (Key Compromise): Private key associated with the certificate compromised or suspected compromised.  <br />  <br />2 (CA compromise): Certificate Authority (CA) certificate or private key compromised or suspected compromised.  <br />  <br />3 (Affiliation Changed): Certificate holder's affiliation or relationship with the organization changed.  <br />  <br />4 (Superseded): Certificate replaced by a new certificate.  <br />  <br />5 (Cessation of Operation): Organization or entity associated with the certificate ceased operation.  <br />  <br />5 (CertificateHold): Organization or entity associated with the certificate will be hold.  <br />  <br />9 (Privilege Withdrawn): Privileges associated with the certificate holder withdrawn.  <br />  <br />10 (AA Compromise): Certificate used for authentication or authorization compromised or suspected compromised.  <br />  <br />ex:- 4</td>\n</tr>\n<tr>\n<td>remarks*</td>\n<td>String</td>\n<td>The '<strong>Remarks</strong>' parameter in the 'revoke' API allows users to include additional comments to the certificate rekeying process.  <br />  <br />ex:-\"Certificate expired\"</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","revoke","suspend","ca"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"a2999337-c571-49f9-94d8-e243103cbb40"},{"name":"reinstateCA","id":"0d62fb7f-f117-4b5a-a300-36405e608a3e","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"}],"body":{"mode":"raw","raw":"{\r\n  \"meta\": {\r\n    \"ver\": \"1.0\",\r\n    \"ts\": \"2024-01-01T11:40:15+05:30\",\r\n    \"txn\": \"347328314273\",\r\n    \"appCode\": \"TestApp\",\r\n    \"authKey\": \"0e56ea59a73102605346cdb2a6ee61e1ab6ddb1d4785d8d5f16401bfa03516a7\"\r\n  },\r\n  \"rereinstateDetails\": {\r\n    \"serialNo\": \"67b3725c49a2e7e5ab13f82effe7f8e9\",\r\n    \"remarks\": \"test\"\r\n  }\r\n}","options":{"raw":{"language":"json"}}},"url":"https://appemca.emudhra.com/emCAServices431/rest/reinstate/ca","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The '<strong>reinstateCA</strong>' API allows for the reinstatement of previously suspended CA Certificate. This functionality is used to restore certificates that were temporarily invalidated, or other reasons. By specifying the serial number of the suspended certificate, this API ensures the restoration of its validity, maintaining security and compliance with organizational certificate management policies.</p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<p><strong>Table no 1</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>serialNo*</td>\n<td>String</td>\n<td>Certificate serial number for which reinstate is initiated.  <br />  <br />Ex :- “b4cb23a4b97g5d0c12f2641c1fc49d9ba7”</td>\n</tr>\n<tr>\n<td>remarks*</td>\n<td>String</td>\n<td>The '<strong>Remarks</strong>' parameter in the '<strong>reinstate</strong>' API allows users to include additional comments to the certificate rekeying process.  <br />  <br />ex:-\"test\"</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","reinstate","ca"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"0d62fb7f-f117-4b5a-a300-36405e608a3e"},{"name":"createOrUpdateUserProfile","id":"5d2e8010-e146-4a70-be36-e00a9593f86d","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"}],"body":{"mode":"raw","raw":"{\r\n    \"meta\": {\r\n        \"ver\": \"1.0\",\r\n        \"ts\": \"2024-06-04T11:40:15+05:30\",\r\n        \"txn\": \"3473283142736543345\",\r\n        \"appCode\": \"certinext\",\r\n        \"authKey\": \"702e3cf0a395063f654cbce7b71d0d647fc8816eabeb353170caaab3b3146dd4\"\r\n    },\r\n    \"profileRequestDetails\": {\r\n        \"certificateProfileID\": \"\",\r\n        \"profileName\": \"test profile\",\r\n        \"subjectAttributes\": [\r\n            {\r\n                \"value\": \"test user cert\",\r\n                \"oid\": \"2.5.4.3\",\r\n                \"isMandatory\": \"1\",\r\n                \"dataType\": \"PrintableString\"\r\n            }\r\n        ],\r\n        \"extensions\": {\r\n            \"basicConstraints\": {\r\n                \"isEnabled\": \"1\",\r\n                \"isCritical\": \"1\",\r\n                \"type\": \"endEntity\",\r\n                \"pathLength\": \"none\",\r\n                \"sortOrder\": \"2\"\r\n            },\r\n            \"authInfoAccess\": {\r\n                \"isEnabled\": \"0\",\r\n                \"isCritical\": \"0\",\r\n                \"ocspURL\": \"http://example.com/ocsp\",\r\n                \"crtURL\": \"http://example.com/ca/testca.cer\",\r\n                \"sortOrder\": \"1\"\r\n            },\r\n            \"crlDistribution\": {\r\n                \"isEnabled\": \"0\",\r\n                \"isCritical\": \"0\",\r\n                \"crlURL\": \"http://www.example.com/repository/crls/test.crl\",\r\n                \"sortOrder\": \"4\"\r\n            },\r\n            \"keyUsageAttributes\": {\r\n                \"encipherOnly\": \"0\",\r\n                \"isEnabled\": \"1\",\r\n                \"isCritical\": \"1\",\r\n                \"nonRepudiation\": \"0\",\r\n                \"digitalSignature\": \"1\",\r\n                \"keyEncipherment\": \"0\",\r\n                \"dataEncipherment\": \"0\",\r\n                \"keyAgreement\": \"0\",\r\n                \"keyCertSign\": \"0\",\r\n                \"crlSign\": \"0\",\r\n                \"decipherOnly\": \"0\",\r\n                \"sortOrder\": \"5\"\r\n            },\r\n            \"extendedKeyUsageAttributes\": {\r\n                \"isEnabled\": \"0\",\r\n                \"isCritical\": \"0\",\r\n                \"serverAuthentication\": \"0\",\r\n                \"clientAuthentication\": \"0\",\r\n                \"codeSigning\": \"0\",\r\n                \"emailProtection\": \"0\",\r\n                \"timeStamping\": \"0\",\r\n                \"ocspSigning\": \"0\",\r\n                \"msftDocumentSigning\": \"0\",\r\n                \"smartCardLogon\": \"0\",\r\n                \"adobeCertifiedDocumentSigning\": \"0\",\r\n                \"encryptionFileSystem\": \"0\",\r\n                \"sortOrder\": \"6\"\r\n            },\r\n            \"subjectKeyIdentifier\": {\r\n                \"isEnabled\": \"1\",\r\n                \"isCritical\": \"0\",\r\n                \"sortOrder\": \"7\"\r\n            },\r\n            \"authorityKeyIdentifier\": {\r\n                \"isEnabled\": \"1\",\r\n                \"isCritical\": \"0\",\r\n                \"sortOrder\": \"8\"\r\n            }\r\n        }\r\n    }\r\n}","options":{"raw":{"language":"json"}}},"url":"https://appemca.emudhra.com/emCAServices431/rest/create/update/user-profile","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The \"<strong>createOrUpdateUserProfile</strong>\" API is used to create or update a user certificate template. This template defines the details and specifications for user certificates.</p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<h3 id=\"request-input-parameters-1\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>meta*</td>\n<td>JSON</td>\n<td>The <strong>meta</strong> parameter is a required JSON object that contains external user details necessary for processing the request.  <br />  <br />please refer table <strong>Meta Object Fields</strong> from above  <br />  <br />ex:-  <br />{  <br />\"ver\": \"1.0\",  <br />\"ts\": \"2024-01-01T11:40:15+05:30\",  <br />\"txn\": \"347328314273\",  <br />\"appCode\": \"TestApp\",  <br />\"authKey\": \"0e56ea59a73102605346cdb2a6ee61e1ab6ddb1d4785d8d5f16401bfa03516a7\"  <br />}</td>\n</tr>\n<tr>\n<td>profileRequestDetails*</td>\n<td>JSON</td>\n<td>The <strong>profileRequestDetails</strong> parameter is a required JSON object that contains the details for creating or updating a user certificate template.  <br />  <br />refer <strong>Table no 1</strong></td>\n</tr>\n</tbody>\n</table>\n</div><p><strong>Table no 1</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>certificateProfileID</td>\n<td>String</td>\n<td>certificateProfileID (String, required for updating existing profiles, not required for creating new profiles): The unique identifier for the certificate profile.  <br />  <br />ex:- \"2\", \"54\"</td>\n</tr>\n<tr>\n<td>profileName*</td>\n<td>String</td>\n<td>The ID of the parent CA. Required if generating a sub CA certificate.  <br />  <br />ex:- \"2\", \"5\"</td>\n</tr>\n<tr>\n<td>subjectAttributes*</td>\n<td>ArrayList of Object</td>\n<td><strong>subjectAttributes</strong> (Array, required): An array of objects specifying the subject attributes of the certificate. Each object includes:  <br />  <br /><strong>oid</strong> (String, required): The Object Identifier (OID) for the attribute.  <br />  <br /><strong>isMandatory</strong> (String, required): Indicates whether the attribute is mandatory (\"1\" for yes, \"0\" for no).  <br />  <br /><strong>data</strong>Type (String, required): The data type of the attribute, such as \"PrintableString\".  <br />  <br />ex:-  <br />[  <br />{  <br />\"oid\": \"2.5.4.3\",  <br />\"isMandatory\": \"0\",  <br />\"dataType\": \"PrintableString\"  <br />},  <br />\"oid\": \"2.5.4.6\",  <br />\"isMandatory\": \"0\",  <br />\"dataType\": \"Utif8String\"  <br />}  <br />]</td>\n</tr>\n<tr>\n<td>extensions*</td>\n<td>JSON</td>\n<td><strong>caExtensions</strong> (Object, optional): A JSON object containing additional X509 extensions for the certificate such as keyUsage, authInfoAccess, certificatePolicy etc  <br />refer <strong>Table no 2</strong>  <br />  <br />ex:-  <br />\"basicConstraints\": {  <br />\"isEnabled\": \"0\",  <br />\"isCritical\": \"0\",  <br />\"type\": \"root\",  <br />\"pathLength\": \"none\",  <br />\"sortOrder\": \"2\"  <br />},  <br />\"authInfoAccess\": {  <br />\"isEnabled\": \"0\",  <br />\"isCritical\": \"0\",  <br />\"ocspURL\": \"<a href=\"http://example.com/ocsp\">http://example.com/ocsp\"</a>,  <br />\"cAIssuerURL\": \"<a href=\"http://example.com/ca/testca.cer\">http://example.com/ca/testca.cer\"</a>,  <br />\"sortOrder\": \"1\"  <br />}</td>\n</tr>\n</tbody>\n</table>\n</div><p><strong>Table no 2</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>basicConstraints*</td>\n<td>JSON</td>\n<td><strong>basicConstraints</strong>: Specifies the basic constraints for the certificate.  <br />this parameter is a required JSON object that contains specific details such as below  <br />  <br /><strong>isEnabled</strong> (String, required): Indicates if the basic constraints extension is enabled (\"1\" for enabled, \"0\" for disabled).  <br /><strong>isCritical</strong> (String, required): Indicates if the basic constraints extension is critical (\"1\" for enabled, \"0\" for disabled).  <br /><strong>type</strong> (String, required): Specifies the type of CA (e.g., \"root\", \"subCA\").  <br /><strong>pathLength</strong> (String, required): Specifies the maximum depth of valid certification paths that include this certificate.  <br />sortOrder (String, required): Specifies the order in which this extension is processed.  <br />  <br />ex:-  <br />{  <br />\"isEnabled\": \"0\",  <br />\"isCritical\": \"0\",  <br />\"type\": \"endEntity\",  <br />\"pathLength\": \"none\",  <br />\"sortOrder\": \"2\"  <br />}</td>\n</tr>\n<tr>\n<td>authInfoAccess</td>\n<td></td>\n<td><strong>authInfoAccess</strong>: Contains URLs for OCSP responder and CA issuer, providing authority information access.  <br />  <br />this parameter is a required JSON object that contains specific details such as below  <br />  <br /><strong>isEnabled</strong> (String, required): Indicates if the authority information access extension is enabled (\"1\" for enabled, \"0\" for disabled).  <br /><strong>isCritical</strong> (String, required): Indicates if the authority information access extension is critical (\"1\" for enabled, \"0\" for disabled).  <br /><strong>ocspURL</strong> (String, required): URL of the OCSP responder.  <br />cAIssuerURL (String, required): URL of the CA issuer certificate.  <br /><strong>sortOrder</strong> (String, required): Specifies the order in which this extension is processed.  <br />  <br />{  <br />\"isEnabled\": \"0\",  <br />\"isCritical\": \"0\",  <br />\"ocspURL\": \"<a href=\"http://example.com/ocsp\">http://example.com/ocsp\"</a>,  <br />\"cAIssuerURL\": \"<a href=\"http://example.com/ca/testca.cer\">http://example.com/ca/testca.cer\"</a>,  <br />\"sortOrder\": \"1\"  <br />}</td>\n</tr>\n<tr>\n<td>certificatePolicy</td>\n<td>JSON</td>\n<td><strong>certificatePolicy</strong>: Defines policies under which the certificate was issued, including policy OIDs and CPS URLs.  <br />this parameter is a required JSON object that contains specific details such as below  <br />  <br /><strong>isEnabled</strong> (String, required): Indicates if the certificate policy extension is enabled (\"1\" for enabled, \"0\" for disabled).  <br /><strong>isCritical</strong> (String, required): Indicates if the certificate policy extension is critical (\"1\" for enabled, \"0\" for disabled).  <br />policyOID (Array, required): An array of objects defining policy OIDs and optional user notice texts.  <br />oid (String, required): The Object Identifier for the policy.  <br />noticeText (String, required): Optional text notice for the policy.  <br />cpsURL (String, required): URL of the Certification Practice Statement.  <br />cpsPolicyOID (String, required): OID for the CPS policy.  <br />sortOrder (String, required): Specifies the order in which this extension is processed.  <br />  <br />ex:-  <br />{  <br />\"isEnabled\": \"0\",  <br />\"isCritical\": \"0\",  <br />\"policyOID\": [  <br />{  <br />\"oid\": \"1.3.24.33.34.34\",  <br />\"noticeText\": \"User Notice\"  <br />}  <br />],  <br />\"cpsURL\": \"<a href=\"http://www.example.com/repository/cps/test.pdf\">http://www.example.com/repository/cps/test.pdf\"</a>,  <br />\"cpsPolicyOID\": \"2.16.356.100.1.8.2\",  <br />\"sortOrder\": \"3\"  <br />}</td>\n</tr>\n<tr>\n<td>crlDistribution</td>\n<td></td>\n<td><strong>crlDistribution</strong>: Provides URLs where the CRL (Certificate Revocation List) can be accessed.  <br />this parameter is a required JSON object that contains specific details such as below  <br />  <br /><strong>isEnabled</strong> (String, required): Indicates if the CRL distribution points extension is enabled (\"1\" for enabled, \"0\" for disabled).  <br /><strong>isCritical</strong> (String, required): Indicates if the CRL distribution points extension is critical (\"1\" for enabled, \"0\" for disabled).  <br /><strong>crlURL</strong> (String, required): URL of the CRL.  <br /><strong>sortOrder</strong> (String, required): Specifies the order in which this extension is processed.  <br />  <br />ex:-  <br />{  <br />\"isEnabled\": \"0\",  <br />\"isCritical\": \"0\",  <br />\"crlURL\": \"<a href=\"http://www.example.com/repository/crls/test.crl\">http://www.example.com/repository/crls/test.crl\"</a>,  <br />\"sortOrder\": \"4\"  <br />}</td>\n</tr>\n<tr>\n<td>keyUsageAttributes*</td>\n<td>JSON</td>\n<td><strong>keyUsageAttributes</strong>: Defines the purpose of the key contained in the certificate, such as signing or enciphering.  <br />this parameter is a required JSON object that contains specific details.  <br />  <br /><strong>isEnabled</strong> (String, required): Indicates if the key usage extension is enabled (\"1\" for enabled, \"0\" for disabled).  <br />  <br /><strong>isCritical</strong> (String, required): Indicates if the key usage extension is critical (\"1\" for enabled, \"0\" for disabled).  <br />  <br /><strong>encipherOnly</strong> (String, required): Indicates if the key is used for enciphering only.  <br />  <br /><strong>nonRepudiation</strong> (String, required): Indicates if the key is used for non-repudiation.  <br />  <br /><strong>digitalSignature</strong> (String, required): Indicates if the key is used for digital signatures.  <br />  <br /><strong>keyEncipherment</strong> (String, required): Indicates if the key is used for key encipherment.  <br />dataEncipherment (String, required): Indicates if the key is used for data encipherment.  <br />  <br /><strong>keyAgreement</strong> (String, required): Indicates if the key is used for key agreement.  <br />keyCertSign (String, required): Indicates if the key is used for signing certificates.  <br />  <br /><strong>crlSign</strong> (String, required): Indicates if the key is used for signing CRLs.  <br />  <br /><strong>decipherOnly</strong> (String, required): Indicates if the key is used for deciphering only.  <br />  <br /><strong>sortOrder</strong> (String, required): Specifies the order in which this extension is processed.  <br />ex:-  <br />{  <br />\"isEnabled\": \"0\",  <br />\"encipherOnly\": \"0\",  <br />\"isCritical\": \"0\",  <br />\"nonRepudiation\": \"0\",  <br />\"digitalSignature\": \"0\",  <br />\"keyEncipherment\": \"0\",  <br />\"dataEncipherment\": \"0\",  <br />\"keyAgreement\": \"0\",  <br />\"keyCertSign\": \"0\",  <br />\"crlSign\": \"0\",  <br />\"decipherOnly\": \"0\",  <br />\"sortOrder\": \"5\"  <br />}</td>\n</tr>\n<tr>\n<td>extendedKeyUsageAttributes</td>\n<td></td>\n<td><strong>extendedKeyUsageAttributes</strong>: Specifies additional key usages for the certificate, such as server authentication or email protection.  <br />  <br />this parameter is a required JSON object that contains specific details.  <br />  <br /><strong>isEnabled</strong> (String, required): Indicates if the extended key usage extension is enabled (\"1\" for enabled, \"0\" for disabled).  <br />  <br /><strong>isCritical</strong> (String, required): Indicates if the extended key usage extension is critical (\"1\" for enabled, \"0\" for disabled).  <br />  <br /><strong>serverAuthentication</strong> (String, required): Indicates if the key is used for server authentication.  <br />  <br /><strong>clientAuthentication</strong> (String, required): Indicates if the key is used for client authentication.  <br />  <br /><strong>codeSigning</strong> (String, required): Indicates if the key is used for code signing.  <br />  <br /><strong>emailProtection</strong> (String, required): Indicates if the key is used for email protection.  <br />  <br /><strong>timeStamping</strong> (String, required): Indicates if the key is used for timestamping.  <br />  <br /><strong>ocspSigning</strong> (String, required): Indicates if the key is used for OCSP signing.  <br />  <br /><strong>msftDocumentSigning</strong> (String, required): Indicates if the key is used for Microsoft document signing.  <br />  <br />smartCardLogon (String, required): Indicates if the key is used for smart card logon.  <br />  <br /><strong>adobeCertifiedDocumentSigning</strong> (String, required): Indicates if the key is used for Adobe certified document signing.  <br />  <br /><strong>encryptionFileSystem</strong> (String, required): Indicates if the key is used for the encryption file system.  <br /><strong>sortOrder</strong> (String, required): Specifies the order in which this extension is processed.  <br />  <br />ex:-  <br />{  <br />\"isEnabled\": \"0\",  <br />\"isCritical\": \"0\",  <br />\"serverAuthentication\": \"0\",  <br />\"clientAuthentication\": \"0\",  <br />\"codeSigning\": \"0\",  <br />\"emailProtection\": \"0\",  <br />\"timeStamping\": \"0\",  <br />\"ocspSigning\": \"0\",  <br />\"msftDocumentSigning\": \"0\",  <br />\"smartCardLogon\": \"0\",  <br />\"adobeCertifiedDocumentSigning\": \"0\",  <br />\"encryptionFileSystem\": \"0\",  <br />\"sortOrder\": \"6\"  <br />}</td>\n</tr>\n<tr>\n<td>subjectKeyIdentifier*</td>\n<td></td>\n<td><strong>subjectKeyIdentifier</strong>: Provides a unique identifier for the certificate's public key.  <br />  <br /><strong>isEnabled</strong> (String, required): Indicates if the subject key identifier extension is enabled (\"1\" for enabled, \"0\" for disabled).  <br /><strong>isCritical</strong> (String, required): Indicates if the subject key identifier extension is critical (\"1\" for enabled, \"0\" for disabled).  <br /><strong>sortOrder</strong> (String, required): Specifies the order in which this extension is processed.  <br />  <br />ex:-  <br />{  <br />\"isEnabled\": \"0\",  <br />\"isCritical\": \"0\",  <br />\"sortOrder\": \"6\"  <br />}</td>\n</tr>\n<tr>\n<td>authorityKeyIdentifier*</td>\n<td></td>\n<td><strong>authorityKeyIdentifier</strong>: Provides a unique identifier for the key used to sign the certificate.  <br />  <br /><strong>isEnabled</strong> (String, required): Indicates if the authority key identifier extension is enabled (\"1\" for enabled, \"0\" for disabled).  <br /><strong>isCritical</strong> (String, required): Indicates if the authority key identifier extension is critical (\"1\" for enabled, \"0\" for disabled).  <br /><strong>sortOrder</strong> (String, required): Specifies the order in which this extension is processed.  <br />  <br />{  <br />\"isEnabled\": \"0\",  <br />\"isCritical\": \"0\",  <br />\"sortOrder\": \"7\"  <br />}</td>\n</tr>\n<tr>\n<td>sanDetails</td>\n<td></td>\n<td><strong>sanDetails</strong>: Specifies the Subject Alternative Name (SAN) attributes, including types and values.  <br />  <br /><strong>isCritical</strong> (String, required): Indicates if the SAN extension is critical (\"1\" for enabled, \"0\" for disabled).  <br />  <br /><strong>isEnabled</strong> (String, required): Indicates if the SAN extension is enabled (\"1\" for enabled, \"0\" for disabled).  <br />  <br /><strong>sortOrder</strong> (String, required): Specifies the order in which this extension is processed.  <br />  <br /><strong>attri</strong>butes (Array, required): An array of objects specifying SAN attributes, each containing:  <br />  <br /><strong>type</strong> (String, required): The type of SAN (e.g., \"rfc822Name\").  <br />  <br /><strong>isMandatory</strong> (String, required): Indicates if the SAN attribute is mandatory.  <br />  <br />ex:-  <br />{  <br />\"isCritical\": \"0\",  <br />\"isEnabled\": \"0\",  <br />\"sortOrder\": \"1\",  <br />\"attributes\": [  <br />{  <br />\"type\": \"rfc822Name\",  <br />\"isMandatory\": \"0\"  <br />}  <br />]  <br />}</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","create","update","user-profile"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"5d2e8010-e146-4a70-be36-e00a9593f86d"},{"name":"createUserCertificate","id":"f1c6ad5c-6601-45d3-8fa9-a0b4a9f34f39","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"}],"body":{"mode":"raw","raw":"{\r\n    \"meta\": {\r\n        \"ver\": \"1.0\",\r\n        \"ts\": \"2024-06-04T11:40:15+05:30\",\r\n        \"txn\": \"3473283142736543345\",\r\n        \"appCode\": \"certinext\",\r\n        \"authKey\": \"702e3cf0a395063f654cbce7b71d0d647fc8816eabeb353170caaab3b3146dd4\"\r\n    },\r\n    \"certificateRequestDetails\": {\r\n        \"certificateProfileID\": \"6\",\r\n        \"csr\": \"MIICzTCCAbUCAQAwgYcxCzAJBgNVBAYTAkdCMRYwFAYDVQQIEw1TdGFmZm9yZHNoaXJlMRcwFQYDVQQHEw5TdG9rZSBvbiBUcmVudDEjMCEGA1UEChMaUmVkIEtlc3RyZWwgQ29uc3VsdGluZyBMdGQxIjAgBgNVBAMTGXRlc3RjZXJ0LnJlZGtlc3RyZWwuY28udWswggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDWLeW88IeAIa3n23R99i874fh0jetf+STsGPgkfGXGJ++tclKGk3MJE0ijD4PNaxGXUCNULgn2ROyybm5sTmGzpEOD+1AAAyV+pLQoFNkHEFuudGqVM6XkPWfqaM2vKvdzUbPPC0X/MfDFGPxc8AY3TUM385c9c9/WOIF6NUcAvAFIQF0zG7evzJZBqDb4enUnatMSLHmxRWMi1JeHtfLINXhNitHewEQWgIB3j1xmh7CPO5FeTb6HzQDxc+f7uMisY6s9J/Ph3GeOCeIDooqU8jnfV5eGEzIMH5CFMZjajrNKF4DYK3YRyUI0K66+v0KILoUntEs++M20LhOn+VE9AgMBAAGgADANBgkqhkiG9w0BAQUFAAOCAQEAUWE7oBX3SLjYNM53bsBOlNGnsgAp1P1fiCPpEKaZGEOUJ2xOguIHSu1N1ZigKpWmiAAZxuoagW1R/ANM3jXpvCLVBRv40AHCFsot9udrdCYjI43aDHAaYvLmT4/Pvpntcn0/7+g//elAHhr9UIooMZwwwo6yom67Jwfw/be/g7Mae7mPHZ2lsQTS02hEeqVynIRk2W9meQULrt+/atog0mqJSBx0WswtHliTc+nXFpQrwFIEzVuPGCOVw7LmCfNmHNCkZVuRSJB/9MdLmrfwchPI3NeTGSe+BZfsOtpt2/7j+bqeYKFu8B0stLoJBEnihxUoV18uZOmOeuVuX1N6nA==\",\r\n        \"subCAID\": \"2\",\r\n        \"subjectAttributes\": [\r\n            {\r\n                \"value\": \"test user cert\",\r\n                \"oid\": \"2.5.4.3\",\r\n                \"isMandatory\": \"1\",\r\n                \"dataType\": \"PrintableString\"\r\n            }\r\n        ],\r\n        \"validityCriteria\": \"d\",\r\n        \"validityValue\": \"365\"\r\n    }\r\n}","options":{"raw":{"language":"json"}}},"url":"https://appemca.emudhra.com/emCAServices431/rest/request/user-certificate","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The \"<strong>createUserCertificate</strong>\" API is used to generate a user certificate based on the provided input parameters. The request includes details such as the certificate profile ID, CSR, SAN attributes, subordinate CA ID, subject attributes, and validity details. The generated user certificate can be returned in base64 encoded X509 format along with the chain of certificates.</p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>meta*</td>\n<td>JSON</td>\n<td>The <strong>meta</strong> parameter is a required JSON object that contains external user details necessary for processing the request.  <br />  <br />please refer table <strong>Meta Object Fields</strong> from above  <br />  <br />ex:-  <br />{  <br />\"ver\": \"1.0\",  <br />\"ts\": \"2024-01-01T11:40:15+05:30\",  <br />\"txn\": \"347328314273\",  <br />\"appCode\": \"TestApp\",  <br />\"authKey\": \"0e56ea59a73102605346cdb2a6ee61e1ab6ddb1d4785d8d5f16401bfa03516a7\"  <br />}</td>\n</tr>\n<tr>\n<td>certificateRequestDetails*</td>\n<td>JSON</td>\n<td>The certificateRequestDetails parameter is a required JSON object that contains specific details about the certificate to be generated.  <br />  <br />refer <strong>Table no 1</strong></td>\n</tr>\n</tbody>\n</table>\n</div><p><strong>Table no 1</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>certificateProfileID*</td>\n<td>String</td>\n<td><strong>certificateProfileID</strong> (String, required): The unique identifier for the certificate template to be used for certificate generation.  <br />  <br />ex:- \"2\", \"5\"</td>\n</tr>\n<tr>\n<td>subCAID*</td>\n<td>String</td>\n<td>The ID of the sub CA.  <br />  <br />ex:- \"2\", \"5\"</td>\n</tr>\n<tr>\n<td>csr*</td>\n<td>String</td>\n<td><strong>csr</strong> (String, required): The Certificate Signing Request (CSR) in string format.  <br />  <br />ex:- \"MIICzTCCAbUCAQAwgYcxCzAJBgN.................ZfsOtpt2/7j+bqeYKFu8B0stLoJBEnihxUoV18uZOmOeuVuX1N6nA==\"</td>\n</tr>\n<tr>\n<td>validityCriteria*</td>\n<td>String</td>\n<td><strong>validityCriteria</strong> (String, required): The criteria for the certificate's validity, such as \"days\", \"months\", or \"years\".  <br />  <br />ex:- \"days\"</td>\n</tr>\n<tr>\n<td>validityValue*</td>\n<td>String</td>\n<td><strong>validityValue :</strong> The value corresponding to the validity criteria (e.g., 365 for 365 days).  <br />  <br />ex:-\"365\"</td>\n</tr>\n<tr>\n<td>subjectAttributes*</td>\n<td>ArrayList of Object</td>\n<td><strong>subjectAttributes (Array, required)</strong>: An array of objects containing the subject attributes of the certificate. Each object includes:  <br />  <br /><strong>oid</strong> (String, required): The Object Identifier (OID) for the attribute.  <br /><strong>value</strong> (String, required): The value of the attribute.  <br />  <br />ex:-  <br />[  <br />{  <br />\"oid\": \"2.5.4.3\",  <br />\"value\": \"common name\"  <br />},  <br />\"oid\": \"2.5.4.6\",  <br />\"value\": \"IN\"  <br />}  <br />]</td>\n</tr>\n<tr>\n<td>sanAttributes</td>\n<td>ArrayList of Object</td>\n<td><strong>sanAttributes</strong> (Array, optional): An array of objects specifying the Subject Alternative Name (SAN) attributes. Each object includes:  <br />  <br /><strong>type</strong> (String, required): The type of SAN attribute, such as \"rfc822Name\".  <br />  <br /><strong>value</strong> (String, required): The value of the SAN attribute.  <br />  <br />ex:-  <br />[  <br />{  <br />\"type\": \"rfc822Name\",  <br />\"value\": \"<a href=\"https://mailto:test@test.com\">test@test.com</a>\"  <br />},  <br />\"type\": \"dnsName\",  <br />\"value\": \"<a href=\"http://www.example.com\">www.example.com\"</a>  <br />}  <br />]</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","request","user-certificate"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"f1c6ad5c-6601-45d3-8fa9-a0b4a9f34f39"}],"id":"c28c3573-571c-4c9a-a3f1-42a43828f4e6","description":"<p>The CA Management APIs for the Certifying Authority (CA) facilitate comprehensive management of digital certificates, enabling tasks such as issuance, renewal, revocation, and validation. These APIs provide secure, programmatic access to CA functions, ensuring seamless integration with existing systems for automated certificate lifecycle management. They support both RSA and ECC algorithms, and adhere to industry standards for security and interoperability, streamlining the process of maintaining robust and compliant public key infrastructures (PKI).</p>\n<p>To ensure clarity and consistency across your CA Management APIs, a <strong>meta object</strong> can be standardized in both request and response structures, including security headers like <strong><code>X-Nonce</code></strong> for replay attack prevention.</p>\n<ul>\n<li><strong><code>X-Nonce</code></strong>: A unique, per-request identifier used to prevent replay attacks by ensuring freshness and uniqueness.</li>\n</ul>\n<p>Here's how you can describe the <strong>meta object</strong> for documentation and implementation across all your APIs.</p>\n<h1 id=\"meta-object-fields\"><strong>Meta Object Fields</strong></h1>\n<p>The \"<strong>meta</strong>\" object must be included as a parameter in all API requests to maintain consistency and security across the system.</p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>ver*</td>\n<td>String</td>\n<td><strong>ver</strong> : Specifies the version of the API or request. This helps in ensuring compatibility and proper handling of the request.  <br />  <br />ex:- \"1.0\"</td>\n</tr>\n<tr>\n<td>ts*</td>\n<td>String</td>\n<td><strong>ts</strong> : Records the time when the request was made. This is crucial for tracking and logging purposes. Format: ISO 8601 ex:-  <br />\"2024-01-01T11:40:15+05:30\"</td>\n</tr>\n<tr>\n<td>txn*</td>\n<td>String</td>\n<td><strong>txn</strong> : A unique identifier for the transaction. This ID helps in uniquely identifying and tracking the request across different systems.  <br />  <br />ex:- 347328314273</td>\n</tr>\n<tr>\n<td>appCode*</td>\n<td>String</td>\n<td><strong>appCode</strong> : Represents the application code that is making the request. It helps in identifying which application or service initiated the request.  <br />  <br />ex:- \"MYAPP\"</td>\n</tr>\n<tr>\n<td>authKey*</td>\n<td>String</td>\n<td><strong>authKey</strong> : An authentication key used to verify the legitimacy of the request. This key ensures that only authorized entities can make requests to the API.  <br />  <br />The auth key is generated by applying the SHA256 hash to the concatenation of the ClientID, request timestamp (ts), and request unique transaction ID (txn).(SHA256(clientid+ts+txn)  <br />  <br />ex:-  <br />\"0e56ea59a73102605346cdb2a6ee61e1ab6ddb1d4785d8d5f16401bfa03516a7\"</td>\n</tr>\n</tbody>\n</table>\n</div>","event":[{"listen":"prerequest","script":{"type":"text/javascript","packages":{},"exec":[""],"id":"65ffcc8b-f9d5-4bbd-8914-4881498d65a9"}},{"listen":"test","script":{"type":"text/javascript","packages":{},"exec":[""],"id":"7c370b62-8a1f-4a1a-8118-12b7474272b8"}}],"_postman_id":"c28c3573-571c-4c9a-a3f1-42a43828f4e6"},{"name":"Certificate Management","item":[{"name":"getJwt-token","event":[{"listen":"prerequest","script":{"exec":[""],"type":"text/javascript","packages":{},"id":"08b028b2-f79c-494c-bbab-0ea93f57aa1f"}}],"id":"04703f23-83cb-4f44-9e3e-abc468d5ce4b","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"}],"body":{"mode":"raw","raw":"{\r\n  \"username\": \"TestUser\",\r\n  \"password\": \"eMudhra@1\",\r\n  \"clientId\": \"0cad7eec-5b4b-4758-8157-8e28d2aee7e0\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://appemca.emudhra.com/emCAServices431/rest/authenticate/getJwt-token","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>Authentication for Certificate Management in emCA REST APIs is handled using a JWT token with a configurable expiry time. This token must be included in the header of every request to the APIs for authentication.</p>\n<p>To obtain a JWT token for the Certificate Management REST APIs, users need to provide their registered username (appCode), password, and clientId to the API.</p>\n<h3 id=\"prerequisites\">Prerequisites</h3>\n<ol>\n<li><p><strong>Register Your Application</strong>: Ensure your application is registered as an external application in emCA before using the API.</p>\n</li>\n<li><p><strong>Share Credentials</strong>: As part of the registration process, provide the emCA team with your username (appCode), password, and IP address.</p>\n</li>\n<li><p><strong>Obtain clientId</strong>: Receive the clientId from Team emCA upon registering an external application user.</p>\n</li>\n</ol>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<p>Table no 1</p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>username*</td>\n<td>String</td>\n<td>Username (appCode) which is used as part of External Application Registartion at emCA.  <br />  <br />ex:- \"certinext\"</td>\n</tr>\n<tr>\n<td>password*</td>\n<td>String</td>\n<td>Password which is used as part of External Application Registartion at emCA.  <br />  <br />ex:- \"P@ssw0rd\"</td>\n</tr>\n<tr>\n<td>clientId*</td>\n<td>String</td>\n<td>ClientID. Received from team emCA post successful Registration  <br />  <br />ex:- \"924e5g30-8cea-4bf4-be77-4b0e160dbaf9\"</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","authenticate","getJwt-token"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"04703f23-83cb-4f44-9e3e-abc468d5ce4b"},{"name":"createCertificate","event":[{"listen":"prerequest","script":{"exec":[""],"type":"text/javascript","packages":{},"id":"903e2fc6-f3aa-4969-85b1-84981dead1f7"}}],"id":"ce627db5-7c63-4570-9cf7-fa88e5344aea","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Client-ID","value":"{{x_client_id}}","type":"text"},{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"},{"key":"X-Emca-Api-Key","value":"{{x_emca_api_key}}","type":"text"}],"body":{"mode":"raw","raw":"{\r\n  \"profile\": \"2\",\r\n  \"output\": \"X509\",\r\n  \"csr\": \"MIICzTCCAbUCAQAwgYcxCzAJBgNVBAYTAkdCMRYwFAYDVQQIEw1TdGFmZm9yZHNoaXJlMRcwFQYDVQQHEw5TdG9rZSBvbiBUcmVudDEjMCEGA1UEChMaUmVkIEtlc3RyZWwgQ29uc3VsdGluZyBMdGQxIjAgBgNVBAMTGXRlc3RjZXJ0LnJlZGtlc3RyZWwuY28udWswggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDWLeW88IeAIa3n23R99i874fh0jetf+STsGPgkfGXGJ++tclKGk3MJE0ijD4PNaxGXUCNULgn2ROyybm5sTmGzpEOD+1AAAyV+pLQoFNkHEFuudGqVM6XkPWfqaM2vKvdzUbPPC0X/MfDFGPxc8AY3TUM385c9c9/WOIF6NUcAvAFIQF0zG7evzJZBqDb4enUnatMSLHmxRWMi1JeHtfLINXhNitHewEQWgIB3j1xmh7CPO5FeTb6HzQDxc+f7uMisY6s9J/Ph3GeOCeIDooqU8jnfV5eGEzIMH5CFMZjajrNKF4DYK3YRyUI0K66+v0KILoUntEs++M20LhOn+VE9AgMBAAGgADANBgkqhkiG9w0BAQUFAAOCAQEAUWE7oBX3SLjYNM53bsBOlNGnsgAp1P1fiCPpEKaZGEOUJ2xOguIHSu1N1ZigKpWmiAAZxuoagW1R/ANM3jXpvCLVBRv40AHCFsot9udrdCYjI43aDHAaYvLmT4/Pvpntcn0/7+g//elAHhr9UIooMZwwwo6yom67Jwfw/be/g7Mae7mPHZ2lsQTS02hEeqVynIRk2W9meQULrt+/atog0mqJSBx0WswtHliTc+nXFpQrwFIEzVuPGCOVw7LmCfNmHNCkZVuRSJB/9MdLmrfwchPI3NeTGSe+BZfsOtpt2/7j+bqeYKFu8B0stLoJBEnihxUoV18uZOmOeuVuX1N6nA==\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://appemca.emudhra.com/emCAServices431/rest/createCertificate","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The \"createCertificate\" API is used to generate an X509 certificate for the provided CSR (PKCS10). The generated certificate can be returned either in base64 encoded X509 format or as a PEM, based on the specified requirements.</p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<p><strong>Table no 1</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>profile*</td>\n<td>String</td>\n<td>A Certificate Profile name or Certificate Profile ID is a unique profile or template created for certificates. Profiles can be created by an admin on emCA or using the CA Management APIs.  <br />  <br />ex:- \"5\", \"SSL Certificate\"</td>\n</tr>\n<tr>\n<td>output*</td>\n<td>String</td>\n<td>Output defines the format of the certificate:  <br />X509: Base64 encoded X509 Certificate (without certificate chain).  <br />PEM: PEM format with certificate chain.  <br />  <br />ex:- \"X509\" or \"PEM\"</td>\n</tr>\n<tr>\n<td>csr*</td>\n<td>String</td>\n<td>Certificate Signing Request (#PKCS10)  <br />  <br />ex:-  <br />\"MIICzTCCAbUCAQAwgYcxCzAJBgNV..........GSe+BZfsOtpt2/7j+bqeYKFu8B0stLoJBEnihxUoV18uZOmOeuVuX1N6nA==\"</td>\n</tr>\n<tr>\n<td>subscriberID</td>\n<td>Integer</td>\n<td>A Unique ID for the Subscribers/Devices uniquely identifies the Subscriber/Device.  <br />The value should only be a positive integer within the allowed range and up from 1 to 10 characters in length.  <br />  <br />ex:- 12345  <br />Max :</td>\n</tr>\n<tr>\n<td>txnID</td>\n<td>Long</td>\n<td>The Transaction ID uniquely identifies the transaction.  <br />  <br />The value should only be a positive integer within the allowed range and upfrom 1 to 19 characters in length.  <br />  <br />ex:- 876545675</td>\n</tr>\n<tr>\n<td>validity</td>\n<td>JSON</td>\n<td>Certificate validity can be defined only if the profile supports custom validity.  <br />  <br />The validity should be less than the validity periods of both the profile and the issuer.  <br />  <br />Ex:-  <br />{  <br />\"days\": 365,  <br />\"hours\": 0,  <br />\"minutes\": 0,  <br />\"seconds\": 0  <br />}</td>\n</tr>\n<tr>\n<td>validfrom</td>\n<td>JSON</td>\n<td>Certificate validity can be defined starting from a specific date if the profile is enabled for custom validity.  <br />  <br />Validation for the validfrom field is as follows:  <br />  <br />validfrom should not be a past date.  <br />day - day of the month (1-31)  <br />month - month of the year (1-12)  <br />year - four-digit year (e.g., 2024)  <br />hour - hour of the day (0-23)  <br />minute - minute of the hour (0-59)  <br />second - second of the minute (0-59)\"  <br />  <br />ex:-  <br />{  <br />\"day\": 1,  <br />\"month\": 1,  <br />\"year\": 2024,  <br />\"hour\": 0,  <br />\"minute\": 0,  <br />\"second\": 0  <br />}</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","createCertificate"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"ce627db5-7c63-4570-9cf7-fa88e5344aea"},{"name":"createCertificates","id":"7b1fab76-bcf8-400c-a65e-be2bfce91535","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Emca-Api-Key","value":"{{x_emca_api_key}}","type":"text"},{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"},{"key":"X-Client-ID","value":"{{x_client_id}}","type":"text"}],"body":{"mode":"raw","raw":"{\r\n    \"profile\": \"2\",\r\n    \"output\": \"X509\",\r\n    \"csrInfo\": [\r\n        {\r\n            \"referenceId\": \"1001\",\r\n            \"csr\": \"MIICzTCCAbUCAQAwgYcxCzAJBgNVBAYTAkdCMRYwFAYDVQQIEw1TdGFmZm9yZHNoaXJlMRcwFQYDVQQHEw5TdG9rZSBvbiBUcmVudDEjMCEGA1UEChMaUmVkIEtlc3RyZWwgQ29uc3VsdGluZyBMdGQxIjAgBgNVBAMTGXRlc3RjZXJ0LnJlZGtlc3RyZWwuY28udWswggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDWLeW88IeAIa3n23R99i874fh0jetf+STsGPgkfGXGJ++tclKGk3MJE0ijD4PNaxGXUCNULgn2ROyybm5sTmGzpEOD+1AAAyV+pLQoFNkHEFuudGqVM6XkPWfqaM2vKvdzUbPPC0X/MfDFGPxc8AY3TUM385c9c9/WOIF6NUcAvAFIQF0zG7evzJZBqDb4enUnatMSLHmxRWMi1JeHtfLINXhNitHewEQWgIB3j1xmh7CPO5FeTb6HzQDxc+f7uMisY6s9J/Ph3GeOCeIDooqU8jnfV5eGEzIMH5CFMZjajrNKF4DYK3YRyUI0K66+v0KILoUntEs++M20LhOn+VE9AgMBAAGgADANBgkqhkiG9w0BAQUFAAOCAQEAUWE7oBX3SLjYNM53bsBOlNGnsgAp1P1fiCPpEKaZGEOUJ2xOguIHSu1N1ZigKpWmiAAZxuoagW1R/ANM3jXpvCLVBRv40AHCFsot9udrdCYjI43aDHAaYvLmT4/Pvpntcn0/7+g//elAHhr9UIooMZwwwo6yom67Jwfw/be/g7Mae7mPHZ2lsQTS02hEeqVynIRk2W9meQULrt+/atog0mqJSBx0WswtHliTc+nXFpQrwFIEzVuPGCOVw7LmCfNmHNCkZVuRSJB/9MdLmrfwchPI3NeTGSe+BZfsOtpt2/7j+bqeYKFu8B0stLoJBEnihxUoV18uZOmOeuVuX1N6nA==\"\r\n        },\r\n        {\r\n            \"referenceId\": \"1002\",\r\n            \"csr\": \"MIIBLzCB1gIBADB0MSkwJwYJKoZIhvcNAQkBFhp0YW5tb3kucHJhZGhhbkBlbXVkaHJhLmNvbTENMAsGA1UEERMEbnVsbDEPMA0GA1UEAxMGVGFubW95MREwDwYDVQQKEwhQZXJzb25hbDEJMAcGA1UECBMAMQkwBwYDVQQGEwAwWTATBgcqhkjOPQIBBggqhkjOPQMBBwNCAAT+EAJgUf75U/UQ12h7ZR9AH4GLGByNOvgu4y/vQIKRkqZeY028EerKzpKjhhL4Ocb8CyNIl/pPElgRJzHawNBDoAAwCgYIKoZIzj0EAwIDSAAwRQIhAPABaUje1TrCD+RqlV4UFvo/pFO3GiMvr989qa8cZfBTAiBLhbbqAo/fx3fdKKahwuLMfbL2dvQXgMHFOdXiR0/oOA==\"\r\n        }\r\n    ]\r\n}","options":{"raw":{"language":"json"}}},"url":"https://appemca.emudhra.com/emCAServices431/rest/createCertificates","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The \"createCertificates\" API is designed to generate multiple X509 Certificates based on up to 10 provided Certificate Signing Requests (CSRs). This API allows for the creation of certificates in either Base64 encoded X509Certificates or PEM. It enables efficient management and creation of multiple certificates simultaneously.</p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<p>Table no 1</p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>profile*</td>\n<td>String</td>\n<td>A Certificate Profile name or Certificate Profile ID is a unique profile or template created for certificates. Profiles can be created by an admin on emCA or using the CA Management APIs.  <br />  <br />ex:- \"5\", \"SSL Certificate\"</td>\n</tr>\n<tr>\n<td>output*</td>\n<td>String</td>\n<td>Output defines the format of the certificate:  <br />X509: Base64 encoded X509 Certificate (without certificate chain).  <br />PEM: PEM format with certificate chain.  <br />  <br />ex:- \"X509\" or \"PEM\"</td>\n</tr>\n<tr>\n<td>csrInfo*</td>\n<td>ArrayList</td>\n<td>A JSON object of csr needs to be passed in an ArrayList for bulk signing. Each csrInfo object should include the necessary details for creating an X509 Certificate, allowing the API to process multiple Certificate Signing Requests (CSRs) simultaneously, up to a maximum of 10 CSRs  <br />  <br />referenceId : Unique Id for CSR.  <br />  <br />ex:-  <br />[  <br />{  <br />\"referenceId\": \"1001\",  <br />\"csr\": \"MIICzTCCAbUCAQAwgYcxCzAJBgN............NeTGSe+BZfsOtpt2/7j+bqeYKFu8B0stLoJBEnihxUoV18uZOmOeuVuX1N6nA==\"  <br />},  <br />{  <br />\"referenceId\": \"1002\",  <br />\"csr\": \"MIICzTCCAbUCAQAwgYcxCzAJBgN............NeTGSe+BZfsOtpt2/7j+bqeYKFu8B0stLoJBEnihxUoV18uZOmOeuVuX1N6nA==\"  <br />}  <br />]</td>\n</tr>\n<tr>\n<td>subscriberID</td>\n<td>Integer</td>\n<td>A Unique ID for the Subscribers/Devices uniquely identifies the Subscriber/Device.  <br />The value should only be a positive integer within the allowed range and up from 1 to 10 characters in length.  <br />  <br />ex:- 12345</td>\n</tr>\n<tr>\n<td>txnID</td>\n<td>Long</td>\n<td>The Transaction ID uniquely identifies the transaction.  <br />  <br />The value should only be a positive integer within the allowed range and upfrom 1 to 19 characters in length.  <br />  <br />ex:- 876545675</td>\n</tr>\n<tr>\n<td>validity</td>\n<td>JSON</td>\n<td>Certificate validity can be defined only if the profile supports custom validity.  <br />  <br />The validity should be less than the validity periods of both the profile and the issuer.  <br />  <br />Ex:-  <br />{  <br />\"days\": 365,  <br />\"hours\": 0,  <br />\"minutes\": 0,  <br />\"seconds\": 0  <br />}</td>\n</tr>\n<tr>\n<td>validfrom</td>\n<td>JSON</td>\n<td>Certificate validity can be defined starting from a specific date if the profile is enabled for custom validity.  <br />  <br />Validation for the validfrom field is as follows:  <br />  <br />validfrom should not be a past date.  <br />day - day of the month (1-31)  <br />month - month of the year (1-12)  <br />year - four-digit year (e.g., 2024)  <br />hour - hour of the day (0-23)  <br />minute - minute of the hour (0-59)  <br />second - second of the minute (0-59)\"  <br />  <br />ex:-  <br />{  <br />\"day\": 1,  <br />\"month\": 1,  <br />\"year\": 2024,  <br />\"hour\": 0,  <br />\"minute\": 0,  <br />\"second\": 0  <br />}</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","createCertificates"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"7b1fab76-bcf8-400c-a65e-be2bfce91535"},{"name":"createCustomCertificate","id":"9fd95586-0b95-4836-9288-bb24067ccc69","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Client-ID","value":"{{x_client_id}}","type":"text"},{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"},{"key":"X-Emca-Api-Key","value":"{{x_emca_api_key}}","type":"text"}],"body":{"mode":"raw","raw":"{\r\n    \"profile\": \"3\",\r\n    \"subjectDN\": {\r\n        \"commonName\": \"test\",\r\n        \"country\": \"IN\"\r\n    },\r\n    \"eSign\": \"No\",\r\n    \"output\": \"X509\",\r\n    \"csr\": \"MIIBLzCB1gIBADB0MSkwJwYJKoZIhvcNAQkBFhp0YW5tb3kucHJhZGhhbkBlbXVkaHJhLmNvbTENMAsGA1UEERMEbnVsbDEPMA0GA1UEAxMGVGFubW95MREwDwYDVQQKEwhQZXJzb25hbDEJMAcGA1UECBMAMQkwBwYDVQQGEwAwWTATBgcqhkjOPQIBBggqhkjOPQMBBwNCAAT+EAJgUf75U/UQ12h7ZR9AH4GLGByNOvgu4y/vQIKRkqZeY028EerKzpKjhhL4Ocb8CyNIl/pPElgRJzHawNBDoAAwCgYIKoZIzj0EAwIDSAAwRQIhAPABaUje1TrCD+RqlV4UFvo/pFO3GiMvr989qa8cZfBTAiBLhbbqAo/fx3fdKKahwuLMfbL2dvQXgMHFOdXiR0/oOA==\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://appemca.emudhra.com/emCAServices431/rest/createCustomCertificate","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The '<strong>createCustomCertificate'</strong> API facilitates the creation of X509 Certificates or PEM by accepting a CSR (#PKCS10) along with additional parameters such as Subject Distinguished Name (DN) and Subject Alternative Name (SAN) details. This API allows for the customization of certificate attributes, enabling the creation of certificates tailored to specific requirements and ensuring flexibility in certificate management.</p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<p><strong>Table no 1</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>profile*</td>\n<td>String</td>\n<td>A Certificate Profile name or Certificate Profile ID is a unique profile or template created for certificates. Profiles can be created by an admin on emCA or using the CA Management APIs.  <br />  <br />ex:- \"5\", \"SSL Certificate\"</td>\n</tr>\n<tr>\n<td>eSign*</td>\n<td>String</td>\n<td>To increase throughput, set this option to 'Yes'. This configuration ensures the application loads all necessary details upfront, such as profiles, and reuses them for all requests, thereby enhancing performance. This approach is commonly used for eSign transactions. Alternatively, set it to 'No'.  <br />  <br />ex:- \"No\" or \"Yes\"</td>\n</tr>\n<tr>\n<td>subjectDN*</td>\n<td>JSON</td>\n<td>Subject dn details which need to be added as part of the certificate.  <br />  <br />ex:  <br />{  <br />\"commonName\": \"test\",  <br />\"country\":\"IN\",  <br />\"oids\": [  <br />{  <br />\"oid\": \"2.5.4.7\",  <br />\"value\": \"test\"  <br />}  <br />]  <br />}  <br />ref :- <strong>Tabel no 2</strong></td>\n</tr>\n<tr>\n<td>csr*</td>\n<td>String</td>\n<td>Certificate Signing Request (#PKCS10)  <br />  <br />ex:-  <br />\"MIICzTCCAbUCAQAwgYcxCzAJBgNV......................u8B0stLoJBEnihxUoV18uZOmOeuVuX1N6nA==\"</td>\n</tr>\n<tr>\n<td>san</td>\n<td>JSON</td>\n<td>Subject Alternative Name which need to be added as part of the certificate.  <br />  <br />ref:- <strong>Table no 3</strong>  <br />ex: -  <br />{  <br />\"rfc822Name\": \"<a href=\"https://mailto:test@test.com\">keven.s@ta.co.in</a>\",  <br />\"dnsName\": \"<a href=\"http://www.example.com\">www.example.com\"</a>,  <br />\"ipAddress\": \"127.0.0.1\",  <br />\"url\": \"<a href=\"https://www.google.com\">https://www.emudhra.com\"</a>,  <br />\"registeredID\": \"2.10.100.2.3.4\", \"directoryName\": \"L=IAO\"  <br />}</td>\n</tr>\n<tr>\n<td>txnID</td>\n<td>Long</td>\n<td>The Transaction ID uniquely identifies the transaction.  <br />  <br />The value should only be a positive integer within the allowed range and upfrom 1 to 19 characters in length.  <br />  <br />ex:- 876545675</td>\n</tr>\n<tr>\n<td>subscriberID</td>\n<td>Integer</td>\n<td>A Unique ID for the Subscribers/Devices uniquely identifies the Subscriber/Device.  <br />The value should only be a positive integer within the allowed range and up from 1 to 10 characters in length.  <br />  <br />ex:- 12345</td>\n</tr>\n<tr>\n<td>validity</td>\n<td>JSON</td>\n<td>Certificate validity can be defined only if the profile supports custom validity.  <br />  <br />The validity should be less than the validity periods of both the profile and the issuer.  <br />  <br />Ex:-  <br />{  <br />\"days\": 365,  <br />\"hours\": 0,  <br />\"minutes\": 0,  <br />\"seconds\": 0  <br />}</td>\n</tr>\n<tr>\n<td>validfrom</td>\n<td>JSON</td>\n<td>Certificate validity can be defined starting from a specific date if the profile is enabled for custom validity.  <br />  <br />Validation for the validfrom field is as follows:  <br />  <br />validfrom should not be a past date.  <br />day - day of the month (1-31)  <br />month - month of the year (1-12)  <br />year - four-digit year (e.g., 2024)  <br />hour - hour of the day (0-23)  <br />minute - minute of the hour (0-59)  <br />second - second of the minute (0-59)\"  <br />  <br />ex:-  <br />{  <br />\"day\": 1,  <br />\"month\": 1,  <br />\"year\": 2024,  <br />\"hour\": 0,  <br />\"minute\": 0,  <br />\"second\": 0  <br />}</td>\n</tr>\n</tbody>\n</table>\n</div><p><strong>Tabel no 2</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>commonName</td>\n<td>String</td>\n<td>Validation for the CN field as below  <br />A character length of minimum 2 and maximum 64 characters  <br />A lowercase or uppercase English letter (from \"a\" to \"z\" and \"A\" to \"Z\").  <br />A digit (from \"0\" to \"9\").  <br />A hyphen (\"-\").  <br />A period (\".\").  <br />An apostrophe (\"'\").  <br />An asterisk (\"*\").  <br />An underscore (\"_\").  <br />At sign (\"@\")  <br />A space (\" \").  <br />  <br />ex:- \"keven\", \"123\", \"abc123\"</td>\n</tr>\n<tr>\n<td>country</td>\n<td>String</td>\n<td>Validation for the Country field as below  <br />A character length of minimum 2 and maximum 75 characters  <br />A lowercase or uppercase English letter (from \"a\" to \"z\" and \"A\" to \"Z\").  <br />ex:- \"IN\", \"India\"</td>\n</tr>\n<tr>\n<td>organisation</td>\n<td>String</td>\n<td>Validation for the this field as below  <br />A character length of minimum 2 and maximum 75 characters  <br />A lowercase or uppercase English letter (from \"a\" to \"z\" and \"A\" to \"Z\").  <br />  <br />ex:- \"emudhra\", \"Test org\"</td>\n</tr>\n<tr>\n<td>organisationUnit</td>\n<td>String</td>\n<td>Validation for the this field as below  <br />A character length of minimum 2 and maximum 75 characters  <br />A lowercase or uppercase English letter (from \"a\" to \"z\" and \"A\" to \"Z\").  <br />It will accept multiple OU values separated by commas(\",\").  <br />  <br />ex:- \"emudhra ltd\",  <br />\"ESS,TECH\"</td>\n</tr>\n<tr>\n<td>postalCode</td>\n<td>String</td>\n<td>Validation for the postal code field as below  <br />A character length of minimum 4 and maximum 64 characters  <br />A digit (from \"0\" to \"9\").  <br />  <br />ex:- \"560063\"</td>\n</tr>\n<tr>\n<td>stateOrProvince</td>\n<td>String</td>\n<td>Validation for the state field as below  <br />A character length of minimum 2 and maximum 75 characters  <br />A lowercase or uppercase English letter (from \"a\" to \"z\" and \"A\" to \"Z\").  <br />  <br />ex:- \"KA\", \"texas\"</td>\n</tr>\n<tr>\n<td>street</td>\n<td>String</td>\n<td>Validation for the this field as below  <br />A character length of minimum 2 and maximum 75 characters  <br />A lowercase or uppercase English letter (from \"a\" to \"z\" and \"A\" to \"Z\").  <br />  <br />ex:-\"abc street\"</td>\n</tr>\n<tr>\n<td>houseIdentifier</td>\n<td>String</td>\n<td>Validation for the this field as below  <br />A character length of minimum 2 and maximum 75 characters  <br />A lowercase or uppercase English letter (from \"a\" to \"z\" and \"A\" to \"Z\").  <br />  <br />ex:- \"xyz\"</td>\n</tr>\n<tr>\n<td>serialNumber</td>\n<td>String</td>\n<td>Validation for the this field as below  <br />A character length of minimum 2 and maximum 75 characters  <br />A lowercase or uppercase English letter (from \"a\" to \"z\" and \"A\" to \"Z\").  <br />  <br />ex:- \"fff44f43224c43\"</td>\n</tr>\n<tr>\n<td>uniqueIdentifier</td>\n<td>String</td>\n<td>Validation for the this field as below  <br />A character length of minimum 2 and maximum 75 characters  <br />A lowercase or uppercase English letter (from \"a\" to \"z\" and \"A\" to \"Z\").  <br />  <br />ex:- \"774434cvfc45\"</td>\n</tr>\n<tr>\n<td>pseudonym</td>\n<td>String</td>\n<td>Validation for the this field as below  <br />A character length of minimum 2 and maximum 75 characters  <br />A lowercase or uppercase English letter (from \"a\" to \"z\" and \"A\" to \"Z\").  <br />  <br />ex:- \"John Doe\"</td>\n</tr>\n<tr>\n<td>telephoneNumber</td>\n<td>String</td>\n<td>SHA256 of Telephone Number  <br />ex:- \"9cd24231c813f6608bcf717e15b76700a80e2170fbf235e5ff344dae948bbfec\"</td>\n</tr>\n<tr>\n<td>title</td>\n<td>String</td>\n<td>Validation for the this field as below  <br />A character length of minimum 2 and maximum 75 characters  <br />A lowercase or uppercase English letter (from \"a\" to \"z\" and \"A\" to \"Z\").  <br />  <br />ex:- \"Data Analyst\"</td>\n</tr>\n<tr>\n<td>email</td>\n<td>String</td>\n<td>A character length of minimum 2 and maximum 64 characters  <br />A lowercase or uppercase English letter (from \"a\" to \"z\" and \"A\" to \"Z\").  <br />A digit (from \"0\" to \"9\").  <br />A hyphen (\"-\").  <br />A period (\".\").  <br />An underscore (\"_\").  <br />At sign (\"@\")  <br />  <br />ex:- \"<a href=\"https://mailto:test@test.com\">jhon.ken@co.in\"</a></td>\n</tr>\n<tr>\n<td>oids</td>\n<td>ArrayList</td>\n<td>Pass additional subject DN details using the OIDs. You can provide multiple OIDs in an array object.  <br />  <br />Refer <strong>Table no 4</strong>  <br />  <br />ex:-  <br />[  <br />{  <br />\"oid\": \"2.5.4.7\",  <br />\"value\": \"Bengalureu\"  <br />}  <br />]</td>\n</tr>\n</tbody>\n</table>\n</div><p><strong>Tabel no 3</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>rfc822Name</td>\n<td>String</td>\n<td>\"<strong>rfc822Name</strong>\" refers to an email address formatted according to RFC 822 standards  <br />ex:-  <br /><a href=\"https://mailto:test@test.com\">\"vikram.s@outlook.com\"</a></td>\n</tr>\n<tr>\n<td>dnsName</td>\n<td>String</td>\n<td>\"<strong>dnsName</strong>\" refers to a domain name system (DNS) name. It identifies a domain or hostname associated with an entity or resource, allowing secure communication over networks while validating the identity of servers and services.  <br />  <br />ex:- \"<a href=\"http://www.example.com\">www.example.com\"</a></td>\n</tr>\n<tr>\n<td>ipAddress</td>\n<td>String</td>\n<td>\"<strong>ipAddress</strong>\" refers to an IP address. It uniquely identifies a device or network interface on a TCP/IP network, enabling secure communication and validation of network endpoints in cryptographic protocols like TLS/SSL.  <br />  <br />ex:- \"10.32.43.124\"</td>\n</tr>\n<tr>\n<td>url</td>\n<td>String</td>\n<td>\"<strong>url</strong>\" refers to a Uniform Resource Locator, commonly known as a web address.  <br />  <br />ex:- \"<a href=\"https://www.google.com\">https://www.emudhra.com\"</a></td>\n</tr>\n<tr>\n<td>registeredID</td>\n<td>String</td>\n<td>\"<strong>registeredID</strong>\" refers to a registered object identifier (OID) that uniquely identifies an object or attribute within a hierarchical naming structure defined by an organization or standards body. it can be used to specify a unique identifier for an entity, attribute, or policy associated with the certificate, ensuring interoperability and standardized identification across systems.  <br />  <br />ex:- \"2.10.100.2.3.4\"</td>\n</tr>\n<tr>\n<td>directoryName</td>\n<td>String</td>\n<td>\"<strong>directoryName</strong>\" is a structured representation of a distinguished name (DN) in X.509 certificates. It includes attributes like common name, organization, and locality, facilitating accurate identification and validation of entities within hierarchical directory systems for secure communications.  <br />  <br />ex:- \"L=IAO\"</td>\n</tr>\n</tbody>\n</table>\n</div><p><strong>Tabel no 4</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>oid</td>\n<td>String</td>\n<td>subject DN details using the OID  <br />ex:- \"2.5.4.7\"</td>\n</tr>\n<tr>\n<td>value</td>\n<td>String</td>\n<td>Validation for the this field as below  <br />A character length of minimum 2 and maximum 75 characters  <br />A lowercase or uppercase English letter (from \"a\" to \"z\" and \"A\" to \"Z\").  <br />  <br />ex:- \"Delhi\"</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","createCustomCertificate"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"9fd95586-0b95-4836-9288-bb24067ccc69"},{"name":"createKeyStore","id":"247362f9-0ced-47ab-a396-f98937e135a5","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Client-ID","value":"{{x_client_id}}","type":"text"},{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"},{"key":"X-Emca-Api-Key","value":"{{x_emca_api_key}}","type":"text"}],"body":{"mode":"raw","raw":"{\r\n    \"profile\": \"4\",\r\n    \"subjectDN\": {\r\n        \"commonName\": \"Encrypted Certificate\",\r\n        \"country\": \"IN\"\r\n    },\r\n    \"keyAlgorithm\": \"RSA-2048\",\r\n    \"keyStorePassword\": \"Test@123\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://appemca.emudhra.com/emCAServices431/rest/createKeyStore","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>This is a method that is responsible for creating a keystore. A keystore is a repository for storing cryptographic keys and certificates.</p>\n<p>This refers to the type of keystore being generated. PKCS12 (Public-Key Cryptography Standards #12) is a standard for storing both X.509 certificates and private keys in a single file. It is widely used and supported by various systems.</p>\n<p>Call the <strong>createKeyStore</strong> method, providing it with the necessary parameters, including the certificate profile.</p>\n<p>The <strong>createKeyStore</strong> method processes based on the provided input perameters and generates a new keystore in the PKCS12 format.</p>\n<h3 id=\"prerequisites\">Prerequisites</h3>\n<ol>\n<li><p>The profile should be KRS (Key Recovery Service) enabled.</p>\n</li>\n<li><p>To enable KRS, follow these steps when creating the user profile</p>\n</li>\n<li><p>Log in to the emCA UI Portal as an Administrator and navigate to the user profile (refer emCA User Manual). Then, select the \"<strong>Is KRS enabled</strong>\" checkbox.</p>\n</li>\n</ol>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<p>Table no 1</p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>profile*</td>\n<td>String</td>\n<td>A Certificate Profile name or Certificate Profile ID is a unique profile or template created for certificates. Profiles can be created by an admin on emCA or using the CA Management APIs.  <br />  <br />ex:- \"5\", \"Encryption Certificate\"</td>\n</tr>\n<tr>\n<td>subscriberID</td>\n<td>Integer</td>\n<td>A Unique ID for the Subscribers/Devices uniquely identifies the Subscriber/Device.  <br />The value should only be a positive integer within the allowed range and up from 1 to 10 characters in length.  <br />  <br />ex:- 12345</td>\n</tr>\n<tr>\n<td>subjectDN*</td>\n<td>JSON</td>\n<td>Pass the all the subject dn details from this perameter  <br />ex:  <br />{  <br />\"commonName\": \"test\",  <br />\"country\":\"IN\".  <br />\"oids\": [  <br />{  <br />\"oid\": \"2.5.4.7\",  <br />\"value\": \"test\"  <br />}  <br />]  <br />}  <br />ref :- <strong>Tabel no 2</strong></td>\n</tr>\n<tr>\n<td>san</td>\n<td>JSON</td>\n<td>Pass the all the san details from this perameter  <br />ref:- <strong>Table no 4</strong>  <br />ex:  <br />{  <br />\"rfc822Name\": \"<a href=\"https://mailto:test@test.com\">test@test.com</a>\"  <br />},</td>\n</tr>\n<tr>\n<td>keyAlgorithm*</td>\n<td>String</td>\n<td>Provide required key algorithm for creating key store  <br />ex:- \"RSA-2048\", \"ECDSA-256\"  <br />For supported key algorithm ref :- <strong>Table no 3</strong></td>\n</tr>\n<tr>\n<td>keyStorePassword*</td>\n<td>String</td>\n<td>Password for generating keystore  <br />ex:- \"P@ssword1\"</td>\n</tr>\n<tr>\n<td>txnID</td>\n<td>Long</td>\n<td>The Transaction ID uniquely identifies the transaction.  <br />  <br />The value should only be a positive integer within the allowed range and upfrom 1 to 19 characters in length.  <br />  <br />ex:- 876545675</td>\n</tr>\n<tr>\n<td>validity</td>\n<td>JSON</td>\n<td>Certificate validity can be defined only if the profile supports custom validity.  <br />  <br />The validity should be less than the validity periods of both the profile and the issuer.  <br />  <br />Ex:-  <br />{  <br />\"days\": 365,  <br />\"hours\": 0,  <br />\"minutes\": 0,  <br />\"seconds\": 0  <br />}</td>\n</tr>\n<tr>\n<td>validfrom</td>\n<td>JSON</td>\n<td>Certificate validity can be defined starting from a specific date if the profile is enabled for custom validity.  <br />  <br />Validation for the validfrom field is as follows:  <br />  <br />validfrom should not be a past date.  <br />day - day of the month (1-31)  <br />month - month of the year (1-12)  <br />year - four-digit year (e.g., 2024)  <br />hour - hour of the day (0-23)  <br />minute - minute of the hour (0-59)  <br />second - second of the minute (0-59)\"  <br />  <br />ex:-  <br />{  <br />\"day\": 1,  <br />\"month\": 1,  <br />\"year\": 2024,  <br />\"hour\": 0,  <br />\"minute\": 0,  <br />\"second\": 0  <br />}</td>\n</tr>\n</tbody>\n</table>\n</div><p><strong>Tabel no 2</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>commonName</td>\n<td>String</td>\n<td>Validation for the CN field as below  <br />A character length of minimum 2 and maximum 64 characters  <br />A lowercase or uppercase English letter (from \"a\" to \"z\" and \"A\" to \"Z\").  <br />A digit (from \"0\" to \"9\").  <br />A hyphen (\"-\").  <br />A period (\".\").  <br />An apostrophe (\"'\").  <br />An asterisk (\"*\").  <br />An underscore (\"_\").  <br />At sign (\"@\")  <br />A space (\" \").  <br />  <br />ex:- \"keven\"</td>\n</tr>\n<tr>\n<td>country</td>\n<td>String</td>\n<td>Validation for the Country field as below  <br />A character length of minimum 2 and maximum 75 characters  <br />A lowercase or uppercase English letter (from \"a\" to \"z\" and \"A\" to \"Z\").  <br />ex:- \"IN\"</td>\n</tr>\n<tr>\n<td>organisation</td>\n<td>String</td>\n<td>Validation for the this field as below  <br />A character length of minimum 2 and maximum 75 characters  <br />A lowercase or uppercase English letter (from \"a\" to \"z\" and \"A\" to \"Z\").  <br />  <br />ex:- \"emudhra\"</td>\n</tr>\n<tr>\n<td>organisationUnit</td>\n<td>String</td>\n<td>Validation for the this field as below  <br />A character length of minimum 2 and maximum 75 characters  <br />A lowercase or uppercase English letter (from \"a\" to \"z\" and \"A\" to \"Z\").  <br />It will accept multiple OU values separated by commas.  <br />  <br />ex:- \"Finance\", \"Sales,Marketing\"</td>\n</tr>\n<tr>\n<td>postalCode</td>\n<td>String</td>\n<td>Validation for the postal code field as below  <br />A character length of minimum 4 and maximum 64 characters  <br />A digit (from \"0\" to \"9\").  <br />  <br />ex:- \"560063\"</td>\n</tr>\n<tr>\n<td>stateOrProvince</td>\n<td>String</td>\n<td>Validation for the state field as below  <br />A character length of minimum 2 and maximum 75 characters  <br />A lowercase or uppercase English letter (from \"a\" to \"z\" and \"A\" to \"Z\").  <br />  <br />ex:- \"KA\", \"India\"</td>\n</tr>\n<tr>\n<td>street</td>\n<td>String</td>\n<td>Validation for the this field as below  <br />A character length of minimum 2 and maximum 75 characters  <br />A lowercase or uppercase English letter (from \"a\" to \"z\" and \"A\" to \"Z\").  <br />  <br />ex:-\"jain street\"</td>\n</tr>\n<tr>\n<td>houseIdentifier</td>\n<td>String</td>\n<td>Validation for the this field as below  <br />A character length of minimum 2 and maximum 75 characters  <br />A lowercase or uppercase English letter (from \"a\" to \"z\" and \"A\" to \"Z\").  <br />  <br />ex:- \"Building A:</td>\n</tr>\n<tr>\n<td>serialNumber</td>\n<td>String</td>\n<td>Validation for the this field as below  <br />A character length of minimum 2 and maximum 75 characters  <br />A lowercase or uppercase English letter (from \"a\" to \"z\" and \"A\" to \"Z\").  <br />  <br />ex:- \"fff44f43224c43\"</td>\n</tr>\n<tr>\n<td>uniqueIdentifier</td>\n<td>String</td>\n<td>Validation for the this field as below  <br />A character length of minimum 2 and maximum 75 characters  <br />A lowercase or uppercase English letter (from \"a\" to \"z\" and \"A\" to \"Z\").  <br />  <br />ex:- \"774434cvfc45\"</td>\n</tr>\n<tr>\n<td>pseudonym</td>\n<td>String</td>\n<td>Validation for the this field as below  <br />A character length of minimum 2 and maximum 75 characters  <br />A lowercase or uppercase English letter (from \"a\" to \"z\" and \"A\" to \"Z\").  <br />  <br />ex:- \"Gorge ven\"</td>\n</tr>\n<tr>\n<td>telephoneNumber</td>\n<td>String</td>\n<td>SHA256 of Telephone Number  <br />ex:- \"9cd24231c813f6608bcf717e15b76700a80e2170fbf235e5ff344dae948bbfec\"</td>\n</tr>\n<tr>\n<td>title</td>\n<td>String</td>\n<td>Validation for the this field as below  <br />A character length of minimum 2 and maximum 75 characters  <br />A lowercase or uppercase English letter (from \"a\" to \"z\" and \"A\" to \"Z\").  <br />  <br />ex:- \"Dovloper\"</td>\n</tr>\n<tr>\n<td>email</td>\n<td>String</td>\n<td>A character length of minimum 2 and maximum 64 characters  <br />A lowercase or uppercase English letter (from \"a\" to \"z\" and \"A\" to \"Z\").  <br />A digit (from \"0\" to \"9\").  <br />A hyphen (\"-\").  <br />A period (\".\").  <br />An underscore (\"_\").  <br />At sign (\"@\")  <br />  <br />ex:- \"<a href=\"https://mailto:test@test.com\">sri.ram@outlook.com\"</a></td>\n</tr>\n<tr>\n<td>oids</td>\n<td>ArrayList</td>\n<td>Pass additional subject DN details using the OIDs. You can provide multiple OIDs in an array object.  <br />  <br />Refer <strong>Table no 5</strong>  <br />  <br />ex:-  <br />[  <br />{  <br />\"oid\": \"2.5.4.7\",  <br />\"value\": \"Hyderabad\"  <br />}  <br />]</td>\n</tr>\n</tbody>\n</table>\n</div><p><strong>Table no 3</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Type of Key algorithm</th>\n<th>Supported key algorithm and Sizes</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>RSA</td>\n<td>RSA-1024, RSA-2048, RSA-3072, RSA-4096, and RSA-8192</td>\n</tr>\n<tr>\n<td>ECDSA secp</td>\n<td>ECDSA-192, ECDSA-256, ECDSA-384 and ECDSA-521</td>\n</tr>\n<tr>\n<td>ECDSA Brainpool</td>\n<td>B-ECDSA-256, B-ECDSA-384 and B-ECDSA-512</td>\n</tr>\n<tr>\n<td>ECDSA Prime</td>\n<td>P-ECDSA-256, P-ECDSA-384 and P-ECDSA-521</td>\n</tr>\n<tr>\n<td>EDDSA</td>\n<td>Ed25519</td>\n</tr>\n<tr>\n<td>PQC</td>\n<td>DILITHIUM2, DILITHIUM3, DILITHIUM5, FALCON-512, FALCON-1024, sha2_256f, sha2_256s, sha2_128f, sha2_128s, sha2_192f, sha2_192s, shake_128f, shake_128s, shake_192f, hake_192s, shake_256f, shake_256s, haraka_192f, haraka_192s, haraka_256f, haraka_256s and haraka_128f</td>\n</tr>\n</tbody>\n</table>\n</div><p><strong>Tabel no 4</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>rfc822Name</td>\n<td>String</td>\n<td>\"<strong>rfc822Name</strong>\" refers to an email address formatted according to RFC 822 standards  <br />ex:-  <br /><a href=\"https://mailto:test@test.com\">\"sam.r@qa.co.in\"</a></td>\n</tr>\n<tr>\n<td>dnsName</td>\n<td>String</td>\n<td>\"<strong>dnsName</strong>\" refers to a domain name system (DNS) name. It identifies a domain or hostname associated with an entity or resource, allowing secure communication over networks while validating the identity of servers and services.  <br />  <br />ex:- \"<a href=\"http://www.example.com\">www.example.com\"</a></td>\n</tr>\n<tr>\n<td>ipAddress</td>\n<td>String</td>\n<td>\"<strong>ipAddress</strong>\" refers to an IP address. It uniquely identifies a device or network interface on a TCP/IP network, enabling secure communication and validation of network endpoints in cryptographic protocols like TLS/SSL.  <br />  <br />ex:- \"10.32.43.124\"</td>\n</tr>\n<tr>\n<td>url</td>\n<td>String</td>\n<td>\"<strong>url</strong>\" refers to a Uniform Resource Locator, commonly known as a web address.  <br />  <br />ex:- \"<a href=\"https://www.google.com\">https://www.emudhra.com\"</a></td>\n</tr>\n<tr>\n<td>registeredID</td>\n<td>String</td>\n<td>\"<strong>registeredID</strong>\" refers to a registered object identifier (OID) that uniquely identifies an object or attribute within a hierarchical naming structure defined by an organization or standards body. it can be used to specify a unique identifier for an entity, attribute, or policy associated with the certificate, ensuring interoperability and standardized identification across systems.  <br />  <br />ex: \"2.10.100.2.3.4\"</td>\n</tr>\n<tr>\n<td>directoryName</td>\n<td>String</td>\n<td>\"<strong>directoryName</strong>\" is a structured representation of a distinguished name (DN) in X.509 certificates. It includes attributes like common name, organization, and locality, facilitating accurate identification and validation of entities within hierarchical directory systems for secure communications.  <br />  <br />ex:- \"L=IAO\"</td>\n</tr>\n</tbody>\n</table>\n</div><p><strong>Tabel no 5</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>oid</td>\n<td>String</td>\n<td>subject DN details using the OID  <br />ex:- \"2.5.4.7\"</td>\n</tr>\n<tr>\n<td>value</td>\n<td>String</td>\n<td>Validation for the this field as below  <br />A character length of minimum 2 and maximum 75 characters  <br />A lowercase or uppercase English letter (from \"a\" to \"z\" and \"A\" to \"Z\").  <br />  <br />ex:- \"kerala\"</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","createKeyStore"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"247362f9-0ced-47ab-a396-f98937e135a5"},{"name":"rekey","id":"dbd7c729-c85e-4d70-920a-895cc28b6c7b","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Client-ID","value":"{{x_client_id}}","type":"text"},{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"},{"key":"X-Emca-Api-Key","value":"{{x_emca_api_key}}","type":"text"}],"body":{"mode":"raw","raw":"{\r\n  \"serialNo\": \"551c7bf7e4494a965c7ab38ad1ff4892\",\r\n  \"output\": \"X509\",\r\n  \"remarks\": \"test\",\r\n  \"csr\": \"MIICzTCCAbUCAQAwgYcxCzAJBgNVBAYTAkdCMRYwFAYDVQQIEw1TdGFmZm9yZHNoaXJlMRcwFQYDVQQHEw5TdG9rZSBvbiBUcmVudDEjMCEGA1UEChMaUmVkIEtlc3RyZWwgQ29uc3VsdGluZyBMdGQxIjAgBgNVBAMTGXRlc3RjZXJ0LnJlZGtlc3RyZWwuY28udWswggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDWLeW88IeAIa3n23R99i874fh0jetf+STsGPgkfGXGJ++tclKGk3MJE0ijD4PNaxGXUCNULgn2ROyybm5sTmGzpEOD+1AAAyV+pLQoFNkHEFuudGqVM6XkPWfqaM2vKvdzUbPPC0X/MfDFGPxc8AY3TUM385c9c9/WOIF6NUcAvAFIQF0zG7evzJZBqDb4enUnatMSLHmxRWMi1JeHtfLINXhNitHewEQWgIB3j1xmh7CPO5FeTb6HzQDxc+f7uMisY6s9J/Ph3GeOCeIDooqU8jnfV5eGEzIMH5CFMZjajrNKF4DYK3YRyUI0K66+v0KILoUntEs++M20LhOn+VE9AgMBAAGgADANBgkqhkiG9w0BAQUFAAOCAQEAUWE7oBX3SLjYNM53bsBOlNGnsgAp1P1fiCPpEKaZGEOUJ2xOguIHSu1N1ZigKpWmiAAZxuoagW1R/ANM3jXpvCLVBRv40AHCFsot9udrdCYjI43aDHAaYvLmT4/Pvpntcn0/7+g//elAHhr9UIooMZwwwo6yom67Jwfw/be/g7Mae7mPHZ2lsQTS02hEeqVynIRk2W9meQULrt+/atog0mqJSBx0WswtHliTc+nXFpQrwFIEzVuPGCOVw7LmCfNmHNCkZVuRSJB/9MdLmrfwchPI3NeTGSe+BZfsOtpt2/7j+bqeYKFu8B0stLoJBEnihxUoV18uZOmOeuVuX1N6nA==\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://appemca.emudhra.com/emCAServices431/rest/rekey","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The \"<strong>rekey</strong>\" API facilitates the regenerating a certificate's remaining validity period by revoking the existing certificate. It requires a Certificate Signing Request (CSR) to generate a new certificate with the remaining validity timeframe. This workflow ensures the secure replacement of compromised or lost certificates, maintaining continuous secure communication while adhering to best practices in certificate management.</p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<p>Table no 1</p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>serialNo*</td>\n<td>String</td>\n<td>Certificate serial number for which rekey is initiated.  <br />  <br />Ex :- “e4cb23a4b97a0c12f2641c1fc49d9ba7”</td>\n</tr>\n<tr>\n<td>output*</td>\n<td>String</td>\n<td>Output defines the format of the certificate:  <br />X509: Base64 encoded X509 Certificate (without certificate chain).  <br />PEM: PEM format with certificate chain.  <br />  <br />ex:- \"X509\" or \"PEM\"</td>\n</tr>\n<tr>\n<td>csr*</td>\n<td>String</td>\n<td>Certificate Signing Request (#PKCS10)  <br />  <br />ex:-  <br />\"MIICzTCCAbUCAQAwgYcxCzAJBgNV..........................B0stLoJBEnihxUoV18uZOmOeuVuX1N6nA==\"</td>\n</tr>\n<tr>\n<td>remarks</td>\n<td>String</td>\n<td>The '<strong>Remarks</strong>' parameter in the 'rekey' API allows users to include additional comments to the certificate rekeying process.  <br />  <br />ex:-\"lost the public key\"</td>\n</tr>\n<tr>\n<td>validfrom</td>\n<td>JSON</td>\n<td>Certificate validity can be defined starting from a specific date if the profile is enabled for custom validity.  <br />  <br />Validation for the validfrom field is as follows:  <br />  <br />validfrom should not be a past date.  <br />day - day of the month (1-31)  <br />month - month of the year (1-12)  <br />year - four-digit year (e.g., 2024)  <br />hour - hour of the day (0-23)  <br />minute - minute of the hour (0-59)  <br />second - second of the minute (0-59)\"  <br />  <br />ex:-  <br />{  <br />\"day\": 1,  <br />\"month\": 1,  <br />\"year\": 2024,  <br />\"hour\": 0,  <br />\"minute\": 0,  <br />\"second\": 0  <br />}</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","rekey"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"dbd7c729-c85e-4d70-920a-895cc28b6c7b"},{"name":"regenerateKeyStore","id":"a31f02e3-5e38-4522-a45f-fa41328e230d","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"},{"key":"X-Client-ID","value":"{{x_client_id}}","type":"text"},{"key":"X-Emca-Api-Key","value":"{{x_emca_api_key}}","type":"text"}],"body":{"mode":"raw","raw":"{\r\n  \"serialNo\": \"551c7bf7e4494a965c7ab38ad1ff4892\",\r\n  \"output\": \"X509\",\r\n  \"remarks\": \"test\",\r\n  \"csr\": \"MIICzTCCAbUCAQAwgYcxCzAJBgNVBAYTAkdCMRYwFAYDVQQIEw1TdGFmZm9yZHNoaXJlMRcwFQYDVQQHEw5TdG9rZSBvbiBUcmVudDEjMCEGA1UEChMaUmVkIEtlc3RyZWwgQ29uc3VsdGluZyBMdGQxIjAgBgNVBAMTGXRlc3RjZXJ0LnJlZGtlc3RyZWwuY28udWswggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDWLeW88IeAIa3n23R99i874fh0jetf+STsGPgkfGXGJ++tclKGk3MJE0ijD4PNaxGXUCNULgn2ROyybm5sTmGzpEOD+1AAAyV+pLQoFNkHEFuudGqVM6XkPWfqaM2vKvdzUbPPC0X/MfDFGPxc8AY3TUM385c9c9/WOIF6NUcAvAFIQF0zG7evzJZBqDb4enUnatMSLHmxRWMi1JeHtfLINXhNitHewEQWgIB3j1xmh7CPO5FeTb6HzQDxc+f7uMisY6s9J/Ph3GeOCeIDooqU8jnfV5eGEzIMH5CFMZjajrNKF4DYK3YRyUI0K66+v0KILoUntEs++M20LhOn+VE9AgMBAAGgADANBgkqhkiG9w0BAQUFAAOCAQEAUWE7oBX3SLjYNM53bsBOlNGnsgAp1P1fiCPpEKaZGEOUJ2xOguIHSu1N1ZigKpWmiAAZxuoagW1R/ANM3jXpvCLVBRv40AHCFsot9udrdCYjI43aDHAaYvLmT4/Pvpntcn0/7+g//elAHhr9UIooMZwwwo6yom67Jwfw/be/g7Mae7mPHZ2lsQTS02hEeqVynIRk2W9meQULrt+/atog0mqJSBx0WswtHliTc+nXFpQrwFIEzVuPGCOVw7LmCfNmHNCkZVuRSJB/9MdLmrfwchPI3NeTGSe+BZfsOtpt2/7j+bqeYKFu8B0stLoJBEnihxUoV18uZOmOeuVuX1N6nA==\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://appemca.emudhra.com/emCAServices431/rest/rekey","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The \"<strong>rekey</strong>\" API facilitates the regenerating a certificate's remaining validity period by revoking the existing certificate. It requires a Certificate Signing Request (CSR) to generate a new certificate with the remaining validity timeframe. This workflow ensures the secure replacement of compromised or lost certificates, maintaining continuous secure communication while adhering to best practices in certificate management.</p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<p>Table no 1</p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>serialNo*</td>\n<td>String</td>\n<td>Certificate serial number for which rekey is initiated.  <br />  <br />Ex :- “e4cb23a4b97a0c12f2641c1fc49d9ba7”</td>\n</tr>\n<tr>\n<td>output*</td>\n<td>String</td>\n<td>Output defines the format of the certificate:  <br />X509: Base64 encoded X509 Certificate (without certificate chain).  <br />PEM: PEM format with certificate chain.  <br />  <br />ex:- \"X509\" or \"PEM\"</td>\n</tr>\n<tr>\n<td>csr*</td>\n<td>String</td>\n<td>Certificate Signing Request (#PKCS10)  <br />  <br />ex:-  <br />\"MIICzTCCAbUCAQAwgYcxCzAJBgNV..........................B0stLoJBEnihxUoV18uZOmOeuVuX1N6nA==\"</td>\n</tr>\n<tr>\n<td>remarks</td>\n<td>String</td>\n<td>The '<strong>Remarks</strong>' parameter in the 'rekey' API allows users to include additional comments to the certificate rekeying process.  <br />  <br />ex:-\"lost the public key\"</td>\n</tr>\n<tr>\n<td>validfrom</td>\n<td>JSON</td>\n<td>Certificate validity can be defined starting from a specific date if the profile is enabled for custom validity.  <br />  <br />Validation for the validfrom field is as follows:  <br />  <br />validfrom should not be a past date.  <br />day - day of the month (1-31)  <br />month - month of the year (1-12)  <br />year - four-digit year (e.g., 2024)  <br />hour - hour of the day (0-23)  <br />minute - minute of the hour (0-59)  <br />second - second of the minute (0-59)\"  <br />  <br />ex:-  <br />{  <br />\"day\": 1,  <br />\"month\": 1,  <br />\"year\": 2024,  <br />\"hour\": 0,  <br />\"minute\": 0,  <br />\"second\": 0  <br />}</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","rekey"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"a31f02e3-5e38-4522-a45f-fa41328e230d"},{"name":"revoke","id":"fd8a4f3f-4eba-4e76-9d5c-4fffe416d4eb","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"},{"key":"X-Client-ID","value":"{{x_client_id}}","type":"text"},{"key":"X-Emca-Api-Key","value":"{{x_emca_api_key}}","type":"text"}],"body":{"mode":"raw","raw":"{\r\n  \"serialNo\": \"551c7bf7e4494a965c7ab38ad1ff4892\",\r\n  \"remarks\": \"test\",\r\n  \"reason\": 1\r\n}","options":{"raw":{"language":"json"}}},"url":"https://appemca.emudhra.com/emCAServices431/rest/revoke","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The \"<strong>revoke</strong>\" API facilitates the revocation of a certificate based on its serial number. This functionality is crucial for invalidating certificates that are compromised or no longer trusted.</p>\n<p>By specifying the serial number of the certificate, this API ensures immediate termination of its validity, thereby maintaining security and compliance with organizational policies regarding certificate management.</p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<p>Table no 1</p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>serialNo*</td>\n<td>String</td>\n<td>Certificate serial number for which revoke is initiated.  <br />  <br />Ex :- “b4cb23a4b97g5d0c12f2641c1fc49d9ba7”</td>\n</tr>\n<tr>\n<td>reason*</td>\n<td>Integer</td>\n<td>0 (Unspecified): Reason not specified or unknown.  <br />  <br />1 (Key Compromise): Private key associated with the certificate compromised or suspected compromised.  <br />  <br />2 (CA compromise): Certificate Authority (CA) certificate or private key compromised or suspected compromised.  <br />  <br />3 (Affiliation Changed): Certificate holder's affiliation or relationship with the organization changed.  <br />  <br />4 (Superseded): Certificate replaced by a new certificate.  <br />  <br />5 (Cessation of Operation): Organization or entity associated with the certificate ceased operation.  <br />  <br />9 (Privilege Withdrawn): Privileges associated with the certificate holder withdrawn.  <br />  <br />10 (AA Compromise): Certificate used for authentication or authorization compromised or suspected compromised.  <br />  <br />ex:- 4</td>\n</tr>\n<tr>\n<td>remarks*</td>\n<td>String</td>\n<td>The '<strong>Remarks</strong>' parameter in the 'revoke' API allows users to include additional comments to the certificate rekeying process.  <br />  <br />ex:-\"Certificate expired\"</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","revoke"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"fd8a4f3f-4eba-4e76-9d5c-4fffe416d4eb"},{"name":"suspend","id":"d090fe44-6fd3-425a-b442-25f25016d828","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"},{"key":"X-Client-ID","value":"{{x_client_id}}","type":"text"},{"key":"X-Emca-Api-Key","value":"{{x_emca_api_key}}","type":"text"}],"body":{"mode":"raw","raw":"{\r\n  \"serialNo\": \"bbc11e8f406e4a24c31c852660b464dd\",\r\n  \"remarks\": \"test\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://appemca.emudhra.com/emCAServices431/rest/suspend","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The '<strong>suspend</strong>' API suspends certificates based on their serial numbers, crucial for invalidating compromised, or untrusted certificates. Users can also reinstate suspended certificates as needed, ensuring security and compliance with organizational policies.</p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<p>Table no 1</p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>serialNo*</td>\n<td>String</td>\n<td>Certificate serial number for which revoke is initiated.  <br />  <br />Ex :- “b4cb23a4b97g5d0c12f2641c1fc49d9ba7”</td>\n</tr>\n<tr>\n<td>remarks*</td>\n<td>String</td>\n<td>The '<strong>Remarks</strong>' parameter in the 'supend' API allows users to include additional comments to the certificate rekeying process.  <br />  <br />ex:-\"forgot password\"</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","suspend"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"d090fe44-6fd3-425a-b442-25f25016d828"},{"name":"reinstate","id":"61f944ff-90c8-44f2-8cb8-1a859909d758","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"},{"key":"X-Client-ID","value":"{{x_client_id}}","type":"text"},{"key":"X-Emca-Api-Key","value":"{{x_emca_api_key}}","type":"text"}],"body":{"mode":"raw","raw":"{\r\n  \"serialNo\": \"bbc11e8f406e4a24c31c852660b464dd\",\r\n  \"remarks\": \"test\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://appemca.emudhra.com/emCAServices431/rest/reinstate","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The '<strong>reinstate</strong>' API allows for the reinstatement of previously suspended certificates. This functionality is used to restore certificates that were temporarily invalidated due to compromise, or other reasons. By specifying the serial number of the suspended certificate, this API ensures the restoration of its validity, maintaining security and compliance with organizational certificate management policies.</p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<p><strong>Table no 1</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>serialNo*</td>\n<td>String</td>\n<td>Certificate serial number for which reinstate is initiated.  <br />  <br />Ex :- “b4cb23a4b97g5d0c12f2641c1fc49d9ba7”</td>\n</tr>\n<tr>\n<td>remarks*</td>\n<td>String</td>\n<td>The '<strong>Remarks</strong>' parameter in the '<strong>reinstate</strong>' API allows users to include additional comments to the certificate rekeying process.  <br />  <br />ex:-\"test\"</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","reinstate"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"61f944ff-90c8-44f2-8cb8-1a859909d758"},{"name":"getCertificate","id":"005c97e7-3e4d-487b-b742-dad30847a768","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"},{"key":"X-Client-ID","value":"{{x_client_id}}","type":"text"},{"key":"X-Emca-Api-Key","value":"{{x_emca_api_key}}","type":"text"}],"body":{"mode":"raw","raw":"{\r\n  \"serialNo\": \"bbc11e8f406e4a24c31c852660b464dd\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://appemca.emudhra.com/emCAServices431/rest/getCertificate","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The \"<strong>getCertificate</strong>\" API allows users to download a User certificate based on its serial number or retrieve the status of a manually authorized request using the requestId. This functionality supports efficient certificate management by providing access to specific certificates or the status of requests in a straightforward manner.</p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<p><strong>Note</strong>: Users must provide either the serial number or the request ID; both parameters cannot be included in the same request</p>\n<p><strong>Table no 1</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>serialNo</td>\n<td>String</td>\n<td>Certificate serial number  <br />  <br />Ex :- “b4cb23a4b97g5d0c12f2641c1fc49d9ba7”</td>\n</tr>\n<tr>\n<td>requestId</td>\n<td>String</td>\n<td>The requestId is obtained when a certificate request is manually authorized.  <br />  <br />ex:-\"53352123554532\"</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","getCertificate"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"005c97e7-3e4d-487b-b742-dad30847a768"},{"name":"getProfiles","id":"03927ab2-c82b-4f51-bcee-9e75eaf09be7","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"},{"key":"X-Client-ID","value":"{{x_client_id}}","type":"text"},{"key":"X-Emca-Api-Key","value":"{{x_emca_api_key}}","type":"text"}],"body":{"mode":"raw","raw":"{\r\n  \"caName\": \"CA Certificate 2024\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://appemca.emudhra.com/emCAServices431/rest/getProfiles","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The \"<strong>getProfiles</strong>\" API retrieves all profiles created for the issuing CA, providing basic information such as profile name, profile ID, and validity. By specifying the CA name, users can efficiently manage and review all profiles associated with that issuing CA.</p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<p><strong>Table no 1</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>caName*</td>\n<td>String</td>\n<td>Common name of CA Certifictae  <br />  <br />Ex :- “CA Certificate 2924”</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","getProfiles"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"03927ab2-c82b-4f51-bcee-9e75eaf09be7"},{"name":"getProfileInfo","id":"730c05b1-724e-416b-bd4f-0dc8d8836772","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Client-ID","value":"{{x_client_id}}","type":"text"},{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"},{"key":"X-Emca-Api-Key","value":"{{x_emca_api_key}}","type":"text"}],"body":{"mode":"raw","raw":"{\r\n  \"profile\": \"3\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://appemca.emudhra.com/emCAServices431/rest/getProfileInfo","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The \"<strong>getProfileInfo</strong>\" API retrieves profile information for a CA or USER by providing the profile name or profile id. This API helps in obtaining detailed information about specific profiles, facilitating efficient management and verification of CA or user profiles</p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<p><strong>Table no 1</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>profile*</td>\n<td>String</td>\n<td>Pass Certificate profile name or Id to be used to get profile information  <br />  <br />ex:- \"5\", \"signer cert profile\"</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","getProfileInfo"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"730c05b1-724e-416b-bd4f-0dc8d8836772"},{"name":"getCertInfo","id":"3676d8e9-2f78-452c-8b09-2f7b275c9647","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Client-ID","value":"{{x_client_id}}","type":"text"},{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"},{"key":"X-Emca-Api-Key","value":"{{x_emca_api_key}}","type":"text"}],"body":{"mode":"raw","raw":"{\r\n  \"caName\": \"CA Certificate 2024\",\r\n  \"noOfCertificates\": 100,\r\n  \"round\": 0\r\n}","options":{"raw":{"language":"json"}}},"url":"https://appemca.emudhra.com/emCAServices431/rest/getCertInfo","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The \"<strong>getCertInfo</strong>\" API retrieves user certificate information by providing the Issuing CA's common name. This API helps in obtaining detailed information about user certificates issued by a specific Certificate Authority, facilitating efficient certificate management</p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<p><strong>Table no 1</strong></p>\n<p>Integer</p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>caName*</td>\n<td>String</td>\n<td>Common name of CA Certifictae  <br />  <br />Ex :- “CA Certificate 2024\"</td>\n</tr>\n<tr>\n<td>noOfCertificates*</td>\n<td>Integer</td>\n<td>Retrieve the number of recently generated certificates under the provided CA. For instance, get the last 10 certificates generated under \"CA Certificate 2024.\"  <br />  <br />ex:- 10</td>\n</tr>\n<tr>\n<td>round</td>\n<td>Integer</td>\n<td>The certificate details can be retrieved up to the configuration limit, depending on the defined configuration. For example, to get 1000 certificate details when the limitation in the configuration is 100, follow the approach below:  <br />  <br />1. To get certificates 1-100, pass 0 or leave it empty.  <br />To get certificates 101-200, pass 1.  <br />2. To get certificates 201-300, pass 2.  <br />3. Continue this approach to retrieve certificates up to 1000</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","getCertInfo"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"3676d8e9-2f78-452c-8b09-2f7b275c9647"},{"name":"getCertCount","id":"d9db6e0f-008c-4141-ab75-9ad025a64b67","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"},{"key":"X-Client-ID","value":"{{x_client_id}}","type":"text"},{"key":"X-Emca-Api-Key","value":"{{x_emca_api_key}}","type":"text"}],"body":{"mode":"raw","raw":"{\r\n  \"responseType\": \"Y\",\r\n  \"caName\": [\r\n    \"CA Certificate 2024\"\r\n  ]\r\n}","options":{"raw":{"language":"json"}}},"url":"https://appemca.emudhra.com/emCAServices431/rest/getCertCount","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The \"<strong>getCertCount</strong>\" API retrieves the total count of certificates issued under the specified Issuing CA. By providing the Issuing CA's details, users can obtain an accurate count of all certificates issued by that CA.</p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<p><strong>Table no 1</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>responseType</td>\n<td>String</td>\n<td>The response will vary based on the <strong>responseType</strong> parameter. Please refer to the following expected responses:  <br />  <br />Empty (\"\") or null : Retrieves the total certificate count.  <br />  <br />\"Y\" : Retrieves the certificate count year-wise.  <br />  <br />\"M\" : Retrieves the certificate count month-wise.  <br />  <br />Ex:- \"M\" or \"Y\" or \"\" or null</td>\n</tr>\n<tr>\n<td>caName*</td>\n<td>ArrayList</td>\n<td>List of common names of CA certificates for which you want to get the count of issuing user certificates.  <br />  <br />Ex:-  <br />[  <br />\"CA Certificate 2023\",  <br />\"CA Certificate 2024\"  <br />]</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","getCertCount"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"d9db6e0f-008c-4141-ab75-9ad025a64b67"},{"name":"getExpiringSoonCertInfo","id":"0445e8aa-4f3a-4925-9c5f-25c5dc578456","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"},{"key":"X-Client-ID","value":"{{x_client_id}}","type":"text"},{"key":"X-Emca-Api-Key","value":"{{x_emca_api_key}}","type":"text"}],"body":{"mode":"raw","raw":"{\r\n  \"noOfDays\": 370,\r\n  \"caName\": [\r\n    \"\"\r\n  ],\r\n  \"round\": 0\r\n}","options":{"raw":{"language":"json"}}},"url":"https://appemca.emudhra.com/emCAServices431/rest/getExpiringSoonCertInfo","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The \"<strong>getExpiringSoonCertInfo</strong>\" API retrieves information about certificates that are expiring soon, based on the specified number of days. Users can optionally provide the CA name to filter results for a specific Certificate Authority, aiding in the efficient management of certificates nearing expiration within the defined time frame.</p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<p><strong>Table no 1</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>noOfDays*</td>\n<td>Integer</td>\n<td>Number of days until certificates are nearing expiration.  <br />  <br />ex:- 10</td>\n</tr>\n<tr>\n<td>caName</td>\n<td>ArrayList</td>\n<td>List of common names of CA certificates for which you want to retrieve information about expiring user certificates.  <br />  <br />Ex:-  <br />[  <br />\"CA Certificate 2023\",  <br />\"CA Certificate 2024\"  <br />]</td>\n</tr>\n<tr>\n<td>round</td>\n<td>Integer</td>\n<td>The certificate details can be retrieved up to the configuration limit, depending on the defined configuration. For example, to get 1000 certificate details when the limitation in the configuration is 100, follow the approach below:  <br />  <br />1. To get certificates 1-100, pass 0 or leave it empty.  <br />To get certificates 101-200, pass 1.  <br />2. To get certificates 201-300, pass 2.  <br />3. Continue this approach to retrieve certificates up to 1000  <br />  <br />ex:- 1</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","getExpiringSoonCertInfo"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"0445e8aa-4f3a-4925-9c5f-25c5dc578456"},{"name":"getCAs","id":"60dacfd2-6ac9-4665-94d0-67736164875d","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"},{"key":"X-Client-ID","value":"{{x_client_id}}","type":"text"},{"key":"X-Emca-Api-Key","value":"{{x_emca_api_key}}","type":"text"}],"url":"https://appemca.emudhra.com/emCAServices431/rest/getCAs","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The \"<strong>getCAs</strong>\" API returns the common names of all available Issuing CA certificates in its response.</p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p><strong>NOTE</strong>: This API does not require any input parameters.</p>\n","urlObject":{"protocol":"https","path":["emCAServices431","rest","getCAs"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"60dacfd2-6ac9-4665-94d0-67736164875d"},{"name":"getCertificateChain","id":"e99f9a7a-019a-4aad-9782-b39ad0ab2427","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"},{"key":"X-Client-ID","value":"{{x_client_id}}","type":"text"},{"key":"X-Emca-Api-Key","value":"{{x_emca_api_key}}","type":"text"}],"body":{"mode":"raw","raw":"{\r\n  \"caName\": \"CA Certificate 2024\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://appemca.emudhra.com/emCAServices431/rest/getCertificateChain","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The \"<strong>getCertificateChain</strong>\" API retrieves the complete certificate chain in encoded PEM format by provding the CA name. This functionality enables users to obtain all certificates in the chain associated with a specific Certificate Authority, facilitating comprehensive certificate management and validation.</p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<p><strong>Table no 1</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>caName*</td>\n<td>String</td>\n<td>Common name of CA Certifictae  <br />  <br />Ex :- “CA Certificate 2024”</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","getCertificateChain"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"e99f9a7a-019a-4aad-9782-b39ad0ab2427"},{"name":"getCAs","id":"e10fb0d4-c6dc-4548-8869-a2d68d87eb86","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[],"url":"https://appemca.emudhra.com/emCAServices431/rest/getCAs/{{x_client_id}}","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The '<strong>getCAs</strong>' API is supported by GET requests. It returns the common names of all available Issuing CA certificates in its response, where clientId is passed as a path variable.</p>\n<p><strong>URL</strong></p>\n<p><a href=\"https://appemca.emudhra.com/emCAServices/rest/getCAs/924e0d30-8cea-4bf4-be77-4b0e160dbaf9\">https://appemca.emudhra.com/emCAServices/rest/getCAs/{clientId}</a></p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<p><strong>Table no 1</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>clientId*</td>\n<td>String</td>\n<td>You need to pass the clientId in path variable You will get the clientId from emCA when you register an external application user for consuming APIs.  <br />  <br />ex:- \"924e0d30-8cea-4bf4-be77-4b0e160dbaf9\"</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","getCAs","{{x_client_id}}"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"e10fb0d4-c6dc-4548-8869-a2d68d87eb86"},{"name":"getCertificateChain","id":"cc5b465d-a3ab-4efe-bade-cdff0831104e","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[],"url":"https://appemca.emudhra.com/emCAServices431/rest/getCertificateChain/{{x_client_id}}/eMudhra Root CA","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The '<strong>getCertificateChain</strong>' API is GET-supported API where clientId and caname is passed as a path variable, API retrieves the complete certificate chain in encoded PEM format by provding the CA name. This functionality enables users to obtain all certificates in the chain associated with a specific Certificate Authority, facilitating comprehensive certificate management and validation.</p>\n<p><strong>URL</strong></p>\n<p><a href=\"https://appemca.emudhra.com/emCAServices/rest/getProfileInfo/%7BclientId%7D/%7Bprofile%7D\">https://appemca.emudhra.com/emCAServices/rest/getProfileInfo/{clientId}/{caName}</a></p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<p><strong>Table no 1</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>clientId*</td>\n<td>String</td>\n<td>You need to pass the clientId in path variable You will get the clientId from emCA when you register an external application user for consuming APIs.  <br />  <br />ex:- \"924e0d30-8cea-4bf4-be77-4b0e160dbaf9\"</td>\n</tr>\n<tr>\n<td>caName*</td>\n<td>String</td>\n<td>Common name of CA Certifictae need to be passed from the path variable  <br />  <br />Ex :- “CA Certificate 2924”</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","getCertificateChain","{{x_client_id}}","eMudhra Root CA"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"cc5b465d-a3ab-4efe-bade-cdff0831104e"},{"name":"getProfileInfo","id":"36b75ebe-87c5-47d5-9f0f-4c39f078e0ec","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[],"url":"https://appemca.emudhra.com/emCAServices431/rest/getProfileInfo/{{x_client_id}}/3","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>\"The '<strong>getProfileInfo</strong>' API is supported by GET requests. It retrieves profile information for a CA or user, where clientId, profile name, or profile ID is passed as path variables. This API facilitates the retrieval of detailed information about specific profiles, enhancing the efficient management and verification of CA or user profiles.\"</p>\n<p><strong>URL</strong></p>\n<p><a href=\"https://appemca.emudhra.com/emCAServices/rest/getProfileInfo/%7BclientId%7D/%7Bprofile%7D\">https://appemca.emudhra.com/emCAServices/rest/getProfileInfo/{clientId}/{profile}</a></p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<p><strong>Table no 1</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>clientId*</td>\n<td>String</td>\n<td>You need to pass the clientId in path variable You will get the clientId from emCA when you register an external application user for consuming APIs.  <br />  <br />ex:- \"924e0d30-8cea-4bf4-be77-4b0e160dbaf9\"</td>\n</tr>\n<tr>\n<td>profile*</td>\n<td>String</td>\n<td>Pass Certificate profile name or Id in path variable to be used to get profile information  <br />  <br />ex:- \"3\", \"signer cert profile\"</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","getProfileInfo","{{x_client_id}}","3"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"36b75ebe-87c5-47d5-9f0f-4c39f078e0ec"},{"name":"getProfiles","id":"26fa2dc6-c02b-496d-adc0-42e32f320c31","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[],"url":"https://appemca.emudhra.com/emCAServices431/rest/getProfiles/{{x_client_id}}/CA Certificate 2024","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The '<strong>getProfiles</strong>' API is GET-supported API where clientId and caname is passed as a path variable, It retrieves all profiles created for the issuing CA, providing essential details such as profile name, profile ID, and validity. Users specify the CA name to efficiently manage and review profiles associated with that issuing CA.</p>\n<p><strong>URL</strong></p>\n<p><a href=\"https://appemca.emudhra.com/emCAServices/rest/getProfileInfo/%7BclientId%7D/%7Bprofile%7D\">https://appemca.emudhra.com/emCAServices/rest/getProfileInfo/{clientId}/{caName}</a></p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<p><strong>Table no 1</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>clientId*</td>\n<td>String</td>\n<td>You need to pass the clientId in path variable You will get the clientId from emCA when you register an external application user for consuming APIs.  <br />  <br />ex:- \"924e0d30-8cea-4bf4-be77-4b0e160dbaf9\"</td>\n</tr>\n<tr>\n<td>caName*</td>\n<td>String</td>\n<td>Common name of CA Certifictae need to be passed from the path variable  <br />  <br />Ex :- “CA Certificate 2024”</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","getProfiles","{{x_client_id}}","CA Certificate 2024"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"26fa2dc6-c02b-496d-adc0-42e32f320c31"},{"name":"getCertificate","id":"96277350-b163-4009-9c58-6d7d9d3a41ad","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[],"url":"https://appemca.emudhra.com/emCAServices431/rest/getCertificate/{{x_client_id}}?serialNo=bbc11e8f406e4a24c31c852660b464dd","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The \"<strong>getCertificate</strong>\" API is a GET-supported API where clientId is passed as a path variable, and the serial number and requestId parameters need to be passed from the query parameters. This API allows users to download a user certificate based on its serial number or retrieve the status of a manually authorized request using the requestId, supporting efficient certificate management.</p>\n<p><strong>URL</strong></p>\n<p><a href=\"https://appemca.emudhra.com/emCAServices/rest/getProfileInfo/%7BclientId%7D/%7Bprofile%7D\">https://appemca.emudhra.com/emCAServices/rest/getProfileInfo/{clientId}?</a>serialNo=bbc11e8f406e4a24c31c852660b464dd</p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<p><strong>Note</strong>: Users must provide either the serial number or the request ID; both parameters cannot be included in the same request</p>\n<p><strong>Table no 1</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>clientId*</td>\n<td>String</td>\n<td>You need to pass the clientId in path variable You will get the clientId from emCA when you register an external application user for consuming APIs.  <br />  <br />ex:- \"924e0d30-8cea-4bf4-be77-4b0e160dbaf9\"</td>\n</tr>\n<tr>\n<td>serialNo</td>\n<td>String</td>\n<td>Certificate serial number.  <br />serial number need to be passed from the query parameters  <br />  <br />Ex :- “b4cb23a4b97g5d0c12f2641c1fc49d9ba7”</td>\n</tr>\n<tr>\n<td>requestId</td>\n<td>String</td>\n<td>The requestId is obtained when a certificate request is manually authorized.  <br />  <br />requestId need to be passed from the query parameters  <br />  <br />ex:-\"53352123554532\"</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","getCertificate","{{x_client_id}}"],"host":["appemca","emudhra","com"],"query":[{"key":"serialNo","value":"bbc11e8f406e4a24c31c852660b464dd"}],"variable":[]}},"response":[],"_postman_id":"96277350-b163-4009-9c58-6d7d9d3a41ad"}],"id":"420bc21d-c7b1-44b8-adea-2c6109e377aa","description":"<p>The Certificate Management APIs provide a robust and secure solution for handling the entire lifecycle of digital certificates. These APIs enable automated processes for certificate issuance, renewal, revocation, and validation, ensuring efficient management and enhanced security. Supporting both RSA and ECC algorithms, these APIs are designed to integrate seamlessly with existing systems and adhere to industry standards for security and interoperability. By utilizing these APIs, organizations can maintain a compliant and reliable public key infrastructure (PKI) with minimal manual intervention.</p>\n<p>To ensure secure communication and multi-tenant isolation, all requests must include the following headers:</p>\n<ul>\n<li><p><strong><code>X-Nonce</code></strong>: A unique, per-request identifier used to prevent replay attacks by ensuring freshness and uniqueness.</p>\n</li>\n<li><p><strong><code>X-Client-ID</code></strong>: Identifies the tenant or organization initiating the request, enabling proper scoping and access control.</p>\n</li>\n<li><p><strong><code>X-Emca-Api-Key</code></strong>: A secure API key used to authenticate the client and authorize access to certificate management operations.</p>\n</li>\n</ul>\n<p>By leveraging these headers and adhering to a security-first approach, the Certificate Management APIs enable organizations to maintain a compliant, scalable, and reliable public key infrastructure (PKI) with minimal manual intervention.</p>\n","_postman_id":"420bc21d-c7b1-44b8-adea-2c6109e377aa"},{"name":"Backup Management","item":[{"name":"manualBackup","id":"a078f39a-324f-4e42-a492-49b0eb3420f8","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"},{"key":"X-Client-ID","value":"{{x_client_id}}","type":"text"},{"key":"X-Emca-Api-Key","value":"{{x_emca_api_key}}","type":"text"}],"body":{"mode":"raw","raw":"{\r\n  \"backupProperties\": true,\r\n  \"backupDatabase\": true,\r\n  \"filePath\": \"/backup/emca\",\r\n  \"async\": false\r\n}","options":{"raw":{"language":"json"}}},"url":"https://appemca.emudhra.com/emCAServices431/rest/backup/manual","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The <strong>\"manualBackup\"</strong> API allows <strong>Administrator</strong> or authorized <strong>external application users</strong> to initiate a <strong>manual backup</strong> of the application's <strong>configuration files</strong> and <strong>database</strong>.</p>\n<p>This API is essential for creating point-in-time backups to ensure <strong>recovery</strong>, <strong>auditability</strong>, and <strong>continuity</strong> in case of failure or data loss.</p>\n<p>By triggering this API, users can <strong>programmatically initiate</strong> a backup process without relying on scheduled tasks, enabling integration with external backup management systems.</p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<p><strong>Note</strong>: Users must provide atlease one perameters of <strong>backupProperties</strong> or <strong>backupDatabase</strong>; both parameters also be included in the same request</p>\n<p><strong>Table no 1</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>backupProperties</td>\n<td>Boolean</td>\n<td>Its Conditional, Indicates whether configuration files should be backed up  <br />  <br />ex:- true</td>\n</tr>\n<tr>\n<td>backupDatabase</td>\n<td>Boolean</td>\n<td>Indicates whether the database should be backed up..  <br />  <br />ex:- false</td>\n</tr>\n<tr>\n<td>filePath*</td>\n<td>String</td>\n<td>Absolute path where the backup files should be stored.  <br />  <br />ex:-  <br />\"/backup/emca\"</td>\n</tr>\n<tr>\n<td>async</td>\n<td>Boolean</td>\n<td>If set to true, the backup will be performed asynchronously in background.  <br />  <br />e: false</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","backup","manual"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"a078f39a-324f-4e42-a492-49b0eb3420f8"},{"name":"manualBackupStatus","id":"7e61c60b-35eb-4a3b-83bf-e36bd6a96f71","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[],"url":"https://appemca.emudhra.com/emCAServices431/rest/backup/manual/status/<transactionId>","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The \"<strong>manualBackupStatus</strong>\" API is used to <strong>track the status</strong> of a <strong>manual backup operation</strong> that was initiated with <strong><code>\"async\": true</code></strong>.</p>\n<p>When a manual backup is triggered asynchronously, the system immediately returns a unique <strong><code>transactionId</code></strong>. This API allows users or external systems to <strong>query the current state</strong> of that backup operation by passing the <code>transactionId</code> in the URL.</p>\n<p>This is essential for monitoring long-running backup processes and ensuring timely notifications or follow-up actions based on the outcome.</p>\n<p><strong>Possible Status Values:</strong></p>\n<ul>\n<li><p><code>IN_PROGRESS</code> – The backup is still running.</p>\n</li>\n<li><p><code>COMPLETED</code> – The backup finished successfully.</p>\n</li>\n<li><p><code>FAILED</code> – The backup process encountered an error.</p>\n</li>\n</ul>\n<p><strong>URL</strong><br /><a href=\"https://appemca.emudhra.com/emCAServices431/rest/backup/manual/status/%7BtransactionId%7D\">https://appemca.emudhra.com/emCAServices431/rest/backup/manual/status/{transactionId}</a></p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<p><strong>Note</strong>: Users must provide either the serial number or the request ID; both parameters cannot be included in the same request</p>\n<p><strong>Table no 1</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>transactionId</td>\n<td>String</td>\n<td>Unique ID returned when the manual backup was initiated asynchronously. This ID is used to fetch the current status of that specific backup job.r  <br />  <br />Ex :- “a3f29d4c-5e2b-4d16-bfd5-8a7d2ecf49f1”</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","backup","manual","status","<transactionId>"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"7e61c60b-35eb-4a3b-83bf-e36bd6a96f71"},{"name":"AutomcaticBackup","id":"44c0fad0-edaf-4b07-a7cf-cdf352fb6c7e","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"},{"key":"X-Client-ID","value":"{{x_client_id}}","type":"text"},{"key":"X-Emca-Api-Key","value":"{{x_emca_api_key}}","type":"text"}],"body":{"mode":"raw","raw":"{\r\n  \"backupProperties\": true,\r\n  \"backupDatabase\": true,\r\n  \"filePath\": \"/backup/emca\",\r\n  \"frequency\": \"Daily\",\r\n  \"scheduledTime\": \"02:00\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://appemca.emudhra.com/emCAServices431/rest/backup/schedule","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The <strong>\"automaticBackup\"</strong> feature allows the application to <strong>schedule automated backups</strong> of configuration files and database at predefined <strong>time intervals</strong>.</p>\n<p>This functionality ensures that critical data and configuration are <strong>backed up regularly</strong> without manual intervention, supporting <strong>disaster recovery</strong>, <strong>compliance</strong>, and <strong>operational continuity</strong>.</p>\n<p>Administrators can configure backup frequency, location, and retention policies to align with organizational requirements.</p>\n<p>Once configured, the system will automatically perform backups as per the defined <strong>schedule</strong>, reducing the risk of data loss due to unexpected failures.</p>\n<h3 id=\"request-input-parameters\"><strong>Request Input Parameters</strong></h3>\n<p>* - Mandatory parameter</p>\n<p><strong>Table no 1</strong></p>\n<div class=\"click-to-expand-wrapper is-table-wrapper\"><table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Data Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>backupProperties</td>\n<td>Boolean</td>\n<td>Indicates whether configuration files should be included in the backup.</td>\n</tr>\n<tr>\n<td>backupDatabase</td>\n<td>Boolean</td>\n<td>Indicates whether the database should be included in the backup.</td>\n</tr>\n<tr>\n<td>filePath*</td>\n<td>String</td>\n<td>Absolute path where the backup files will be stored.</td>\n</tr>\n<tr>\n<td>frequency*</td>\n<td>String</td>\n<td>How often the backup should occur. Supported values: <strong>Daily</strong>, <strong>Weekly</strong>, <strong>Monthly</strong>.</td>\n</tr>\n<tr>\n<td>scheduledTime*</td>\n<td>String</td>\n<td>Time at which the backup should start (24-hour format, e.g., 02:00).</td>\n</tr>\n</tbody>\n</table>\n</div>","urlObject":{"protocol":"https","path":["emCAServices431","rest","backup","schedule"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"44c0fad0-edaf-4b07-a7cf-cdf352fb6c7e"},{"name":"AutomcaticbackupStatus","id":"5b24c4e3-9d3f-4d95-8a3c-66f723c6c795","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"key":"X-Nonce","value":"{{x_nonce}}","type":"text"},{"key":"X-Client-ID","value":"{{x_client_id}}","type":"text"},{"key":"X-Emca-Api-Key","value":"{{x_emca_api_key}}","type":"text"}],"url":"https://appemca.emudhra.com/emCAServices431/rest/backup/schedule/status","description":"<h3 id=\"purpose\">Purpose</h3>\n<p>The <strong>\"automaticBackupStatus\"</strong> API is used to <strong>check the current status</strong> and configuration of the scheduled automatic backup feature.</p>\n<p>This API provides detailed insights into:</p>\n<ul>\n<li><p>Whether <strong>automatic backups</strong> are currently <strong>enabled</strong></p>\n</li>\n<li><p>The <strong>last backup execution time</strong></p>\n</li>\n<li><p>The <strong>next scheduled backup time</strong></p>\n</li>\n</ul>\n<p>This functionality ensures administrators can <strong>monitor scheduled backup health</strong>, verify <strong>execution history</strong>, and ensure backups are aligned with disaster recovery and compliance strategies.</p>\n<p>By querying this API, users gain visibility into backup automation and can take necessary actions if backups are missed or delayed.</p>\n","urlObject":{"protocol":"https","path":["emCAServices431","rest","backup","schedule","status"],"host":["appemca","emudhra","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"5b24c4e3-9d3f-4d95-8a3c-66f723c6c795"}],"id":"121f3173-a6ad-48cb-b69b-538de087f612","description":"<p>The <strong>Backup Management APIs</strong> provide a secure and programmatic interface for managing the backup lifecycle of the application's critical components, including configuration files and databases. These APIs enable both automated and manual control over backup operations to support disaster recovery, compliance, and operational resilience.</p>\n<p>They are designed for use by administrators or authorized external applications, and can be easily integrated into enterprise backup workflows or third-party management systems.</p>\n<h3 id=\"key-capabilities-include\">Key Capabilities Include:</h3>\n<ul>\n<li><p><strong>Manual Backup Initiation</strong>: Trigger on-demand backups via the <code>manualBackup</code> API.</p>\n</li>\n<li><p><strong>Scheduled Backup Control</strong>: Configure and manage automatic backup schedules.</p>\n</li>\n<li><p><strong>Backup Status Monitoring</strong>: Retrieve logs or status of current and past backup operations.</p>\n</li>\n<li><p><strong>Retention &amp; Cleanup Management</strong>: Manage backup retention policies and clean up outdated backup files.</p>\n</li>\n</ul>\n<p>All backup operations are executed securely and recorded for audit and compliance purposes.</p>\n<h3 id=\"security--access-control\">Security &amp; Access Control:</h3>\n<p>Access to the Backup Management APIs is restricted to authorized users and systems via:</p>\n<ul>\n<li><p><strong>X-Client-ID</strong> for tenant scoping</p>\n</li>\n<li><p><strong>X-Emca-Api-Key</strong> for authentication</p>\n</li>\n<li><p><strong>X-Nonce</strong> to prevent replay attacks</p>\n</li>\n</ul>\n<p>By using these APIs, organizations can maintain reliable backup and restore capabilities with flexibility, transparency, and automation, ensuring continuity and protection of critical data.</p>\n<p>Note : This will only work if user have required preveledge for backup.</p>\n","_postman_id":"121f3173-a6ad-48cb-b69b-538de087f612"}],"event":[{"listen":"prerequest","script":{"type":"text/javascript","packages":{},"exec":["function generateUUID() {\r","    let d = new Date().getTime();\r","    if (typeof performance !== 'undefined' && typeof performance.now === 'function'){\r","        d += performance.now(); // use high-precision timer if available\r","    }\r","    return 'xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx'.replace(/[xy]/g, function(c) {\r","        const r = (d + Math.random()*16)%16 | 0;\r","        d = Math.floor(d/16);\r","        return (c==='x' ? r : (r&0x3|0x8)).toString(16);\r","    });\r","}\r","\r","const nonce = `${Date.now()}-${generateUUID()}`;\r","\r","// Set it as a global or local variable\r","pm.variables.set(\"x_nonce\", nonce);\r","pm.variables.set(\"x_client_id\", \"0cad7eec-5b4b-4758-8157-8e28d2aee7e0\");\r","pm.variables.set(\"x_emca_api_key\", \"eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJncnBJZCI6IjEiLCJBdXRoS2V5IjoiTUdOaFpEZGxaV010TldJMFlpMDBOelU0TFRneE5UY3RPR1V5T0dReVlXVmxOMlV3IiwiaWF0IjoxNzUyNzI4OTAwLCJleHAiOjE3NTI3MzI1MDB9.mL7c7ixJbCrwEFe4RmhrSigUMkSkWO9nqB6ATiv-bNU\");"],"id":"0ed407be-d6af-4643-bcfe-8fa47f8bcaa9"}},{"listen":"test","script":{"type":"text/javascript","packages":{},"exec":[""],"id":"0addc67c-ad19-4955-93fb-33fc1ee6a400"}}]}