Requisition JSON Integration

generic json payload requisitions integration the role of this integration is to expose a jobylon endpoint where the integrating partner can send requisitions as json data as well as receiving requisition status updates back to the integrating partner using optionally provided callback url authentication jobylon supports both oauth 2 0 client credentials flow (defined in oauth 2 0 rfc 6749, section 4 4 https //tools ietf org/html/rfc6749#section 4 4 ) and basic authentication depending on the selected authentication method, jobylon will either provide client id and client secret for oauth or username and password for basic authentication headers api specification once enabled, jobylon will provide integration partner with a unique endpoint following such format https //api jobylon com/requisitions/g/\<id>/\<uuid>/json provider/ where \<id> and \<uuid> are supplied by jobylon during the configuration process if the integration partner has provided jobylon with a callback url jobylon will call that url on requisition status changes if chosen, the callback request may include basic authentication headers, so integration partners could authenticate the request requisition creation integration partner is expected to perform post requests with a json list of objects to jobylon endpoint for requisition creation any values of received data can later be configured to be displayed or used in jobylon, however there are certain expected parameters parameter name description required jbl reference company identifier where requisition belongs to it is especially useful when an organization has multiple accounts and would like to choose what account in jobylon the posted requisition belongs to yes jbl external id identifier of a requisition coming from external system yes jbl status requisition status acceptable values are available, draft, scheduled, published, closed, archived yes requisition status updates for requisition status updates, the integration partner should perform patch request with json objects to https //api jobylon com/requisitions/g/\<id>/\<uuid>/json provider/\<external id>/ where external id url parameter must match jbl external id provided during requisition creation