---
title: Rejection handlers
description: A rejection handler defines the action to take when a request to an application or resource is rejected by policy evaluation. This lets you decide if you want to display an error template or redirect the user to another URL for error details, instructions, or additional actions.
component: pingaccess
version: 9.0
page_id: pingaccess:pingaccess_user_interface_reference_guide:pa_rejection_handlers
canonical_url: https://docs.pingidentity.com/pingaccess/9.0/pingaccess_user_interface_reference_guide/pa_rejection_handlers.html
revdate: February 6, 2023
---

# Rejection handlers

A rejection handler defines the action to take when a request to an application or resource is rejected by policy evaluation. This lets you decide if you want to display an error template or redirect the user to another URL for error details, instructions, or additional actions.

You can specify the response status code to send if policy evaluation fails.

You include a rejection handler in a rule by clicking to expand **Advanced** on the **Create Rule** window.

PingAccess contains three predefined rejection handlers:

* Default API Rejection Handler

  Returns a `403` status code in a JavaScript Object Notation (JSON) *(tooltip: \<div class="paragraph">
  \<p>An open, lightweight data-interchange format that uses human-readable text to store and transmit data.\</p>
  \</div>)* template.

* Default Rate Limiting Rejection Handler

  Returns a `429` status code in a JSON template.

* Default Web Rejection Handler

  Returns a `403` status code in an HTML template.