Inbox Entries
All the data sent by someone to an Inbox is called an Entry. In Threads and Stores, a user must be assigned to the Module to send data. In Inboxes, however, anyone who has Inbox ID can send a reply (assuming they have the Bridge URL and Solution ID).
Inboxes allow users to receive encrypted entries, either from external or internal sources.
-
Internal sources are people who have access to an Inbox, or are simply registered in a given Context. Those users are known to your application, and their entries can be linked to their accounts.
-
External sources are people from the outside; they do not have an account linked with your app. For example, someone who fills out an online contact form without the need to create an account.
About Entries
The structure of an entry and a brief description of its elements is outlined in the following table:
| Field | Type | Encrypted | Description |
|---|---|---|---|
data | binary | Content of the entry | |
files | File[] | List of attached files | |
authorPubKey | string | Public key of the author |
Define Data Structure
Inbox's architecture does not require you to use a specific data structure inside the entries. Before working with Inboxes, define the structure of your entries.
We recommend future-proofing your entries by choosing an easily modifiable format. It is a good idea to include both a type and a version field in the structure.
Example: Form with Text Answer
The type field allows future support for different types of entries like: "select_answer", or "multi_select".
And in case of changing the schema, you can always distinguish between them using "version" field.
Remember that this is only an example and you should consider your app's requirements and limitations.
Before working with Inboxes, follow our Getting Started Guide. It will show you how to set up your project to work with PrivMX Bridge.
Sample code on this page is based on the initial assumptions.
Entry's publicMeta and privateMeta fields support any kind of data formats encoded to byte arrays. Examples in this section use Swift serialization to JSON format.
Assumptions
In further examples, the following structures are used:
Sending Entries
Having established public connection and inboxApi, you can send data to the Inbox:
Listing Entries
Created entries can be listed by non-public connections created using PrivMXEndpoint.
Listing the most recent Entries in given Inbox
Reading Files from Entries
Files from Entries can be read by non-public connections created using PrivMXEndpoint class
We use cookies on our website. We use them to ensure proper functioning of the site and, if you agree, for purposes such as analytics, marketing, and targeting ads.
PrivMX Endpoint Swift v2.6