InferOwl includes settings for API keys and webhook subscriptions. These are connection controls. The external system, data flow, supported operations, and implementation responsibilities still need confirmation for your agency.
API-key settings
Owners and managers can view API Keys. Owners can create or revoke keys; managers can review the listed usage and scopes. The creation form asks for a name and selected scopes. A newly created key is shown once, so its owner must store it through the agency's approved secure process.
Before requesting a key, have the technical owner specify the records and operations the connection needs. Confirm that those operations are supported for the agreed integration. Never send a key in an initial support email or include it in a screenshot.
Webhook settings
Webhooks describe where selected event notifications should be sent. Owners and managers can view subscriptions and delivery information. Owners control creation, changes, and deletion. The setup form takes a destination URL and selected events; the signing secret is shown once when the subscription is created.
The receiving system needs a technical owner who can handle and verify incoming messages. Confirm actual event delivery and recovery behavior during technical scoping. Subscription settings and a successful test do not establish that every recruiting event is delivered to the other system.
File imports
Candidate imports provide a separate way to bring a reviewed batch into InferOwl. Use Import candidates in bulk for supported input and review steps. A file import is a batch operation; it does not establish an ongoing synchronization with the source system.
Agree who owns each part
The agency owner approves access and data sharing. A manager describes the workflow and the acceptance checks. The technical owners of InferOwl setup and the external system confirm the connection method, field mapping, permitted writes, monitoring, and recovery process. Agree their responsibilities in the implementation scope.
For each shared field, name the authoritative record, the allowed direction of change, and what should happen when the values conflict. Include a way to identify duplicate records and report unsuccessful or partial updates.
Confirm availability before rollout
Bring the external system name, edition, technical contact, intended records, expected volume, and required direction of data flow to a workflow review. Ask which parts are available in your workspace and which require configuration or additional work. No named ATS connector, automatic two-way synchronization, delivery guarantee, or setup price is established by this reference.
If a connection fails, describe the intended operation, time and timezone, and redacted error. Check the receiving record before repeating a write. Ask the owner to review configuration changes that could affect other workflows.