> ## Documentation Index > Fetch the complete documentation index at: https://superdoc-caio-pizzol-docs-ai-core-preset.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Verify > Verify the signature and integrity of a signed PDF. Send a JSON request body with: - `document`: object containing either `base64` or `url` The response includes verification status, signer information, and document metadata. ## OpenAPI ````yaml /openapi.json post /v1/verify openapi: 3.0.3 info: title: SuperDoc API version: 0.9.0 description: >- ## Quick Start 1 - **Register**: https://api.superdoc.dev/v1/auth/register?email=you@email.com 2 - **Verify**: Check email, then https://api.superdoc.dev/v1/auth/verify?email=you@email.com&code=123456 3 - **Convert** ```bash curl -X POST https://api.superdoc.dev/v1/convert?from=docx \ -H "Authorization: Bearer YOUR_API_KEY" \ -F "file=@document.docx" \ -o converted.pdf ``` Or use our Playground: https://api.superdoc.dev/docs/#tag/documents/post/v1/convert That's it! Your DOCX is now a PDF. --- [Status](https://status.superdoc.dev) • [GitHub](https://github.com/superdoc-dev/superdoc) contact: name: Support email: api@superdoc.dev url: https://superdoc.dev/contact-us license: name: Commercial url: https://superdoc.dev servers: - url: https://api.superdoc.dev description: Production security: [] tags: - name: Documents description: Document conversion and transformation - name: Authentication description: Registration and API key management - name: System description: Health and service information paths: /v1/verify: post: tags: - Verification summary: Verify description: >- Verify the signature and integrity of a signed PDF. Send a JSON request body with: - `document`: object containing either `base64` or `url` The response includes verification status, signer information, and document metadata. requestBody: content: application/json: schema: $ref: '#/components/schemas/VerifyRequest' responses: '200': description: Default Response content: application/json: schema: $ref: '#/components/schemas/VerifyResponse' '400': description: Standard error format used across all API endpoints content: application/json: schema: type: object title: Error Response description: Standard error format used across all API endpoints required: - code - error - message properties: code: type: string description: Machine-readable error code for programmatic handling example: VALIDATION_ERROR error: type: string description: HTTP error category example: Bad Request message: type: string description: Human-readable error description example: The provided document format is not supported requestId: type: string description: Unique request ID for support example: req_abc123 details: type: array description: Additional error details for validation errors items: type: object properties: field: type: string description: Field that caused the error issue: type: string description: Description of the issue example: code: INVALID_FILE_FORMAT error: Bad Request message: File is not a valid DOCX requestId: req_abc123 '413': description: Standard error format used across all API endpoints content: application/json: schema: type: object title: Error Response description: Standard error format used across all API endpoints required: - code - error - message properties: code: type: string description: Machine-readable error code for programmatic handling example: VALIDATION_ERROR error: type: string description: HTTP error category example: Bad Request message: type: string description: Human-readable error description example: The provided document format is not supported requestId: type: string description: Unique request ID for support example: req_abc123 details: type: array description: Additional error details for validation errors items: type: object properties: field: type: string description: Field that caused the error issue: type: string description: Description of the issue example: code: INVALID_FILE_FORMAT error: Bad Request message: File is not a valid DOCX requestId: req_abc123 '500': description: Standard error format used across all API endpoints content: application/json: schema: type: object title: Error Response description: Standard error format used across all API endpoints required: - code - error - message properties: code: type: string description: Machine-readable error code for programmatic handling example: VALIDATION_ERROR error: type: string description: HTTP error category example: Bad Request message: type: string description: Human-readable error description example: The provided document format is not supported requestId: type: string description: Unique request ID for support example: req_abc123 details: type: array description: Additional error details for validation errors items: type: object properties: field: type: string description: Field that caused the error issue: type: string description: Description of the issue example: code: INVALID_FILE_FORMAT error: Bad Request message: File is not a valid DOCX requestId: req_abc123 components: schemas: VerifyRequest: type: object title: Verify Request required: - document properties: document: type: object description: Signed PDF provided as either base64 or URL VerifyResponse: type: object title: Verify Response required: - valid properties: valid: type: boolean description: Whether the signature is valid reason: type: string description: Explanation of verification result signer: description: Primary signer information signers: type: array description: All signers (only when valid) document: type: object description: Document metadata (only when valid) ````