Developer Docs

FAQ & Troubleshooting

Common implementation questions for Vitae APIs, matching workflow issues, and practical fixes for integration problems.

This FAQ provides quick answers for common implementation issues. Each answer is intentionally short, with links to deeper pages in the docs sidebar.

Why do I get 401 Unauthorized?

Your bearer token is missing, invalid, expired, or malformed.

Why do I get 403 on matching?

Matching endpoint access requires Professional or Enterprise tier.

Why do I get 422 even though JSON is valid?

422 means schema validation failed. Common causes are short job descriptions, out-of-range top_n, or unknown fields in payload.

Why are matches empty?

Empty results can be valid. Check threshold value, filters, and candidate data quality.

How should I handle 429 responses?

Use exponential backoff for minute-level limits and queue non-urgent jobs for daily quota exhaustion.

Why does template preview fail after .sty edits?

Revert the latest change and re-apply incrementally. Validate placeholders and command mapping.

Why does logo not render in template output?

Confirm logo file is available, show_logo is enabled, and %%companylogo%%is present in template.