Getting Started with the Enerflo API

Who These Docs Are For

The Enerflo API is designed for experienced developers and technical integration teams who already have working knowledge of REST APIs, GraphQL, HTTP, and authentication patterns.

If you're building an integration with Enerflo, your team should be comfortable with:

• Making authenticated API requests and handling responses
• Working with webhooks and event-driven architectures
• Debugging API calls using tools like Postman, cURL, or a GraphQL client
• Reading and implementing technical documentation independently

A note on support: Enerflo's support team are platform experts who are happy to help with general Enerflo questions and can log bug reports if something appears broken in the API. For deeper integration guidance — such as identifying the right endpoints, selecting webhooks, or working through implementation steps — that falls outside what our standard support team is equipped to help with. If you need that level of hands-on assistance, ask your Enerflo contact about our available paid support options. For documentation gaps or bugs, use the API Docs Feedback Form.

---

The Short Version

Enerflo has two APIs. Which one you need depends on where in the solar deal lifecycle the data you're working with lives:

• Creating or receiving a lead? → Use the V1 REST API
• Pre-signing deal activity? → Use the V2 GraphQL API
• Post-signing install & customer data? → Use the V1 REST API
• Building a full CRM integration? → You'll likely use all three touchpoints

---

The Deal Lifecycle

The flow is: V1 lead → V2 deal (via project submit) → V1 post-signing install.

Leads are created in V1. When a project is submitted, a V2 Deal object is created and owns everything through signing. After signing, the V1 Install Tracker takes over.

Note: The V1 Install Tracker is created at a specific moment in the V2 deal flow. See When Does the V1 Install Tracker Get Created? for details on that handoff.

---

V1 vs. V2 at a glance

Important: V1 and V2 use different API keys. Make sure you're generating and authenticating with the right key for the API you're calling.

---

Where to go next

🔑 Set up authentication

• V1 REST API authentication
• V2 GraphQL API authentication

📖 Explore the APIs

• V1 REST endpoint reference
• V2 GraphQL queries & mutations

🔔 Set up webhooks & events

• Webhooks overview
• V1 Events · V2 Events

🔗 Build a CRM integration

• How to Integrate Enerflo with My CRM

This guide covers common business use cases and best practices for data exchange. CRM-specific connectors, field mapping, and surrounding business logic are outside its scope — those decisions are left to your team.

---

Questions?

Most questions are answered in the sections linked above. If you get stuck, reach out to your Enerflo contact or submit a request through the API Docs Feedback Form.