2. Reading / Writing Data
PDA Data I/O
The PDA is a data store. This means that you can read and write any data you want, be it a passport, your health records or any data you can think of.
HAT API Android
has built-in support for reading or writing data to your PDA
.
This section describes the mechanism of writing data. For reading, this is done through data-debits, a system of consented data exchange.
Writing Data to PDA
Make network requests
Hat API Android
offers a general method to create network requests:
url
is the URL to send the request tomethod
is the HTTP method of the request, you can find the different methods herecontentType
is the content-type of the request, you can find more hereheaders
is the additional headers of the request, this field can be an empty dictionary,mapOf("","")
completion
is a callback function to execute when the request has finished. The result type of the callback can either beisSuccess(var statusCode: Int?, var error: Error?, var json: Json?, var resultString: String?, var token: String?)
if the request was successful or
HasFailed(var statusCode: Int?, var error: Error?, var json: Json?, var resultString: String?, var token: String?)
if the request has failed.
The result type is an enum
. Depending if the request was a success or a failure it will have the right type. When the request is successful, the result type will include:
A boolean value
isSuccess
, indicating if the request was successful. It may be that the request triggers the successful result type but the isSuccess is false, for example, a 404 response.The
statusCode
of the request. Usually the200..299
range is a success and400..599
is failure. You can learn more about the different status codes here.The
result
isJson
type ofFuel
, can be found here.The
token
is a refreshed token returned from thePDA
. It's optional and sometimes can be null or empty.
When the request has failed, the result type will include:
The
error
that has occurred with the request, e.g. no internet connection or time out.The
statusCode
of the request. Usually the200..299
range is a success and400..599
is failure. You can learn more about the different status codes here.The
result
isJSON
type ofFuel
, can be found here. Usually it will hold more info about the failure.
Write data
Let's say we want to save the randomStructure
below in our PDA
:
The URL
that the data will be saved is https://$hatAddress/api/v2.6/data/$path
.
If the hatAddress
is postman.hubat.net
and the path
is randomdata
then the URL
will be: https://postman.hubat.net/api/v2.6/data/dataswift-sandbox/randomdata
.
The path
is formed by your app name, dataswift-sandbox
, and the rest of the path, randomdata
. It can also be folder/something/data/random
. How deep the path will be depends on the data structure that your app uses to navigate to different files.
To write data to the PDA
, we also need the user's token in the headers of the request. The header you need to add is x-auth-token
along with the token retrieved from the KeyStore
. NEVER save the token in a non-encrypted database.
Using the function from Hat API Android
that will be
Based on the type of the completionCallback
you might have gotten the data back or you might get an error. Your app should know how to react in both scenarios:
A successful response will have statusCode
201 and look like this:
endpoint
is thepath
that the file resides,https://$hatAddress/api/v2.6/data/$path
recordId
is the record identifier in thePDA
. It's useful for when you want to delete the file for example.data
is the data structure that you have saved in thePDA
A request that has failed will look like this:
error
is the error that has occurredmessage
is a more descriptive message about theerror
that has occurred
Read data
If we want to read data we are going to use the same request again but method
will be GET
instead of POST
:
If we make the same assumptions again, the hatAddress
is postman.hubat.net
, the path
is randomdata
and the x-auth-token
in the headers includes the token, then the call will look like below:
Notice that since we want to read data and not write, we don't include any parameters.
Based on the type of the completionCallback
you might have gotten the data back or you might get an error. Your app should know how to react in both scenarios:
A successful response will have statusCode
200 and look like this:
endpoint
is thepath
that the file resides:https://$hatAddress/api/v2.6/data/$path
recordId
is the record identifier in thePDA
. It's useful for when you want to delete the file for example.data
is the data structure that you have saved in thePDA
A request that has failed will look like this:
error
is the error that has occurredmessage
a more descriptive message about theerror
that has occurred
Update data
Let's say that we want to change our original example:
To something like this:
To update the data, the HTTP method
has to change to PUT
:
If we make the same assumptions again, the hatAddress
is postman.hubat.net
and request and the x-auth-token
in the headers includes the token, then the call will look like below:
Where parameters
is an array of Key-value pair
of type Map<String: Any>
representing the new structure that we want to update. Mind the brackets, it has to be an array even if it's just one element.
Based on the type of the completionCallback
you might have gotten the data back or you might get an error. Your app should know how to react in both scenarios:
A successful response will have statusCode
201 and look like this:
endpoint
is thepath
that the file resides:https://$hatAddress/api/v2.6/data/$path
recordId
is the record identifier in thePDA
. It's useful for when you want to delete the file for example.data
is the data structure that you have saved in thePDA
A request that has failed will look like this:
error
is the error that has occurredmessage
is a more descriptive message about theerror
that has occurred
Delete data
If we now want to delete the file we have just created, we need to create a DELETE
request:
If we make the same assumptions again, the hatAddress
is postman.hubat.net
and request and the x-auth-token
in the headers includes the token, then the call will look like below:
Where body
in this case is the recordId
of the entry that we want to delete. We can also delete multiple entries with one request using more parameters. If the recordId
is 5 then the body
will be:
A successful response will have statusCode
200 and look like this:
A request that has failed will look like this:
error
is the error that has occurredmessage
is a more descriptive message about theerror
that has occurred
Last updated