Reading REDA Data via Salesforce APIs

Admin 5 min read Updated July 2026

If you need to pull REDA data into a reporting tool, a data warehouse, or middleware, the good news is that there's nothing REDA-specific to learn. Everything you see in REDA is a Salesforce record, and REDA runs entirely on the Salesforce platform — so any tool that already speaks Salesforce's standard interfaces can read and write REDA's data with no proprietary layer in between. This article orients you: it explains why that's true, points to the official Salesforce documentation for the how, and marks the one boundary worth knowing — the difference between pulling data out and the separate way REDA takes web forms in.

Getting there. This isn't a screen inside REDA. Programmatic access is set up in your Salesforce org's own settings — the standard connected-app and authentication configuration — which lives outside the REDA apps.
Access you'll need. Standard Salesforce API access must be enabled for your org, and the account your tool connects as needs permission to the REDA records it will touch. That permission works exactly like it does for a person: an integration reading invoices needs the same access a human would to view those invoices.

What this means in practice

REDA installs as a set of managed packages on the Salesforce platform. Its records are standard Salesforce records, which means they're queryable, reportable, and exportable through the platform's own programmatic interfaces — the same REST, bulk-data, and other APIs Salesforce provides for any org. Connecting is standard Salesforce authentication; there is no separate REDA sign-in for integrations.

The practical upshot: if your BI tool, warehouse loader, or integration platform already has a Salesforce connector, it can reach REDA's data today. You point it at your org, authenticate the standard way, and query the records REDA manages — properties, leases, invoices, and the rest — as you would any Salesforce data.

What REDA ships, and what it doesn't

It's worth being precise about which parts are REDA and which are simply the platform:

Need	Use
Take web-form submissions into REDA, no code	The REDA Data Service — REDA's one packaged inbound intake surface
Read or write REDA records from your tools	The standard Salesforce APIs — nothing REDA-specific

Beyond the Data Service, REDA adds no proprietary read API and needs none. It also ships no packaged outbound connections: REDA doesn't call out to your systems on its own. The direction is one way by design — you pull from REDA, using the platform's APIs, rather than REDA pushing to you.

Official Salesforce documentation. Because REDA rides entirely on standard Salesforce interfaces, the authoritative reference for authentication, query syntax, and the API endpoints is Salesforce's own — not this Help Center. Start with the Salesforce REST API Developer Guide and the connected apps and OAuth documentation.

Practical pointers

A few things to keep in mind as you plan an integration:

Respect record permissions. Your integration account sees exactly what its permissions allow, the same as a logged-in person — so give it the access it needs and no more. If it should read invoices, grant it invoice access.

Test in a sandbox first. Prove your queries and any writes against a non-production org before pointing them at live data.

Expect internal field names to differ from labels. The programmatic name of a field isn't always the label you see on screen. Your org's own field reference in Salesforce setup is the source of truth for those names; this Help Center stays at the label level by design.

Consider a report before an integration. If your goal is a dashboard or a periodic extract, REDA's built-in reporting may get you there without any API work at all. See Building Reports.

Worked example: a nightly cash dashboard

Meridian Properties' analyst wants a cash dashboard that refreshes overnight. They connect their reporting tool to the org through a standard connected app, authenticating the usual Salesforce way, as an integration user granted read-only access to invoices. Each night the tool queries REDA's invoices and balances and refreshes the dashboard — no REDA-specific endpoint, no key, just standard Salesforce access scoped to what the analyst is allowed to see.

Where to go next

REDA Data Service: Connect Your Forms — the inbound counterpart, for taking web forms into REDA.
Messaging with REDA Connect — another product that lives beside REDA in the same org.
Building Reports — the in-platform way to get data out without an integration.
Understanding Access in REDA — the permission model your integration account inherits.

Frequently asked questions

Only the Data Service uses a key, and only for taking web forms in. General read/write access to REDA data uses standard Salesforce authentication, not a REDA key.

The platform allows writes wherever an account's permissions do — but REDA's automation expects records to be created through its own screens and actions, which set up the related records and steps that a raw write would skip. Before scripting bulk writes into REDA, talk to your REDA partner so the automation still fires correctly.

In your org's own field reference in Salesforce setup. This Help Center describes fields by their on-screen labels rather than their internal names — the official Salesforce documentation and your org's setup are where the programmatic names live.

Was this article helpful?