Guides and workflows
Submit an inquiry
Send a question or a scope of work for a person to read.
Use an inquiry when you have a question or a scope of work, but not a part you can describe as operations. A person at Glyph reads every inquiry and replies by email.
Create it
POST
/api/intake/inquiries| name | Required. Contact name, 200 characters. |
|---|---|
| Required. A valid address. We reply here. | |
| title | Required. 300 characters. |
| description | Required. The scope, 10 000 characters. |
| company, phone | Optional. 200 and 50 characters. |
| budget_range, timeline | Optional. Free text, 100 characters each. A timeline is not a promised date. |
| external_reference | Optional. Your id, 200 characters, returned on every read. |
curl -X POST https://glyphtech.io/api/intake/inquiries \
-H "Authorization: Bearer $KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: rfq-0901" \
-d '{
"name": "Pat Example",
"email": "pat@example.com",
"company": "Example Robotics",
"title": "Weldment for a test fixture",
"description": "Steel frame, 1.2 m by 0.8 m, drawing to follow. Need by end of November.",
"external_reference": "rfq-0901"
}'
Response, 201:
{
"id": "0c2f6c7e-3f31-4f9e-9a3b-0b3a2a7a6a10",
"status": "submitted",
"created_at": "2026-10-12T14:03:22.418+00:00",
"external_reference": "rfq-0901"
}
Follow it
GET
/api/intake/inquiries/{id}curl https://glyphtech.io/api/intake/inquiries/0c2f6c7e-3f31-4f9e-9a3b-0b3a2a7a6a10 \
-H "Authorization: Bearer $KEY"
{
"id": "0c2f6c7e-3f31-4f9e-9a3b-0b3a2a7a6a10",
"status": "accepted",
"title": "Weldment for a test fixture",
"created_at": "2026-10-12T14:03:22.418+00:00",
"updated_at": "2026-10-13T09:15:00.000+00:00",
"external_reference": "rfq-0901",
"job": { "id": "2c5c95fc-0ec3-4a30-9d75-17d6e012c645", "status": "estimated" }
}
job is null until we create a job from the inquiry. Inquiry statuses are submitted, under_review, accepted, declined, queued, in_production, delivered, complete, and archived.
A key can read only the inquiries it created. Another key's inquiry returns 404.
When to use a job instead
If you can name the operations and the hours, create a job. You get a price at once and can accept it without waiting for a reply.