Your scheduling integration
You might have developed a scheduling integration that allows you to schedule interviews in an external tool. You’ll want to make some updates to your integration if it does any of the following:
- Allows users to reschedule or delete externally managed interviews from the past
- Initiates scheduling from a cache of candidates
Aside from that, there are just a few things to note about how the eventual migration of candidate data to the Opportunities data model may affect your integration temporarily.
Next steps and potential impact of not updating integrations
Allows users to reschedule or delete externally managed interviews from the past
Your candidates will be migrated to a new data model to support Opportunities. On Lever's new data model, a candidate's “opportunities” will have independent opportunityIds that will be linked together as part of the same "contact".
It is possible for externally managed interviews in the past to be re-associated with an opportunity with a new opportunityId. However, if you attempt to:
- Retrieve a valid interview or panel, we will return a 301 status code with the new location of the interview or panel in the Location header.
- Update or delete a valid interview or panel, we will return a 307 status code with the location of the new interview in the Location header.
This means that your integration should be able to handle a 30X redirect in order to retrieve, update, or delete an interview at its new location.
Impact: If your integration cannot redirect the request to the new location, then you will not be able to reschedule or delete interviews where the interview was moved to a different opportunity and the interview time has already elapsed. Rescheduling or deleting for upcoming interviews should continue to work as expected post-migration and on a go-forward basis.
Initiates scheduling from a cache candidates
If it’s at all possible for your integration to initiate scheduling from a cache of candidates instead of needing to initiate scheduling from within Lever, then you’ll want to ensure that there is a consistent mechanism for re-pulling candidateIds (in the future, opportunityIds), as the candidate migration to the Opportunities data model will have changed some and created new opportunities as well.
Impact: Without a way to manually or automatically re-fetch, your cache of candidateIds to schedule externally may be outdated after the migration.