Glint Solar Project API

The Glint API lets your own systems read and update data in Glint, for example your CRM or project management tool. Use it to stop copying project status, properties and landowner contacts between tools by hand.

What you can do

Projects. Create, read, update and delete projects, including your custom properties.
Contacts. Create, read, update and delete contacts, and link them to projects and parcels.
Parcels. See the parcels on a project, update their properties such as control status, and link contacts.
Organization data. Read your organization, portfolios and users.

Some examples:

Create a project in Glint when a lead qualifies in your CRM
Keep stage, capacity and other properties the same in both places
Send landowner contacts and parcel status to your CRM

Here is an example of how it could work with a website:

And with Google Sheets:

What stays in Glint

Designs, map objects, analysis results and data layers are not available through the API. Parcels are added in Glint from cadastral data, so they can be updated but not created through the API.

What you need

An organization admin in Glint to switch on API access
Someone to build the connection, such as a developer, your IT team or an integration partner
A plan for how often to sync. The API doesn't send updates by itself, so your system checks Glint on a schedule, for example every night

Set up

Step 1: Switch on API access

An organization admin goes to Company settings → Integrations → API Access and turns on Enable API access. When it is off, nobody in the organization can create or use access tokens.

Step 2: Create a personal access token

Go to My settings → Security → Personal Access Tokens and create a token. You will be asked for your password first. Copy the token right away, it is only shown once.

A token has the same access as the user who created it. It can only reach the portfolios and data that user can see in Glint.

Step 3: Build the integration

Your developer uses the token and the API documentation to connect your systems.

Keep tokens safe

Treat a token like a password. Don't share it or put it in code
Set an expiry date and replace tokens regularly
Delete tokens you no longer need
If a token may have leaked, delete it and create a new one

Need help?

If you are planning an integration, or expect to sync large amounts of data, reach out through the chat in Glint. We can help your developer get started and set limits that fit your use case.