Skip to main content

Support Resources

Documentation

Comprehensive guides and API reference

Platform

Document processing UI, API key management, and usage monitoring

Status Page

Check service status and incidents

Contact Support

Email Support

General Support

support@trypulse.ai
  • Technical questions
  • Integration help
  • Bug reports
  • Feature requests

General Inquiries

hello@trypulse.ai
  • Strategic partnerships
  • Enterprise inquiries
  • Product feedback
  • Special requests

Common Issues

Problem: Getting AUTH_002 Invalid API key errorSolutions:
  1. Verify your API key in the Platform
  2. Check you’re using the correct environment (production vs test)
  3. Ensure the x-api-key header is properly formatted
  4. Regenerate your API key if needed
Problem: FILE_001 Invalid file typeSolutions:
  1. Check supported formats: PDF, JPG/JPEG, PNG, DOCX, PPTX, XLSX, HTML
  2. Verify file extension matches content
  3. Ensure file isn’t corrupted
Problem: FILE_002 File too largeSolutions:
  1. Contact support for large files
  2. Consider using async processing
  3. Split very large documents if needed
Problem: Job timing out or failingSolutions:
  1. Use smaller page ranges for complex documents
  2. Check job status regularly
  3. Implement proper error handling
Problem: Missing or incorrect data in schema extractionSolutions:
  1. Use descriptive field names matching document terminology
  2. Provide schema prompts for context
  3. Start with simple schemas and add complexity
  4. Make optional fields nullable
Problem: Getting rate limited or BILLING_001 errorsSolutions:
  1. Check current usage in Console
  2. Implement client-side rate limiting
  3. Use caching to avoid reprocessing
  4. Upgrade plan for higher limits

Best Practices

Before Contacting Support

1

Check Documentation

Review relevant documentation sections for your issue
2

Verify Error Details

Note the exact error code and message
3

Test with Simple Case

Try a basic example to isolate the issue
4

Gather Information

Collect request/response details, file samples, and code snippets

What to Include in Support Requests

Additional Context: [Any other relevant information]

Debug Mode

Enable detailed logging for troubleshooting:

FAQ

  1. Sign up at platform.runpulse.com/
  2. Generate an API key
  3. Follow the Quickstart Guide
  4. Start with simple extractions before adding complexity
/extract supports both synchronous and asynchronous modes:
  • Sync (default): Best for documents under 50 pages. Returns the result directly.
  • Async (async: true): Returns a job_id for polling via GET /job/{jobId}. Recommended for large documents.
  • The deprecated /extract_async endpoint still works but redirects to /extract with async: true.
See Async Processing for full details.
Accuracy depends on:
  • Document quality (resolution, clarity)
  • Content type (typed vs handwritten)
  • Schema complexity
Typical accuracy: 95-99% for high-quality documents
Yes! Pulse API supports 100+ languages including:
  • European languages (Spanish, French, German, etc.)
  • Asian languages (Chinese, Japanese, Korean, etc.)
  • RTL languages (Arabic, Hebrew)
  • And many more
Yes, we take security seriously:
  • ISO 27001 certified
  • SOC 2 Type II certified
  • GDPR compliant
  • HIPAA compliant
  • Data encrypted in transit and at rest
  • Automatic deletion after 48 hours
  • No data used for training
For more details, visit our security page.