How to connect
Pick the right setup based on who owns the devices, what you need to pull in, and what you need to send out
Find the row that matches your data. To check whether Texture supports a specific manufacturer, meter system, or partner, see Data sources.
| Your data | How it connects | Who sets it up |
|---|---|---|
| Grid and utility data: AMI, SCADA, and GIS | Texture ingests files from your existing systems, typically over SFTP or from Amazon S3. See Bring in grid data. To send a one-off or large file, use File Exchange. | Texture's Solutions team |
| Consumer-owned devices: a homeowner's Tesla battery, Enphase system, Ecobee thermostat, and so on | Send the customer a Texture Connect link from the dashboard, or embed Texture Connect in your application. The customer completes an OAuth flow that links their device account to your Texture workspace, and Texture begins polling device data automatically. A scoped key is returned that gives your application access to that customer's data. | You, in the dashboard, API, or SDK |
| Operator-managed fleet: you hold the OEM credentials and are responsible for the fleet | Upload a CSV of your sites, customers, and device identifiers with Bulk Import, then enter your OEM platform credentials in Integration Hub so Texture can begin polling telemetry. Both steps are done through the Texture Dashboard. No code required. | You. Some OEMs need the Solutions team for IP allowlisting or program IDs. |
| Program partners: DERMS, VPP, and market platforms | Partners appear in Integration Hub, but configuration is Solutions-led. See Program integrations. | Texture's Solutions team |
To send Texture data to your own systems, such as webhooks, Kafka, email, or SMS, see Destinations.
Moving from another platform#
- Fleet or installer accounts: Add your manufacturer credentials in Integration Hub, and Texture syncs the devices on those accounts.
- Customer reconnection: Send your customers Texture Connect links so they reconnect their devices to you through Texture.
- Existing connections: If you have existing customer authorizations with device manufacturers, contact us to discuss moving them.
If the dashboard looks empty#
- Check your workspace. Production and sandbox hold separate data. Use the Workspace switcher at the bottom-left of the dashboard.
- Your grid data may still be loading. It appears once the Solutions team has loaded it. AMI readings are typically one to two days behind.
- A customer's Connect link may not have finished. In Connect → Session History, a session shows Success once the customer finishes. Error, Expired, Unsupported, or Duplicate means their devices didn't connect, and the session's description says why. Links expire, so send a new one if needed.
- Your fleet's first sync may still be running. In Integration Hub, check that the integration shows Connected. Texture starts pulling devices as soon as you save credentials, then checks again every 15 minutes.
See Data freshness and history for how current each kind of data is, and Troubleshoot missing data for empty charts and missing map pins.
Next step#
Once devices are connected, start at Your program at a glance. Once grid data is in, start at Your grid at a glance.