# Redirect From Sign with Singpass

After completing the digital signing process on the Sign portal, the user will be redirected back to the RP’s application. The redirection uses the pre-registered URL set during [**onboarding**](https://docs.sign.singpass.gov.sg/for-relying-parties/how-our-api-works) and includes key query parameters, allowing the RP to track and finalise the transaction.

## Additional Query Parameters

* **request\_id:**  Match the sign request id returned during the initiate sign request API.
* **status:** Either `success` or `cancelled`, RP must check the actual signing status from [webhook](https://docs.sign.singpass.gov.sg/for-relying-parties/api-documentation/sign-v3/accept-success-signing-webhook) or [get signing result API](https://docs.sign.singpass.gov.sg/for-relying-parties/api-documentation/sign-v3/get-signing-result)
  * `success`: user is being redirected back to RP after successfully completing the signing
  * `cancelled`: user is being redirected back to RP after being identified as a [non-intended signer](https://docs.sign.singpass.gov.sg/for-relying-parties/api-documentation/sign-v3/sign-portal#non-intended-signers)

{% hint style="warning" %}
The query parameters will be changed soon.
{% endhint %}

**Example**

```sh
# Given pre-registed recirect_uri is https://rp.com/sign-redirect
https://rp.com/sign-redirect?request_id=signv3-01961988-8b77-7a86-9641-5f2507965c04&status=success
```

<details>

<summary>Can I provide more than 1 redirect URL for my application?</summary>

We only accept one redirect URL per application onboarded. When we send the user back to your application, we will include the `request_id` in the query parameters, which you can then use to redirect the user back to whichever page on your application you deem necessary.&#x20;

</details>