Qualified electronic signatures with Cleverbase as your qualified trust service provider (QTSP): what you get from us, what you build yourself, and how to build it so that every viewer agrees on the result. This is the API for the Signing service.
This area is a full guide, and it covers one path completely: remote qualified signing over the Cloud Signature Consortium API (CSC API v1.0.4), producing a PAdES signature in a PDF. Cleverbase signs a hash for you; the document is yours to build. The guide walks that path with two libraries, DSS (Java) and pyHanko (Python), documents every endpoint and its required values, describes the screens the signer gets and cannot skip, and ends with the pitfalls we see in signed PDFs that no validator reports but every reader notices.
Other formats (CAdES for arbitrary files, XAdES for XML) exist and are mentioned where they matter, but are not worked out here yet; the same goes for CSC API v2, which has a reference page and no guide.
Start where your question is
Or browse by kind
Every page here is one of three kinds, so you know what you are opening. How-to guides get one thing done in steps and assume you know the basics. Reference describes the hosts, the endpoints and the values Cleverbase requires, for looking up while you code. Explanation is for understanding: why the work is split the way it is, what the signer goes through, what the value you get back really is, what each PAdES level adds. New here? Read How the work is split first, then follow The signing flow.