Upload, query, and delete the CSDs in your account. The same certificates you manage in the CFDI Stamp Management (ADT), from your code.
View SDKs- 1Get a Bearer Token using your SW username and password. We recommend using an infinite (non-expiring) token. All five operations require it in the
Authorizationheader. - 2Have the issuer’s
.cerand.keyfiles in Base64, plus the private key password, at hand. For testing, use the current test CSDs. - 3Upload the CSD once per issuer. After that you can stamp: the Stamping service uses the CSDs you have uploaded.
URLs
Select your active environment. The copy buttons and the code examples below are built with the base URL you choose here.
🔗 Endpoint
Three actions on the same resource. Pick one and its full reference is built below: endpoint, headers, parameters, example, and response.
Uploads an issuer’s CSD to your account. This service receives the .cer and .key in Base64, plus the private key password. It’s the prerequisite for stamping with that RFC.
success with an empty data array.Returns a single certificate by its serial number. Useful to check its validity before stamping.
Returns all the uploaded certificates for a single taxpayer.
Service that deletes a certificate from the account, using the certificate number as a parameter.