Before you start
You need someone who can open Settings > Edit Settings in ApplicantStack. That page shows your account's access token.
ApplicantStack does not sell the API separately and does not name a plan for it.
You will paste two things into Metaintro: your ApplicantStack domain and the access token.
Create the credential in ApplicantStack
ApplicantStack gives each account one access token. You do not create a new one. These steps follow ApplicantStack's API Integration Guide.
Sign in to ApplicantStack.
Go to Settings > Edit Settings.
Copy the access token.
Note your domain. It is the part before .applicantstack.com in your ApplicantStack address, and it is also shown on the same page.
The token works only with its own domain. Anyone with the token can read and change your candidates, so share it only through the Metaintro form.
Connect in Metaintro
In Metaintro, go to Settings > Integrations.
Choose ApplicantStack.
In Account subdomain, enter the part before .applicantstack.com.
In API token, paste the access token.
Select Connect.
Then map your jobs, set your rules, check the preview and go live.
What Metaintro sends and reads
Metaintro only sends people who chose to share their profile with you for a specific job.
Jobs: Metaintro reads your ApplicantStack jobs so you can map them.
Candidate: Metaintro creates a candidate on the mapped job with their name, email and phone, and sets the source to Metaintro. Changes show Metaintro as the publisher in the candidate's history.
Résumé: sent with the candidate when the person has one.
Proof card: ApplicantStack has no notes in its API, so the link to the person's proof card goes in the cover letter.
In ApplicantStack, each candidate record belongs to one job. If the person is already a candidate on another job, Metaintro creates a new candidate on this job.
Metaintro checks each candidate in ApplicantStack regularly and reads their stage and disposition. Hired, not selected and withdrawn are read from them. Metaintro can also move the candidate to a stage with a common name, such as Interview, Offer or Hired.
Limits
ApplicantStack does not return the new candidate's ID when Metaintro creates one, so Metaintro finds the candidate by email straight afterwards. A person without an email address cannot be sent.
To find candidates, Metaintro reads your whole candidate list. If your account has more than about 10,000 candidates, Metaintro cannot be sure whether a person is already there, and it stops rather than risk a duplicate.
ApplicantStack's stage alerts carry a shared password rather than a signature, so Metaintro checks stages regularly instead. Changes reach Metaintro on its next check, not right away.
If a candidate with the same email is already on the job without this proof card, Metaintro does not send them again.
Metaintro can only move a candidate to a stage whose name it recognises. If your stages have other names, move the candidate in ApplicantStack.
If something goes wrong
The token is rejected: copy it again from Settings > Edit Settings, and check that the subdomain matches the same account.
A person was not sent: check that they have an email address, and that the job still exists in ApplicantStack.
Delivery stopped with a search message: your account has more candidates than Metaintro can safely search. Contact Metaintro support.
Stages are late: Metaintro checks regularly, so a change can take a while to show. Nothing needs to be done.