Description

Due to SmartR service sunset (the extended opt-out period ended on Jun 19, 2024), it's no longer possible for
Application API clients to request and receive SmartR Join Url and Candidate Portal (SmartR) Url when creating an application.

The following changes have been made in the Application API - Post an Application endpoint:

  • createJoinLink property removed from request payload
  • smartrJoinUrl property removed from the response body
  • candidatePortalUrl property removed from response body

Impact

Requests with the createJoinLink property will be accepted, however its value will be ignored by the API.

There is no replacement for the smartrJoinUrl or candidatePortalUrl properties.
The link to the new solution (Applicant Tracking Portal) will be sent to the candidate via email.

References

Description

We have fixed an issue in the Webhooks API where the activation of a subscription could fail due to an error in fetching the token needed for handshake authentication. Previously, this would result in a general 500 error. Now, the API will return a 424 HTTP status code if the token required for handshake authentication cannot be fetched during subscription activation.

The 424 HTTP status code was already used for handshake failures. With this change, authentication needed for the handshake is also treated as part of the handshake failure. From now on, instead of a general 500 error, a 424 error will be returned with the following response body:

{
  "errors": [
    {
      "code": "HANDSHAKE_FAILED",
      "message": "[Fallback] Problem with getting token for subscription: 41a50be7-3edd-42a1-a302-bc7fca51d7c5"
    }
  ]
}

Impact

This change is backward compatible, it does not introduce any new error codes, 424 was already returned in case of handshake failure.

References

Description

We are excited to announce that our public API changelog is now available. This changelog will provide detailed information on all updates, fixes, and changes to our public APIs, ensuring that you are always informed about the latest developments.

Impact

There are no API changes associated with this entry. This is an informational update to inform you about the availability of the public API changelog.

References