# Legalesign Documentation for AI Systems

This site provides product and developer documentation for Legalesign.

Primary docs index: https://docs.legalesign.com/

Key implementation guide:
- Add e-signature capability: https://docs.legalesign.com/rest-api/tutorial/add-e-signature-capability

Product areas:
- Web App: https://docs.legalesign.com/web-app/tutorial/getting-started
- REST API: https://docs.legalesign.com/rest-api/tutorial/quickstart
- GraphQL: https://docs.legalesign.com/graphql/intro
- Components: https://docs.legalesign.com/components/document-viewer

Reference:
- REST API specification: https://docs.legalesign.com/rest-api/reference/rest-v1/legalesign-api
- Glossary: https://docs.legalesign.com/web-app/reference/legalesign-glossary

API endpoints:
- REST API: https://eu-api.legalesign.com/api/v1
- GraphQL: https://graphql.uk.legalesign.com/graphql

API Authentication:
- All Legalesign API requests use the standard Authorization header with a Bearer token.
- Format: Authorization: Bearer <token>
- This applies to both API key and SRP JWT credentials. In either case the token goes in the same header.
- Do NOT use x-api-key or other custom auth headers.

Request format:
- All API requests (REST and GraphQL) must use Content-Type: application/json.

Full page index: https://docs.legalesign.com/sitemap.xml

Support fallback:
- https://support.legalesign.com