NIXZ Interim can synchronize interim requests from DAS, VMS, and other vacancy sources with your ATS. NIXZ retrieves new requests from the configured sources and then places them in your ATS according to the agreed setup.
When a source requires access, NIXZ can use your organization’s login details or subscription. This is especially relevant for DAS or VMS portals where assignments are only visible to approved suppliers.
Suitable ATS systems
NIXZ can connect with ATS systems that provide an API or another suitable integration option. In practice, many modern ATS systems can be connected.
Setup usually requires access to the ATS API, documentation, and test environment. Together, we align which data should be created, updated, or retrieved.
Placing requests in your ATS
Interim requests can be placed in your ATS as a vacancy, assignment, lead, project, or another suitable object. This depends on your ATS setup and how your organization works with interim requests.
During setup, we agree which fields are filled, which status a new request receives, and how users can later find or follow up on the requests.
Publication through your ATS
Whether requests can also be published on your website depends on your ATS setup. NIXZ places the request in your ATS with the agreed status or workflow.
From your ATS, you can then connect your own processes to it, such as editing, internal review, publication on your website, or distribution through multiposters.
Available data fields
The available fields differ per source. Often this includes information such as job title, client, location, start date, duration, rate, hours per week, deadline, assignment description, requirements, preferences, and procedure information.
For commonly used sources and ATS systems, NIXZ has standard field mappings. Where needed, we adapt these to the setup of your ATS.
Data quality
NIXZ tries to make retrieved requests as useful as possible before they are synchronized. This includes normalizing dates, cleaning up text, and structuring parts such as requirements, preferences, and assignment information.
The quality and completeness still depend on the original source. For some sources, we can share a sample dataset in advance so you can see what data to expect.
Labels, categories, and criteria
In some ATS systems, NIXZ can include additional information such as labels, categories, match criteria, or recognizable properties of the request. Whether this is possible depends on the capabilities of the ATS and the desired setup.
If you want to exclude specific functions, categorize requests, or use automatic labels, we align this separately during setup.
Candidate-facing vacancy texts with AI
Besides fixed field mappings, NIXZ can also use custom AI prompts to make retrieved requests more suitable for candidate-facing use. This is especially useful because the original text of an interim request is often written for suppliers or bidders, not for candidates.
Such a request usually also contains information that is less relevant to a candidate, such as knockout criteria, evaluation information, rates, submission conditions, or procedure details. With an AI prompt, NIXZ can turn this into a clear candidate-facing vacancy text.
The original request can still be used as the source, but the text is rewritten into a form that better fits publication, matching, or communication with candidates.
Own subscription or access
NIXZ can retrieve requests from sources that are available by default or collected through NIXZ subscriptions. If you want to retrieve requests that are only visible within your own DAS or VMS account, the source can be configured with your organization’s access.
If you eventually want to submit a candidate to an assignment, you usually still need your own subscription or admission for the relevant portal or client.