---
title: "Pushed Authorization Request endpoint. Retrieve a request_uri that can be used with the oidc/auth endpoint. More info here: https://docs.moneyhubenterprise.com/docs/how-to-use-pushed-authorization-request-par-endpoint"
method: POST
path: "/oidc/request"
tags: ["auth"]
---

# Pushed Authorization Request endpoint. Retrieve a request_uri that can be used with the oidc/auth endpoint. More info here: https://docs.moneyhubenterprise.com/docs/how-to-use-pushed-authorization-request-par-endpoint

`POST /oidc/request`

## Request

- Base URL: `https://identity.moneyhub.co.uk`
- URL: `https://identity.moneyhub.co.uk/oidc/request`
- Auth: HTTP basic

## Request body `application/x-www-form-urlencoded`

- object
  - `client_id` string, required: The client’s unique identifier.
  - `scope` string, required: The scopes being requested. Must include openid scope and the id:* scope.
  - `redirect_uri` string, required: The redirect uri that the auth endpoint will redirect to on success. Will error if this does not match the redirect URI registered on the client.
  - `response_type` 'code' | 'id_token' | 'token' | 'code id_token' | 'code token' | 'id_token token' | 'code id_token token', required: Specifies the desired response. Will error if the response type doesn't match any configured for the client.
  - `claims` string: Claims (as JSON string) give extra information on the authorisation flow and how connection should be made.
  - `state` string: Opaque value used to maintain state between the request and the callback. Can prevent attacks such as CRSF.
  - `nonce` string: This is a security value that can prevent replay attacks.
  - `client_assertion` string: A signed JWT. The sub and iss properties in the payload should be the clientId. The aud property should be the token endpoint. For use when doing a private key JWT auth.
  - `client_assertion_type` string: For use when doing a private key JWT auth.
  - `request` string: A signed JWT containing all the authorization request parameters. If included, other individual parameters become optional as they are encapsulated in the JWT. Please check the description here https://docs.moneyhubenterprise.com/docs/using-request-parameter

## Response `201`

A successful response with request_uri

- object
  - `request_uri` string: Access Token
  - `expires_in` integer, required: Request URI expiry

## Other responses

- `400`: Unsuccessful Response - Bad Request - Invalid request/Invalid client/Unauthorized client
- `401`: Unsuccessful Response - Unauthorized - Client Authentication Failed

---

[API](https://skmtc.dev/moneyhubenterprise/apis/moneyhub-identity-service.md) - [All operations](https://skmtc.dev/moneyhubenterprise/apis/moneyhub-identity-service/llms.txt) - [OpenAPI document](https://skmtc.dev/moneyhubenterprise/apis/moneyhub-identity-service/revisions/e004d9ee1fdb?raw)