Skip to content

Using DEXR

DEXR has two main interfaces — the web application at dexr.contextualize.us.com for administrators and DEXR Outpost for devices.

Roles and Access

DEXR uses RBAC and API-key keys for authentication, independent of Carta. Each role is granted a key by an admin or super-admin.

Role What they can do
Super Admin Create and manage admins
Admin Create and manage readers and writers
Writer Push payloads into DEXR
Reader Pull payloads from DEXR

The DEXR Web Interface

At dexr.contextualize.us.com, you log in with your API key. What you can do depends on your that key. Multiple roles require multiple keys.

  • Admins create and manage reader and writer credentials for their deployment
  • Readers and writers can view existing payloads addressed to or from their account
  • Readers and writers can record a transfer — performing a real upload or download while the interface captures it — and receive a generated Python script that reproduces that action automatically

The DEXR API

DEXR is API driven and can be accessed programmatically through this interface. See the Swagger (or equivalently, Redoc) documentation for details. The API can also be pulled into and API tool, such as Postman from https://dexr.contextualize.us.com/openapi.json.

DEXR Outpost

DEXR's primary use is as a fixed end-to-end data exchange: where one system, the writer consistently sends data to a second system, the reader. DEXR Outpost simplifies the configuration of these two systems.

While the DEXR Outpost desktop application simplifies setup, automation systems typical operate outside the desktop application. Therefore, to support automation and scripted actions, DEXR Outpost also includes a command-line tool.

See DEXR Outpost → for an overview, or go directly to Installation → to get started.