Overview
Inboxes are a way for users to send encrypted data to your app.
The advantage of Inboxes is that they don't require the user to be registered in order to send encrypted data. This opens up various possibilities in environments where you need to gather sensitive information from unregistered users (e.g. on your website).
To learn more about Inboxes, their structure, how they are encrypted, and what are their use cases - read Inbox Docs.
Before working with Inboxes, follow our Getting Started Guide. It will show you how to set up your project to work with PrivMX Bridge.
The sample code on this page is based on the same assumptions
Working with Inboxes
When working with Inboxes, you will use the following:
inboxApi
- for methods used to manage Inboxes in given Context
Creating an Inbox
Creating a basic unnamed Inbox, which can be used if your app needs only one Inbox and you don't need a distinction between them:
Fetching Inboxes
Fetching the most recent Inboxes in given Context:
Remember that data is transmitted in binary format, so you'll need to parse it back into your desired format.
You can use the deserializeObject
function provided by the SDK for this purpose.
Modifying Inboxes
To update an Inbox you must always provide its current version, as well as:
- list of users,
- list of managers,
- new private and public meta (even if it didn't change).
We use cookies on our website. We use them to ensure the proper functioning of the site and, if you agree, for purposes we set, such as analytics or marketing.