A real v1 API. Build on the record.
Every job, measurement, proposal, and invoice is reachable through a documented v1 REST API with scoped tokens. Read it, write it, wire your own systems into it. This is the same record the app runs on — not a bolt-on export.
Integrations built on exports don't survive contact with the job.
Mint a token. Scope it. Call the record.
Every call authenticates with a scoped bearer token — no OAuth dance, no session cookie. Grant exactly the access an integration needs, then revoke it any time.
The record's own resources, over REST.
The job record.
Read, create, and update the job — the same record your team runs the business on.
Panes and square footage.
Every pane and square footage on a job, structured and ready to consume.
Quotes, status, tokenized share.
Read quote status and the tokenized share link the customer sees.
Bill from the job, read payment state.
Create an invoice from the job and read back the payment state as it changes.
Mint and revoke scoped access.
Issue a token scoped to exactly what an integration needs, and revoke it the moment it should not have access anymore.
Pair with signed events.
Poll the API or subscribe to signed webhook events — the same v1 resources, pushed the moment they change.
One version. Real access. Real controls.
The developer API, answered.
How do I authenticate?
Every call carries a scoped bearer token in the Authorization header — no OAuth dance, no session cookie. Mint a token, scope it to what the integration needs, and call the API over HTTPS.
What can a token access?
Exactly what you grant it — read or read/write on Projects, Measurements, Proposals, and Invoices. Least privilege by default, and you can revoke a token at any time.
Is this the same data the app uses?
Yes. The API reads and writes the same records your team works on in SightLine every day — it is not a delayed export or a second-class copy.
Will v1 change under me?
v1 stays v1. The API is versioned; any breaking change ships behind a new version, so an integration you build today keeps working.
Can I get pushed events instead of polling?
Yes — pair the API with signed webhook events on the same v1 resources, so your systems hear about a change the moment it happens instead of polling for it.
Everything you need to build on the job.
Mint a scoped token and call v1 today — the same record your team runs the business on, reachable from your own systems.
Book a demo