Reissuing a certificate looks up the signing request from which the given certificate was generated and generates a new certificate with the same values, including the same private and public keys. The reissued certificate will be valid for one year from the time the reissue request was made.

If the status of the original certificate was "good" or "hold", it will automatically be changed to "obsolete".

Once the API call completes successfully, a new certificate will have been generated, with a new ID. The ID of the original certificate should not be used in any further API calls in this or any other sessions. Also, it will no longer be present in responses to any subsequent calls to /cert/list.


https://www.tinycert.org/api/v1/cert/reissue (JSON)
https://www.tinycert.org/api/v1/cert/reissue.xml (XML)



Numeric identifier of the certificate to reissue.


Session identifier.

Return value

When a certificate has been successfully reissued, the API call will return the numeric identifier for the new certificate.


New certificate's identifier. This may be used in API calls to /cert/details, /cert/get and /cert/status.

  1. Introduction
    1. Signing requests
    2. Error conditions
  2. API sessions
    1. /connect: Open a new API session
    2. /disconnect: Close an open API session
  3. Certificate Authority management
    1. /ca/list: Get a list of all CAs in your account
    2. /ca/details: Get further details on a given CA
    3. /ca/get: Download the CA's certificate
    4. /ca/delete: Delete a given CA
    5. /ca/new: Create a new CA
  4. Certificate management
    1. /cert/list: Get a list of all certificates for a given CA
    2. /cert/details: Get further details on a given certificate
    3. /cert/get: Download the certificate, signing request, or private key for a certificate
    4. /cert/reissue: Re-issue an existing certificate
    5. /cert/status: Change certificate status
    6. /cert/new: Create a new certificate