Getting Help
We're here to help you get the most out of Systango Inhibitor. Choose the support option that best fits your needs.
Documentation
Start with our Integration Guide for API documentation, code examples, and best practices. It covers:
- Quick start guide for setting up Inhibitor
- POST /v3/evaluate endpoint for text evaluation
- POST /v3/document-evaluate endpoint for document scanning
- Request/response shapes and error codes
- Code examples in cURL, Python, Node.js, and async variants
Common Issues
API Key Issues
Problem: "Unauthorized" or 401 error when calling the API.
- Verify your API key is correct and not expired
- Check that the X-API-Key header is included in your request
- Ensure you're using the correct endpoint base URL
- If your key was recently created, allow a few seconds for propagation
Rate Limiting
Problem: "Rate Limited" or 429 error.
- Your app has exceeded its inference quota for this billing period
- Contact support to review your plan or increase limits
- Implement exponential backoff retry logic for resilience
Validation Errors
Problem: "Validation Error" or 422 error.
- Check that all required fields are present in your request
- Verify field types match (e.g., input must be a string, actor_profile must be an object)
- Ensure your JSON is well-formed and doesn't contain extra/unexpected fields
Document Upload Issues
Problem: Document evaluation fails or returns an error.
- Supported formats: PDF, DOCX, XLSX, CSV, TXT
- Ensure the file is not corrupted
- Check that file size is within limits
- Verify multipart/form-data headers are correct
Troubleshooting Steps
1. Verify Your Setup
- Confirm the API endpoint URL is correct
- Test connectivity with a simple curl request
- Verify your API key is valid and active
2. Check the Response
- Log the full HTTP response, including headers and body
- Look for detailed error messages in the response JSON
- Check the evaluation_id to trace logs server-side
3. Test with Minimal Request
Start with a minimal valid request to isolate issues:
curl -X POST https://your-api-url/v3/evaluate \ -H "Content-Type: application/json" \ -H "X-API-Key: inh-your_api_key_here" \ -d {"input": "Hello world"}Understanding Decision Results
ALLOW
Content passed all policy checks. Forward the original input to your LLM unchanged.
MODIFY
Content was sanitised or disclosures were injected. Use modified_content instead of the original, and append any items in disclosures_injected to the LLM response.
BLOCK
A hard-stop policy violation was detected. Do not forward to your LLM. Surface a safe rejection message to the user and log the violation details.
Performance & Best Practices
Optimize Response Time
- Keep input text concise where possible
- Batch evaluations for better throughput (if supported)
- Implement client-side caching for repeated content
Error Handling
- Always implement exponential backoff for retries
- Don't retry on 401 (auth issues) or 422 (validation)
- Log evaluation_id with each request for debugging
Security
- Never expose your API key in client-side code
- Always use HTTPS for API calls
- Rotate API keys periodically
- Store keys securely (e.g., environment variables, secrets manager)
Contact Support
If you can't find the answer to your question, reach out to our support team:
- Email: support@systango.com
- Documentation: Integration Guide
- Privacy Policy: Privacy Policy
When contacting support, please include:
- Your evaluation_id from the response
- The exact request you sent (without API keys)
- The full error response
- Your app name and environment (dev/staging/prod)
Monitoring & Logging
Each evaluation request returns an evaluation_id and audit_id. Use these to:
- Trace evaluations in your application logs
- Look up detailed audit records server-side
- Debug policy violations with support
- Track performance metrics over time
Service Status
For real-time service status, system uptime, and incident reports, contact our support team at support@systango.com.