Documentation

Connect Oracle Recruiting Cloud

Oracle is the one connection you can't complete on your own: your Oracle administrator creates an account for Voyse to use, and you enter its details. Once it's in, requisitions import on a schedule and applications go back the same way.

Before you start

Ask your Oracle administrator for:

  • The address of your Oracle instance — the hostname you use to reach Oracle, in the shape https://yourcompany.fa.region.oraclecloud.com, with no path and no trailing slash.
  • An integration user account and its password, allowed to read job requisitions and to create applications. A dedicated account rather than a person's login: this one won't be affected when somebody leaves, and its activity in Oracle is recognisable as Voyse's.

You may also be given a Direct Apply partner key. It applies only after Oracle has taken your organisation through Direct Apply onboarding, so leave the field empty unless you were handed one.

Connect it

  1. Select Integrations in the sidebar.
  2. Under Connect an ATS, choose Oracle Recruiting Cloud.
  3. Fill in Base URL, Integration username and Password, and the Direct Apply partner key if you have one.
  4. Select Connect. The pill by the provider's name reads Connected, and Sync status fills in once the first import finishes.

Voyse checks the details by asking Oracle for a single requisition, so a wrong hostname or password is refused there and then rather than failing quietly later.

How updates reach Voyse

Oracle doesn't send Voyse anything, so there is no Webhooks section on the page for this connection and nothing to configure. Requisitions are re-read on a schedule, once a day, and Sync now fetches everything again when you don't want to wait — after posting a requisition, say.

What comes across

Requisitions whose status is Open and whose external status is Posted. One that is open but not posted externally stays in Oracle, which is what you want: it's the posted ones candidates can be told about.

Each role carries its department name and primary location. There is no separate list of departments from Oracle, so Voyse's department list is built from the roles that came across.

Capabilities lists two rows, both Essential:

  • Job Sync — requisitions, into Voyse.
  • Application Submit — someone applies in Voyse, with their answers and CV, and the application appears in Oracle.

The optional features other systems offer — writing notes back, prospect links, the candidate intent score — aren't available through Oracle, so no row for them appears.

If it didn't work

  • Invalid Oracle Recruiting Cloud credentials — most often the base URL. It must be the hostname alone, with no path after it.
  • Connected, but no roles — check with your administrator that requisitions are posted externally, and that the integration user is allowed to read them.
  • Applications refused — the integration user can read requisitions but isn't allowed to create applications. That's a change your Oracle administrator makes.

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