---
title: Parameters stage
description: This stage captures parameters in the original request. To advance, the stage assesses the input body. Any values that have been passed in and are listed in the configuration are put into state. The stage ignores any values that are not listed in the configuration. The self-service mechanism passes the parameters back to the client at the end of the process.
component: pingidm
version: 7.5
page_id: pingidm:self-service-reference:stages/stage-parameters
canonical_url: https://docs.pingidentity.com/pingidm/7.5/self-service-reference/stages/stage-parameters.html
keywords: ["JSON", "Configuration", "Authentication", "Self-Service", "User Self-Service"]
---

# Parameters stage

This stage captures parameters in the original request. To advance, the stage assesses the input body. Any values that have been passed in and are listed in the configuration are put into `state`. The stage ignores any values that are not listed in the configuration. The self-service mechanism passes the parameters back to the client at the end of the process.

By default, this stage is required *only* if you are integrating IDM with AM. The stage is added automatically if you use the UI to configure a self-service process, but can generally be ignored unless a custom client or UI requires it.

* Example configuration

  ```json
  {
      "name" : "parameters",
      "parameterNames" : [
          "returnParams"
      ]
  }
  ```

* Dependencies

  In all of the default IDM self-service processes, this must be the first stage in the process. In a custom process, the stage has no order dependencies, and can occur anywhere in a process. All this stage does is to copy named parameters into `successAdditions` for the process to output at `tag:end`.

* Required Parameters

  * `parameterNames` - a list of parameters the stage supports. These parameters are returned in the requirements.