source
and table
from the previous API version with namespace
and endpoint
, where:namespaces
designated for it, such as Rumpel-only writing to the rumpel
namespace. Applications are not authorised to write into each other's namespaces.endpoints
are defined by the application developer as required. Data is grouped under a combination of a namespace
and an endpoint
where the two together identify a set of data accessible via a URL path /api/v2.6/data/namespace/endpoint
./api/v2.6/data/rumpel/locations
for all locations saved into a PDA by the Rumpel app./hat/locations
), with multiple records inserted in one go. The data provided in the example is merely an illustration – the PDA will accept any well-formed JSON data. Note the request is authenticated with an ACCESS_TOKEN
obtained previously and the token has been issued for the namespace of hat
specifically.endpoint
– field that includes the specific endpoint the record was assigned torecordId
– UUID of the data recorddata
– the data JSON structure exactly as submittedBad Request
response code with the details of the error in the body of the response. If, for example, such data (as decided by its hash) already exists in the PDA, none of the data in the request will be saved and you will receive a message indicating so:namespace
, but a different endpoint
:GET
request to the /api/v2.6/data/namespace/endpoint
.take
to implement data pagingPUT
request to the /api/v2.6/data
endpoint with the complete Data Record structure in the request body:accuracy
field of the record already stored, however in practice the provided data replaces the whole record already stored in the PDA.DELETE
request to the /api/v2.6/data
endpoint with IDs of the records to be deleted in query parameters:records
parameter for each record ID. The response will contain an error if you are not authorised to delete any of the provided records or if any of the records do not exist – no records will be deleted in this case.