SpringRoll Connect
Give apps the data they need.
Connect business data and platform APIs once. Choose the fields or endpoints your apps can use. Keep access approved, scoped and revocable.
Use approved data or familiar native APIs. Source credentials stay out of your apps.
Try a governed read
Example dataAn app has approval to read order, region and total. Customer details stay outside its access.
| Order | Region | Total |
|---|---|---|
| ORD-1041 | Asia Pacific | 320 |
| ORD-1042 | Europe | 180 |
| ORD-1043 | Asia Pacific | 240 |
3 sample rows · no live connection
From a source to approved app access.
Connect your source
Choose a database or platform and test its connection. SpringRoll keeps the credentials encrypted.
Choose access
Publish selected business fields, or choose the native API endpoints an app needs.
Approve each app
Review access for each app environment. Set limits and expiry, then revoke access when needed.
Useful data.
Clear boundaries.
Query approved business fields directly, or keep the platform APIs you already know. Each has its own explicit access grants.
Read the integration guide →- Only approved fields
- Seeing a data product does not grant access to its rows. Each app requests the fields it needs.
- Limits at every read
- Row restrictions, masking, expiry and query limits apply when data is returned.
- Access you can revoke
- Stop an app’s data access without changing its source credentials or redeploying it.
- Familiar platform APIs
- Keep native methods, paths and payloads. Approve endpoint access separately; native responses follow the platform account’s permissions.
Start with the data you already have.
- PostgreSQL
- MySQL
- MariaDB
- Oracle
- SQL Server
- Notion
- Salesforce
- SAP S/4HANA
- ServiceNow
- Microsoft 365
- REST API
- API Gateway
Databases support approved reads. Platform and REST APIs keep their native request format, behind owner-approved endpoint access. Dataset capabilities vary by source.
Connect your data