Fetches audit history based on query parameters
GET/audit
Fetches audit history and parses based on query parameters
Request
Query Parameters
Possible values: [created
, updated
, deleted
]
The type of action to search for.
Possible values: non-empty
and <= 40 characters
, Value must match regular expression ^[^<>]*$
The organisation ID
Possible values: [apiResource
, apiDiscoveryEndpoint
, authorisationServer
, authorisationServerCertification
, certificationManager
, contact
, organisation
, organisationCertificate
, organisationAdmin
, organisationAuthorityClaim
, organisationAuthorityClaimAuthorisations
, organisationAuthorityDomainClaim
, organisationAuthorityDomainClaimUser
, organisationTermsAndConditions
, softwareStatement
, softwareStatementAuthorityRoleClaim
, softwareStatementCertificate
, softwareStatementCertification
, referenceAuthorisationDomain
, referenceAuthorisationDomainRole
, referenceAuthorisationDomainRoleMetadata
, referenceAuthority
, referenceAuthorityAuthorisationDomain
, referenceTermsAndConditions
, superUser
]
The type of resource to search for.
The ID of the specific resource we want to parse by.
The user email you want to parse by. This will be performed for createdBy and updatedBy based on the revision type
Optional start of date range to constrain the set of results returned. This will restrict the clients returned to those whose metadata was most recently modified after the specified startDate. The date must be supplied in RFC3339 format. If not supplied, the startDate used will be the epoch.
Optional end of date range to constrain the set of results returned. This will restrict the clients returned to those whose metadata was most recently modified before the specified sendDate. The date must be supplied in RFC3339 format. If not supplied, the endDate used will be the current date and time.
The page number to return of the result set
The size of the pages to return
The field name to sort
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.
Responses
- 200
- 400
- 401
- 403
- 404
- 429
- 500
- 501
- 502
- 504
Audit history in paginated form
Response Headers
x-fapi-interaction-id
string
- application/json
- Schema
- Example (from schema)
Schema
Array [
- OrganisationAuthorityClaimDetailsAudit
- SoftwareStatementAudit
]
Array [
]
items
object[]
anyOf
Possible values: [apiResource
, apiDiscoveryEndpoint
, authorisationServer
, authorisationServerCertification
, certificationManager
, contact
, organisation
, organisationCertificate
, organisationAdmin
, organisationAuthorityClaim
, organisationAuthorityClaimAuthorisations
, organisationAuthorityDomainClaim
, organisationAuthorityDomainClaimUser
, organisationTermsAndConditions
, softwareStatement
, softwareStatementAuthorityRoleClaim
, softwareStatementCertificate
, softwareStatementCertification
, referenceAuthorisationDomain
, referenceAuthorisationDomainRole
, referenceAuthorisationDomainRoleMetadata
, referenceAuthority
, referenceAuthorityAuthorisationDomain
, referenceTermsAndConditions
, superUser
]
Possible values: [created
, updated
, deleted
]
The user who performed the action
When the action was performed
The unique ID of the action
Possible values: non-empty
and <= 40 characters
, Value must match regular expression ^[^<>]*$
Unique ID associated with the organisation
Possible values: non-empty
and <= 40 characters
, Value must match regular expression ^[^<>]*$
Unique ID associated with the authority claims
Possible values: non-empty
and <= 40 characters
, Value must match regular expression ^[^<>]*$
Unique ID associated with the Authorisation reference schema
Possible values: [Active
, Inactive
]
Default value: Active
Current status of this resource
Possible values: <= 30 characters
, Value must match regular expression ^[^<>]*$
Authorisation Domain for the authority
Possible values: non-empty
and <= 60 characters
, Value must match regular expression ^[^<>]*$
The authorisation domain role name
Possible values: <= 40 characters
, Value must match regular expression ^[^<>]*$
Registration ID for the organisation
Possible values: <= 255 characters
, Value must match regular expression ^[^<>]*$
Legacy and will eventually be removed - please use UniqueTechnicalIdentifiers instead
Possible values: <= 16
Possible values: [apiResource
, apiDiscoveryEndpoint
, authorisationServer
, authorisationServerCertification
, certificationManager
, contact
, organisation
, organisationCertificate
, organisationAdmin
, organisationAuthorityClaim
, organisationAuthorityClaimAuthorisations
, organisationAuthorityDomainClaim
, organisationAuthorityDomainClaimUser
, organisationTermsAndConditions
, softwareStatement
, softwareStatementAuthorityRoleClaim
, softwareStatementCertificate
, softwareStatementCertification
, referenceAuthorisationDomain
, referenceAuthorisationDomainRole
, referenceAuthorisationDomainRoleMetadata
, referenceAuthority
, referenceAuthorityAuthorisationDomain
, referenceTermsAndConditions
, superUser
]
Possible values: [created
, updated
, deleted
]
The user who performed the action
When the action was performed
The unique ID of the action
Possible values: [Active
, Suspended
, Inactive
]
Default value: Active
Is this software statement Active/Suspended/Inactive
Possible values: <= 255 characters
, Value must match regular expression ^[^<>]*$
Software Statement client Id
Possible values: <= 255 characters
, Value must match regular expression ^[^<>]*$
Software Statement client name
Possible values: <= 255 characters
, Value must match regular expression ^[^<>]*$
Software Statement description
Possible values: <= 40 characters
, Value must match regular expression ^[^<>]*$
The additional check for software statement, this field can avoid
Possible values: non-empty
and <= 40 characters
, Value must match regular expression ^[^<>]*$
Unique ID associated with the organisation
Possible values: <= 40 characters
, Value must match regular expression ^[^<>]*$
Unique Software Statement Id
Possible values: <= 8 characters
, [Live
, Test
]
Default value: Live
Software Statement mode
Client created flag
Possible values: <= 255 characters
, Value must match regular expression ^[^<>]*$
A reference to fourth party organisation resource on the RTS Directory if the registering Org is acting on behalf of another
Possible values: <= 255 characters
, Value must match regular expression ^(http://|https://).*
A compliant URI string that points to a human-readable privacy policy document
Possible values: <= 255 characters
, Value must match regular expression ^(http://|https://).*
The Software Statement client compliant URI
Possible values: Value must match regular expression ^(http://|https://).*.(svg|png|jpg|jpeg)$|(data:image/[a-zA-Z0-9;+=-]+,[A-Za-z0-9+/]*={0,2})$
A compliant URI
Possible values: <= 255 characters
, Value must match regular expression ^(http://|https://).*
Possible values: <= 255 characters
, Value must match regular expression ^(http://|https://).*
Possible values: <= 255 characters
, Value must match regular expression ^(https:\/\/[^\s/?#]+(?:\/[^\s\/?#]+)*)$
Possible values: <= 255 characters
, Value must match regular expression ^(http://|https://).*
The Software Statement terms of service compliant URI
Possible values: <= 255 characters
, Value must match regular expression ^(http://|https://).*
A compliant URI
Possible values: [Pending
, Confirmed
, Deactivated
]
Default value: Pending
Possible values: <= 40 characters
Software Statement version as provided by the organisation's software team
Flag shows if assertion has been generated on the software statement - will be set to true when assertion is generated
Flag shows if software statement is in failed update state
Possible values: Value must match regular expression ^[^<>]*$
Error message describing why the update failed
Possible values: <= 255 characters
, Value must match regular expression ^[^<>]*$
Extra metadata defined by the org admins to be loaded into the software statement and made avaiable during introspection
Is this software statement enabled for federation
Possible values: [openid_entity_federation_managed
, openid_entity_self_managed
]
The type of federation management that applies to this software statement
Default value: true
Require a signed request object. If this is set to false, the client will not be FAPI compliant
Possible values: [PS256
, RS256
]
Default value: PS256
Signing algorithm that a client expects the server to return an id_token with. Must be PS256
Possible values: non-empty
and <= 60 characters
, [private_key_jwt
, tls_client_auth
, client_secret_basic
]
Default value: private_key_jwt
Token endpoint authentication method
Possible values: <= 255 characters
, Value must match regular expression ^https:\/\/(?:[a-zA-Z0-9-]+\.)+[a-zA-Z]+(?::\d+)?(?:\/[a-zA-Z0-9-._~!$&'()*+,;=:@\/?%]*)?(?:\?[a-zA-Z0-9-._~!$&'()*+,;=:@\/?%]*)?(?:#[a-zA-Z0-9-._~!$&'()*+,;=:@\/?%]*)?$|(^android:apk-key-hash:[a-zA-Z0-9-]+)|(^ios:bundle-id:[a-zA-Z][-a-zA-Z0-9]*\.([a-zA-Z][-a-zA-Z0-9]*\.?)+)$
Default value: true
Are the tokens issued for this client bound to a client tls certificate
ID of the Authorisation Server that is connected to this Software Statement
Possible values: <= 255 characters
, Value must match regular expression ^(http://|https://).*
The URI for the website with details about the application and its services
pageable
object
Page number
sort
object
orderBy
object[]
Name of the property used for sorting
Possible values: [ASC
, DESC
]
Direction of sort, i.e. ascending or descending
Was the case ignored
Whether ascending
Size of the page
Offset
Is the page sorted
Is this an unpaged response
{
"items": [
{},
{}
],
"totalPages": 0,
"totalSize": 0,
"pageable": {
"number": 0,
"sort": {
"sorted": true,
"orderBy": [
{
"property": "createdAt",
"direction": "ASC",
"ignoreCase": true,
"ascending": true
}
]
},
"size": 0,
"offset": 0,
"sorted": true,
"unpaged": true
},
"numberOfElements": 0,
"size": 0,
"offset": 0,
"empty": true,
"pageNumber": 0
}
Bad Request
Response Headers
x-fapi-interaction-id
string
- application/json
- Schema
- Example (from schema)
Schema
Validation Error messages
{
"errors": [
"string"
]
}
Unauthorized
Response Headers
x-fapi-interaction-id
string
Forbidden
Response Headers
x-fapi-interaction-id
string
Not found
Response Headers
x-fapi-interaction-id
string
- application/json
- Schema
- Example (from schema)
Schema
Validation Error messages
{
"errors": [
"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
Request is not yet implemented
Response Headers
x-fapi-interaction-id
string
- application/json
- Schema
- Example (from schema)
Schema
Validation Error messages
{
"errors": [
"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