TnC history of the user
GET/users/:UserEmailOrID/history
Get historical data on TnCs signed by user
Request
Path Parameters
Possible values: <= 50 characters
, Value must match regular expression ^[^<>]*$
UUID or email address of the user. Note use of the email address is considered deprecated
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
- 401
- 403
- 404
- 429
- 500
- 502
- 504
User TnCs history
Response Headers
x-fapi-interaction-id
string
- application/json
- Schema
- Example (from schema)
Schema
Array [
]
Array [
]
content
object[]
TermsAndConditionsItem
object
ExternalSigningService
object
Possible values: [DocuSign
]
The Name of the External Signing Service
ExternalSigningServiceSignerTemplateConfig
object
Possible values: non-empty
, Value must match regular expression ^[^<>]*$
Template ID for 1 signer
Version of the TnC document
Possible values: non-empty
, Value must match regular expression ^[^<>]*$
Template ID for 2 signers
Version of the TnC document
Possible values: non-empty
, Value must match regular expression ^[^<>]*$
Template ID for 3 signers
Version of the TnC document
Possible values: non-empty
, Value must match regular expression ^[^<>]*$
Template ID for 4 signers
Version of the TnC document
Possible values: non-empty
, Value must match regular expression ^[^<>]*$
Template ID for 5 signers
Version of the TnC document
Possible values: non-empty
, Value must match regular expression ^[^<>]*$
Template ID for 6 signers
Version of the TnC document
Possible values: non-empty
, Value must match regular expression ^[^<>]*$
The Subject of the External Signing Service
Possible values: non-empty
and <= 100 characters
, Value must match regular expression ^[^<>]*$
The Subject of the Email for External Signing Service
Version of the TnC
Unique identifier for the Terms and Conditions Item
Possible values: non-empty
, Value must match regular expression ^[^<>]*$
The Name of the TnC
Possible values: [Participant
, Directory
]
Role for which this TnC applies
Possible values: non-empty
, Value must match regular expression ^[^<>]*$
The MarkDown of the TnC
Possible values: [Active
, Inactive
]
Default value: Active
Current status of this resource
Possible values: <= 255 characters
Terms and Conditions initiated date
Possible values: Value must match regular expression ^[^<>]*$
The envelope id of the ess signing request
Possible values: [completed
, created
, declined
, deleted
, delivered
, processing
, sent
, signed
, template
, voided
, expired
, reissued
]
Access code for the specifier to fill in the signer details. This will be populated only once, when signing is initiated
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
{
"content": [
{
"TermsAndConditionsItem": {
"TnCId": 0,
"Name": "string",
"Type": "Participant",
"Content": "string",
"Status": "Active"
},
"InititatedDate": "string",
"ExternalSigningServiceEnvelopeId": "string",
"ExternalSigningServiceEnvelopePasscode": "string"
}
],
"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
}
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
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