API Overview

Unified API for Energy Devices#

Texture's API provides a standardized interface to interact with any supported energy device, regardless of manufacturer. Our API enables you to:

Read device telemetry, status, and configuration data
Write commands to control devices (charge, discharge, set modes, etc.)
Manage device connections, sites, and customers
Configure automations, schedules, and rules
Access supplemental data like weather forecasts and carbon intensity

API Resources#

Resource	Description
Devices	Get device information, telemetry, and device history
Device Commands	Send operations to specific devices
Sites	Manage physical locations with associated devices and weather data
Customers	Create and manage customer records
Connections	Create device connection flows for end users
Programs	Access energy program definitions
Enrollments	Manage program enrollments
Metrics	Access aggregated metrics (consumption, production, storage, etc.)
Commands	Specialized device commands for batteries, thermostats, etc.)

Deprecations#

Deprecated endpoints keep working until their sunset date. Responses from them include a Deprecation header with the date the endpoint was deprecated (RFC 9745, e.g. Deprecation: @1790640000), a Sunset header with the removal date, and a Link header pointing to this section.

There are no deprecated endpoints at the moment.

Removed#

Removed	Removed on	Replacement
`GET /v1/leads` and `POST /v1/leads`	September 29, 2026	None. Leads are retired.
`identificationType: "leadId"` on `POST /v1/programInstances/{instanceId}/enrollments`	September 29, 2026	Use `customerId` for an existing customer or `customerInfo` for a new one. See Enrollments.

Note

These surfaces were announced with an October 29, 2026 sunset and were removed ahead of that date. Requests to /v1/leads now return 404, and enrollment requests with identificationType: "leadId" are rejected with a 400 validation error. Enrollment responses still include a leadId field on enrollments that were created from a lead.

Using the API#

Our API follows REST principles with JSON payloads and standard HTTP methods. Authentication is performed using API keys which you can generate in the Dashboard, within the Developer section.

# Example: Get a list of your devices
curl -X GET "https://api.texturehq.com/v1/devices" \
  -H "Texture-Api-Key: your_api_key"
 
# Example: Get device metrics for consumption
curl -X GET "https://api.texturehq.com/v1/metrics/consumption?period=day&timeframe=1d" \
  -H "Texture-Api-Key: your_api_key"
 
# Example: Create a connection for device onboarding
curl -X POST "https://api.texturehq.com/v1/connections" \
  -H "Texture-Api-Key: your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "referenceId": "your-reference-id",
    "redirectUrl": "https://your-app.example.com/callback",
    "clientName": "Your Application"
  }'

Documentation#

We provide comprehensive documentation for our entire API:

Interactive API Explorer - Browse and test API endpoints
OpenAPI Specification - Full API specification
Example Applications - Sample code and implementation examples

You can use the OpenAPI specification to generate client libraries in your preferred programming language or use our provided SDKs for common platforms.