Courses / Applicant Tracking System (ATS)
1. ATS account setup
Creating and initializing an ATS tenant/account including basic organization metadata and contact settings.
How It Works
Think of the ATS tenant like a new office: you provision the office (create tenant), put up signs and phone numbers (metadata and contact settings), and connect the delivery entrance (SFTP/CSV intake) so resumes and notifications arrive correctly.
Call the ATS "create tenant" API with required org fields (name, region, admin email).
Use the returned tenant ID and API key to PATCH organization settings (timezone, locale, default hiring locations).
Configure contact channels: set recruiter email, default from-address, and webhook/SFTP endpoints for inbound resumes.
Upload initial CSV or enable SFTP with credentials so candidate import and scheduled feeds start flowing.
See It
The script shows three steps: creating the tenant, updating settings, and uploading a CSV. In reality the create call returns a tenant_id and api_key you must capture and use for subsequent requests; try changing timezone to "Europe/London" to see localized timestamps in the ATS UI.
Use It
Onboarding a new recruiting team so their ATS is ready with locations, recruiter contacts, and an initial candidate list.
Automating these steps ensures every new team has consistent contact settings and a working feed endpoint so resumes and notifications don't get lost.
Break It
What will this script print or do when run against the real ATS API?
Many ATS APIs wrap payloads: the create endpoint returns {"data":{"tenant_id":"tnt","api_key":"sk_..."}} rather than top-level fields. jq -r '.api_key' therefore extracts nothing and yields "null" (or empty), so the Authorization header is invalid and the PATCH is rejected. The root cause is assuming flat JSON instead of inspecting the real response shape.
Read the actual nested field (e.g., .data.api_key) from the create response and validate it's non-empty before using it.
Level Up
Idempotent tenant creation: Re-runable create logic that checks for an existing tenant (by domain or admin email) and returns the existing tenant_id instead of erroring, preventing duplicate accounts.
Atomic seed and rollback: Use a transaction-style sequence: create tenant, seed contacts and CSVs, and if any step fails, call the tenant-delete API to avoid half-configured tenants.
Secure SFTP lifecycle automation: Rotate SFTP keys and programmatically distribute them to partner systems on a schedule to maintain secure inbound feeds without manual key handling.
Prove It
Write a bash script that creates a tenant, extracts the nested tenant_id and api_key from {"data":{...}}, then uploads a small CSV to /tenants/{tenant_id}/uploads using the api_key; exit nonzero on any failure.
Integration/Automation (APIs, CSV, SFTP)
ATS account setup
Creating and initializing an ATS tenant means programmatically making a new account and seeding it with organization metadata and contact settings so hiring teams can start using it.
"I need new hiring teams to be ready to source, track, and email candidates without manual clicks."
ATS account setup is the automated process of creating a tenant via the ATS API, applying organization-level metadata (company name, timezone, hiring locations), and configuring contact/email and SFTP/CSV intake settings so integrations work immediately.
"I need new hiring teams to be ready to source, track, and email candidates without manual clicks."
ATS account setup is the automated process of creating a tenant via the ATS API, applying organization-level metadata (company name, timezone, hiring locations), and configuring contact/email and SFTP/CSV intake settings so integrations work immediately.