Troubleshooting your ATS connection
Solutions to the most common issues when connecting or maintaining an ATS integration with Remote Jobster.
Connection errors after entering an API key
Invalid API key: double-check that you have copied the key in full with no trailing spaces. Some ATS platforms display keys in a way that makes accidental partial selections easy.
Insufficient permissions: some ATS platforms require specific permission scopes on API keys. Check the individual integration guide for your ATS to confirm the required scopes (usually "Candidates: Read & Write" and "Jobs: Read").
Wrong subdomain or company identifier: several ATS platforms (Workable, BreezyHR, Recruitee) require your company-specific subdomain in addition to the API key. Ensure this field is filled in correctly.
Applications not appearing in your ATS
Check your job mapping: if a Remote Jobster listing is not mapped to an ATS job, applications for that listing will not be forwarded. Navigate to Settings → Integrations → your ATS and verify that all active listings are mapped.
Check your ATS for errors: some ATS platforms log failed incoming API calls. Check your ATS integration or webhook log for entries around the time of the missing application.
Expired API key: API keys can expire or be revoked in your ATS settings. If your integration was working and has suddenly stopped, try regenerating your API key and updating it in Remote Jobster.
Getting further help
If you have worked through the above and the issue persists, contact our support team at hello@remotejobster.com. Include your ATS name, the listing affected, and the date and time of the application that did not appear — this information allows us to trace the issue quickly.
Was this article helpful?