tablefrom the previous API version with
namespacesdesignated for it, such as Rumpel-only writing to the
rumpelnamespace. Applications are not authorised to write into each other's namespaces.
endpointsare defined by the application developer as required. Data is grouped under a combination of a
endpointwhere the two together identify a set of data accessible via a URL path
/api/v2.6/data/rumpel/locationsfor 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_TOKENobtained previously and the token has been issued for the namespace of
endpoint– field that includes the specific endpoint the record was assigned to
recordId– UUID of the data record
data– the data JSON structure exactly as submitted
Bad Requestresponse 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
GETrequest to the
taketo implement data paging
PUTrequest to the
/api/v2.6/dataendpoint with the complete Data Record structure in the request body:
accuracyfield of the record already stored, however in practice the provided data replaces the whole record already stored in the PDA.
DELETErequest to the
/api/v2.6/dataendpoint with IDs of the records to be deleted in query parameters:
recordsparameter 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.