Integrating with Spott

this guide covers creating an api key https //docs pin com/integrating with spott#generate an api key in spott connecting spott to pin https //docs pin com/integrating with spott#connecting spott to pin configure job syncing https //docs pin com/integrating with spott#configure job syncing syncing candidates to spott https //docs pin com/integrating with spott#syncing candidates to spott when candidates sync to spott https //docs pin com/integrating with spott#when candidates sync to spott candidate data synced to spott https //docs pin com/integrating with spott#candidate data synced to spott manually syncing a candidate to spott https //docs pin com/integrating with spott#manually syncing a candidate to spott checking if a candidate synced to spott https //docs pin com/integrating with spott#checking if a candidate synced to spott disconnecting spott from pin https //docs pin com/integrating with spott#disconnecting spott from pin troubleshooting https //docs pin com/integrating with spott#troubleshooting pin integrates directly with spott (v2), so candidates and job positions you work in pin can sync straight into your spott pipeline this guide walks through generating an api key in spott and connecting it in pin before you start you'll need admin access in spott to generate an api key, and access to settings → ats integration in pin to connect it generate an api key in spott in spott https //app spott io/ , click your workspace name in the top left corner and select settings in the settings sidebar, go to api , then click + create api key give the key a name that makes it easy to identify later — for example, pin integration — so you (or your team) can tell at a glance what it's used for if you need to manage or revoke it down the line click create key spott shows the new key once click copy key and save it somewhere safe — you'll paste it into pin in the next step one time only this is your only chance to copy the api key spott will not show the key again if you lose it, you'll need to generate a new one and reconnect important a spott api key is tied to both your workspace and the spott user who created it — every action the integration performs will show as done by that user if that person leaves or loses access, generate a fresh key from another admin account and reconnect connecting spott to pin in pin, go to settings → ats integration find spott (v2) in the list of supported ats platforms and select it paste the api key you copied from spott into the api key field click connect to ats configure job syncing once connected, the spott (v2) card shows connected , with a disconnect option if you ever need to remove the integration below that, once you set the sync option and ats position on each job, pin lists each job position, alongside sync to ats — the trigger that determines when a candidate on that position gets pushed to spott (for example, once they're added to an outreach sequence) ats position — the matching position in spott that candidates should sync into syncing candidates to spott to sync candidates from each job in pin to a specific job in spott go to job settings > position details scroll to the ats integration section c hoose when to sync candidates by selecting one of the following triggers never they're added to an outreach sequence contact information is found they receive their first message t hey reply to an email they reply to an email and are interested s elect the spott job and stage you want to sync candidates to once you've selected your preferred triggers, pin will automatically update the settings and sync candidates to the selected job in spott based on the chosen trigger reminder you’ll need to set up the syncing for each job you want to send from pin to spott in the position details tab within the job settings we recommend setting up the job sync before adding candidates to outreach this ensures candidates sync correctly to the job without issues if you prefer not to sync candidates to a job, you can still set up a trigger and leave the job field empty when candidates sync to spott once the selected trigger occurs, candidates will sync to spott within a few minutes for example if you choose the trigger “export candidates when contact information is found”, the candidate will automatically sync to spott a few minutes after being added to outreach candidate data synced to spott the following candidate data will sync to spott from pin full name email phone number linkedin profile url location (city, state) current and previous roles education a pin generated resume pdf profile photo important only contact information syncs to spott, not message content pin does not push linkedin messages, sequence emails, or candidate replies to any connected ats manually syncing a candidate to spott if the candidate hasn’t synced yet go to all candidates and select the checkmark next to the candidate click “export to ats” choose the spott job you want to sync the candidate to, then click “export” to complete the sync after exporting, refresh the page, and you should now see the spott logo appear on their profile important once a candidate is synced to spott, their contact information cannot be re synced if some information didn’t sync, you’ll need to manually update that candidate’s profile in spott the "export to ats" button only works for candidates who haven’t already synced to spott if an integration was connected after the selected trigger, pin won’t retroactively sync those candidates in that case, use the "export to ats" button to sync them over checking if a candidate synced to spott to confirm if a candidate has synced to spott, you can open their profile in pin if you see the spott logo, this means that they’ve been successfully synced clicking the logo will take you directly to their profile in spott disconnecting spott from pin to remove the integration, go back to settings → ats integration → spott (v2) and click disconnect this stops the sync but doesn't delete anything already pushed to spott troubleshooting "connect to ats" isn't working / key rejected — double check the key was copied in full with no trailing spaces, and confirm it hasn't been revoked from the spott side (settings → api) a position isn't syncing — check its sync to ats trigger and confirm an ats position is mapped; positions without a mapped ats position won't sync need a new key — generate a replacement in spott (settings → api → create api key) and paste it into pin the same way; the old key can then be revoked related spott's api documentation https //docs spott io/ — authentication, rate limits, and the full endpoint reference