Avionté (ATS): Usage Guide and Limitations

Contents:

1. Stages & IDs
2. Application Types & Data Sources
3. Stage Movement Rules
4. Limitations
5. Sync

Stages and IDs:

Avionte has 3 main stages in which an application can be in:

• General Stages are:
  • Web Application Stage
  • Pipeline Stage
  • Nomination Stage
• Substages of those general stages are customizable in Avionte:
  • Examples: Pre-Screening, 1st Interview, Declined etc.

Web Applications: No application ID → we create a Composite ID (candidateId:jobId)

• no stage ID → we create a fixed stage internally (→ Web Application)

Pipeline Applications: No application ID → Composite ID

• We get different pipeline application structures from different endpoints where some don’t have data on the stage an application is in
• So we just store every application in the pipeline with the stage: “Pipeline”
• There are different, more specific, pipeline stages (e.g. Pre-Screening) which you can sync and move an application to (but when syncing the application back it will just be in stage: “Pipeline”)

Nominated Applications: Real ID → internally we use a composite ID for consistency

• Custom stages which are also reflected as such in the system

   

Application Types & Data Sources

Web Application:

• Endpoint: Get Web Applications for a candidate
• We fetch web applications for a candidate and add a stage to them (Web Application) because they don’t have a proper stage property

Pipeline Stage

• Endpoints: Get Candidate by Pipeline ID + Webhook event
• We can only fetch pipeline applications if we have received a webhook event before (e.g. talent moved with pipeline or talent was moved into the pipeline)
• The ID received from webhook (“PipelineID”) is the only way to fetch applications from the pipeline stage

→ In your first sync you will most likely not have any applications in the pipeline stage because you don’t have any pipeline IDs yet which we can use to fetch them

Nominated Stage:

• Endpoints: Get Application IDs in nominated stage + Get Application By Id
• Here we have extensive data about stages and substages (Interview) which we store

• You can move an application to any nominated stage and that will also be reflected in the system

   

Stage Movement Rules:

• There are no stages within web applications
• API does not allow the movement of applications within the pipeline stage (possible in UI)
  • That means you can move a candidate into the pipeline stage and out of it but not within
• Cannot move applications back to a previous stage
• Can move within stages in the nominated stage
• Applications cannot move down from a higher stage
  • Web Application (Lowest) → Pipeline (middle) → Nominated (Highest)

⚠️ Limitations

• Cannot move/reject applications within Pipeline (API limitation).
• Applications synced from Pipeline always appear as Pipeline (no sub-stage).
  • They will not have a specific stage like “Pre-Screening” but can be moved there
• Rejection reasons only available for Nominated applications.
• This integration does not support a tracked only sync (sync which only gets the candidates/applications that we created through you)

Syncs:

1. The sync frequency can not be adjusted, it is set to every 24h
   1. There will be one initial data hydration sync which syncs all of the resources -> after that we rely on webhook events to keep the data fresh
   2. The stages and rejection reasons will be synced every 24h because we do not receive webhook events for them
   3. The normal sync that will run will only show the stages and rejection reasons, just important that to remember that is expected
2. You can still triggers syncs manually from the dashboard or via API but there is a warning before

Reason: Comapies which use Avionté internally (your customers) have to pay for the API by usage, the lowest tier is 15k calls per month. This would easily be blown by a single sync for medium-large size instances in which case Avionté would automatically bump up your customer to the next tier. That can go as high as $5000/month which leads to unexpected costs for your customers. Thats why we have limited the syncs to only sync resources we cannot get from webhooks (rejection reasons & stages) regularly (every 24h). If you have questions about this please reach out to our support.