Documentation

Connect Pinpoint

Pinpoint is the one connection where the secret travels the other way: Pinpoint generates the webhook signing secret, and you bring it back to Voyse. That makes the order matter, so it's worth reading this page through before you start rather than following it a step at a time.

Before you start

You need Company Manager permission in Pinpoint to create an API key.

Have your subdomain to hand — it's the first part of your Pinpoint address, so acme in acme.pinpointhq.com.

Create the key in Pinpoint

  1. In Pinpoint, go to Settings → API & Webhooks.
  2. Turn on Pinpoint API if it isn't on already.
  3. Select + Create New and name the key, such as Voyse.
  4. Set the permissions. Pinpoint lists these by function, with read, write and delete separately:
    • Jobs and Departments — read. Your open roles.
    • Applications — write. Candidates apply through Voyse.
    • Comments — read and write. The summary of what a candidate asked, and the weekly note on each role.
    • Job seekers — read. Personalised links for named people.
    • Custom fields — read, and custom attributes — write. The candidate intent score.
  5. Select Create API Key, reveal it with the eye icon, and copy it.

Voyse never needs delete on anything.

Connect it in Voyse

  1. Select Integrations in the sidebar.
  2. Under Connect an ATS, choose Pinpoint.
  3. Fill in Subdomain and API Key.
  4. Webhook Signing Secret is also required, and Pinpoint only issues one once a webhook exists. If you don't have it yet, type any value to get connected — you'll replace it in the next section.
  5. Select Connect. The pill by the provider's name reads Connected, and Sync status fills in once the first import finishes.

Add the webhook, then bring its secret back

  1. On the Voyse Integrations page, copy the Webhook URL from the Webhooks section.
  2. In Pinpoint, go to your Company Profile and open the Webhooks tab.
  3. Create a webhook pointing at that URL, and choose the events. Voyse acts on job created, job updated, job closed and job deleted; application created, application stage changed and application hired; and job seeker deleted, which withdraws that person's personalised links.
  4. Save it. Pinpoint shows a signing secret — copy it now.
  5. Back in Voyse, in the Webhooks section, select Update beside Secret key and paste it.

Until the two match, Voyse turns away Pinpoint's messages, and Last webhook stays Never. Your roles still import once a day and whenever you select Sync now.

What comes across

Jobs whose status in Pinpoint is open, with their department, location and application questions.

Capabilities lists what your key allows, and Check capabilities re-tests it after you change the key's permissions:

Feature What it needs
Job Sync, Application Submit, Webhook Events Essential
CRM Prospects Job seekers read
Candidate Notes Comments read and write
Job Notes Comments, including on jobs
Candidate intent score Custom fields read and custom attributes write
Hiring manager contacts Jobs read, including hiring managers

Once the intent score row is granted, a Candidate intent score field selector appears under Capabilities. Create the field in Pinpoint first: an application custom field of type Short text, which holds the value Voyse writes — high, medium or low — reflecting how much someone read and asked before applying.

If it didn't work

  • Invalid Pinpoint credentials — usually the subdomain. It's the name alone, not the whole address.
  • Last webhook stays Never — the signing secret in Voyse isn't Pinpoint's. Copy it again from the webhook in Pinpoint and use Update.
  • The intent score never appears on an application — the key lacks custom attributes write, or the field in Pinpoint isn't application-scoped.

The rest of the page — sync status, the activity log, disconnecting — is covered in Connect your ATS.