AM/TA/Inv - Get File Correlation IDs History

Details

/external/v1/file/correlation-id/historyarrow-up-right

Synopsis

Get File Correlation Ids History

get

This route is used to retrieve the history data entries of file correlation ids given a set of filters such as blockchain details or file identifiers. The history entries will reflect the state of the file correlation ids on a particular block on the ledger. This endpoint returns paginated data. Up to 20 can be extracted per call. This endpoint can be called by applications with access to scope "manageReferenceData".

chevron-right
lockRequired scopes
This endpoint requires the following scopes:
  • : manageReferenceData
Authorizations
OAuth2clientCredentialsRequired
Token URL:
Query parameters
pageSizenumberOptional

The number of rows being retrieved. Must be a positive integer.

offsetnumberOptional

The offset (i.e. row start index). Must be a positive integer (or 0).

blockNumbernumber · max: 2147483647Optional

The block number where the action was recorded on the ledger.

Example: 350
transactionIdstring · max: 500Optional

The transaction id where the action was recorded on the ledger.

Example: 456789OIJHGFCVGHJKLKJHGF67JHPattern: ^[a-zA-Z0-9-]*$
channelNamestring · max: 20Optional

The name of the channel where the action was recorded on the ledger.

Example: OG123Pattern: ^[a-zA-Z0-9-]*$
fileIdsFilterstringOptional

The comma delimited list of file ids to filter the file history records. Up to 25 records can be provided. Each record should not exceed 12 characters.

Example: USCCWSF01I00,USCCWSF01I01
fileCorrelationIdsFilterstringOptional

The comma delimited list of file correlation ids to filter the file history records. Up to 25 records can be provided. Each record should not exceed 100 characters.

Example: 1234,5678,7890
fileCorrelationOrgIdstring · max: 12Optional

The organization identifier linked to the correlation ids provided in the "fileCorrelationIdsFilter" property. If not provided the organization id will be inferred from the access token.

Responses
chevron-right
200

Successfully retrieved the File Correlation Ids history entries

application/json
timestampstring · date-timeRequired

The timestamp in which the action took place.

Example: 2024-09-12T00:00:00.000Z
blockNumbernumberRequired

The block number where this action was recorded on the ledger.

Example: 350
transactionIdstringRequired

The transaction id where this action was recorded on the ledger.

Example: 456789OIJHGFCVGHJKLKJHGF67JH
channelNamestringRequired

The name of the channel where this action was recorded on the ledger.

Example: OG123
hashstringRequired

The hash of the referenced correlation information. Argon2id is used for hashing with dynamic salt

Example: $argon2id$v=19$m=4096,t=3,p=1$8AVpNOnlBvN/reiv7Rdkpw$lzXOuG0H4SibMa0elrEZ5sq3YAvdu+Y5L+ta0oSSMTg
get
/external/v1/file/correlation-id/history

Last updated

Was this helpful?