AutoGlass CRM API Reference
Integrate your website and other systems with the CRM. Send in leads, and more over time — every endpoint here is documented with request fields, responses and copy-paste examples.
https://www.autoglass-crm.comOverview
The CRM exposes a small, focused HTTP API. All requests and responses are JSON, sent over HTTPS. You authenticate with an API key you generate inside the CRM. CORS is enabled, so you can call the public endpoints directly from browser JavaScript on your own website.
REST + JSON
Plain HTTPS requests with JSON bodies — no SDK required.
API-key auth
Per-website keys, generated and revoked in Settings.
Copy-paste ready
cURL, fetch and a full HTML form for every endpoint.
Authentication
Create a key in Settings → Website Leads (Admin only). You can issue one key per website, see how many leads each has received, and disable or delete a key at any time. The full key (format agk_…) is shown once — copy it immediately.
Send the key on every request in either header:
X-API-Key: agk_9f3a1b…
# — or —
Authorization: Bearer agk_9f3a1b…A key used in browser code is visible to visitors. That's acceptable for lead intake (it can only create leads and can be revoked), but for full secrecy proxy the request through your own server and add the header there.
Website Leads
LiveTurn a website contact / quote form into a CRM lead. Each submission becomes a Lead tagged 🌐 Website, attributed to the originating site.
https://www.autoglass-crm.com/api/public/leadsRequest body
JSON. phone is the only strictly required field, plus a name (name, or firstName + lastName).
| Field | Type | Required | Notes |
|---|---|---|---|
| name | string | name or first | Full name; split into first/last automatically. |
| firstName | string | name or first | Use instead of name if you have separate fields. |
| lastName | string | optional | Optional. |
| phone | string | required | Minimum 7 characters. |
| string | optional | Validated if present. | |
| vin | string | optional | Recommended — drives accurate glass lookup. |
| year | number | optional | 1900–2100. |
| make | string | optional | Optional. |
| model | string | optional | Optional. |
| serviceType | string | optional | Free text e.g. "windshield repair" — mapped to a job type. |
| jobType | string | optional | Same as serviceType; either works. |
| address | string | optional | Service location. |
| city | string | optional | — |
| state | string | optional | — |
| zip | string | optional | — |
| message | string | optional | Customer message → stored as customer notes. |
| website | string | optional | Originating page/site; overrides auto-detected source. |
| shopId | string | optional | Route the lead to a specific shop. |
| source | string | optional | Public source only (WEBSITE, GOOGLE, FACEBOOK…). Defaults WEBSITE. |
Responses
Examples
curl -X POST https://www.autoglass-crm.com/api/public/leads \
-H "Content-Type: application/json" \
-H "X-API-Key: agk_9f3a1b…" \
-d '{
"name": "Jane Doe",
"phone": "555-123-4567",
"email": "jane@example.com",
"vin": "1HGCM82633A004352",
"serviceType": "windshield repair",
"message": "Rock chip on the highway"
}'What happens to the lead
- • Created with
source = WEBSITEand a unique number (LD-YYYY-NNNNNN). - • Attributed to the originating website (stored on the lead and shown with a 🌐 Website flag).
- • Routed to a shop: payload
shopId→ default shop → the only active shop. - • Appears instantly in Leads, newest first.
Ready to connect a website?
Generate a key and paste in one of the snippets above.
More endpoints will appear here as they ship. Questions? Contact your CRM administrator.