Post a Oauth 2.0 pushed authorization request
POST/request
Post a Oauth 2.0 pushed authorization request
Request
Header Parameters
Possible values: Value must match regular expression ^(Mon|Tue|Wed|Thu|Fri|Sat|Sun), \d{2} (Jan|Feb|Mar|Apr|May|Jun|Jul|Aug|Sep|Oct|Nov|Dec) \d{4} \d{2}:\d{2}:\d{2} (GMT|UTC)$
The time when the PSU last logged in with the TPP. All dates in the HTTP headers are represented as RFC 7231 Full Dates. An example is below: Sun, 10 Sep 2017 19:43:31 UTC
The PSU's IP address if the PSU is currently logged in with the TPP.
An RFC4122 UID used as a correlation id.
Indicates the user-agent that the PSU is using.
- application/json
Body
required
Reference introspection request
Possible values: non-empty
Oauth 2.0 token to be introspected
Responses
- 201
- 404
- 406
- 429
- 500
- 502
- 504
metadata for token
Response Headers
x-fapi-interaction-id
string
- application/json
- Schema
- Example (from schema)
Schema
if the token has expired
Possible values: <= 255 characters
id of client who owns the token
expiration time in ms
when the token was issued
the issuer
unique string
scope
type of token
subject of token (not always present, depending on the token)
{
"active": true,
"client_id": "string",
"exp": "string",
"iat": "string",
"iss": "string",
"jti": "string",
"scope": "string",
"token_type": "string",
"sub": "string"
}
Not found
Response Headers
x-fapi-interaction-id
string
- application/json
- Schema
- Example (from schema)
Schema
Validation Error messages
{
"errors": [
"string"
]
}
Not Acceptable
Response Headers
x-fapi-interaction-id
string
Too many requests, maximum capacity reached. Requests are now throttled.
Response Headers
x-fapi-interaction-id
string
Internal Server Error
Response Headers
x-fapi-interaction-id
string
Bad Gateway
Response Headers
x-fapi-interaction-id
string
Upstream timeout, insufficient capacity to serve request. More capacity being brought online. Please try again.
Response Headers
x-fapi-interaction-id
string