Embedding API

welcome to the jobylon embedding api ! this api allows you to integrate your pages into the jobylon ats platform, creating a smooth and unified experience for users we currently support embedding in the following areas main dashboard add your page to the main dashboard company settings add your page to the settings of a company application detail provide detailed insights or actions related to specific applications application search for a job add your page to a job provisioning if you wish to be notified when a new company registers the integration in jobylon ats, we provide an optional possibility to provision the integration by sending a webhook from joblylon ats to your system with the following sample data { "company id" 123, "initial data" { "company name" "example company" } } to enable that, jobylon ats requires a callback url to your system authentication partners should implement a url for jobylon to retrieve a token for a user per company tokens should be user specific if a lifetime is not provided, we will default to manually setting the token's lifespan to one hour you need to provide us with token url, an app id and an app key , which jobylon ats will use to generate user specific tokens upon token requests, jobylon ats posts the following payload to the partner { "company id" 123, "email" "user\@example com", "full name" "user userson", "role" "member" } role can be one of the following owner, admin, manager, member localisation jobylon will pass the user's language as a query parameter in the iframe url the language codes follow the iso 639 1 standard (e g , en for english, sv for swedish) it is up to you to decide whether to act on this parameter or ignore it security all endpoints must originate from the same domain specific endpoints below is an overview of how each specific url is structured and behaves here is an example for reference https //domain com/embed/dashboard/?token=xxx\&company=xxx navigation bar and company settings these are the simplest endpoints to implement in these cases, we will pass the company id as a parameter this allows you to tailor the content or functionality based on the specific company example https //domain com/embed/dashboard/?token=xxx\&company=xxx application search for a job for the application search endpoint, we will pass the job id this enables you to provide job specific functionality or data additionally, we will listen for events related to authentication or authorisation issues example https //domain com/embed/dashboard/?token=xxx\&job=xxx application detail in the application detail endpoint, we will pass the applicant id similar to the application search, we will monitor events for any authentication or authorisation issues, and handle errors example https //domain com/embed/dashboard/?token=xxx\&application=xxx events to accomodate for error handling, jobylon ats will listen for message events from your integration in the example of application detail iframe, if an application exists in jobylon ats but not in your system, you can notify us using the following format { "partner" "name of the partner", "api" "embedding", "payload" { "error" "not found" } }