1. API Key Generation
After generating your API key (see How to Manage Your API Keys (On Premise, SCIM, Public APIs) | Letsignit Help Center), you can use our public API to retrieve your collaborators' signatures.
The API key must be used as a Bearer Token (see RFC 6750 - The OAuth 2.0 Authorization Framework: Bearer Token Usage).
2. Endpoint
GET https://api.letsignit.com/public/api/v1/signature/
3. Required Headers
Accept: application/jsonAuthorization: Bearer <API_KEY>
4. Usage Examples
a) cURL
curl -X GET \
'https://api.letsignit.com/public/api/v1/signature/<USEREMAIL>' \
-H 'Accept: application/json' \
-H 'Authorization: Bearer <API_KEY>'
b) Python (requests)
import requests
url = "https://api.letsignit.com/public/api/v1/signature/<USEREMAIL>"
headers = {
"Accept": "application/json",
"Authorization": "Bearer <API_KEY>"
}
response = requests.get(url, headers=headers)
print(response.json())
c) Node.js (Axios)
const axios = require('axios');
const url = "https://api.letsignit.com/public/api/v1/signature/<USEREMAIL>";
const headers = {
"Accept": "application/json",
"Authorization": "Bearer <API_KEY>"
};
axios.get(url, { headers })
.then(response => console.log(response.data))
.catch(error => console.error(error));5. Response Example5. Response example
The API call returns a JSON object with the following structure:
{
"name": "Signature name",
"content": "<html>Signature content in HTML</html>",
"reply": "<html>Reply variant content if defined</html>"
}Field Descriptions
name(string): Unique signature name.content(string): Main signature content in HTML format.reply(string, optional): HTML variant used for replies, if defined.
6. Complete Documentation
You can view the complete technical documentation here: Public API - Swagger UI.