Request data via token

Overview

Request data retrieval using a previously exchanged token. This initiates the data retrieval process from storage devices back through Privicore to the requesting application.

Request Data via Token

Endpoint: POST /data-token/request-data

Authentication: Required (Authorization token obtained from the step)

Content-Type: application/x-www-form-urlencoded

Request Parameters

Parameter	Type	Required	Description
`token`	string	Yes	The data token identifier to retrieve data for
`ssid`	string	No	Session ID that will be returned with the data for request tracking

Use Case

When you need to retrieve data previously exchanged for a token, use this endpoint to initiate the retrieval process. Privicore contacts the storage devices holding the encrypted data, retrieves it, and prepares it for download. The optional ssid parameter allows you to track specific requests, useful when managing multiple concurrent data retrievals.

After requesting data, use the download endpoint to actually retrieve the decrypted data. The data flows backward through the encryption chain: Device decrypts → Privicore decrypts → Application receives encrypted data → Application decrypts locally.

The token must be a permanent token (data already exchanged)
Profile must have authorization to access the token's data
Use ssid for tracking requests in multi-request scenarios
Data retrieval follows the reverse decryption chain

Request Code Samples

Shell

JavaScript

Java

Swift

PHP

Python

HTTP

Objective-C

Ruby

OCaml

Dart

Responses

🟢200Success

application/json

Command accepted.
Use DPT CAB websocket server to subscribe to your profile channel via authorization token and receive command status messages in real time.
Data can be retrieved either by listening to a socket or RabbitMQ profile queue.

Headers

Body

Example

[
    "string"
]

🟠401401

🟠422422

Request data via token

Overview#