Myjgid JGID API
Agent-ready OpenAPI document · curated by JenticCRMDeal Pipelinebearer18 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Manage clients, enquiries, quotes, jobs, invoices, inventory, and timesheets in a JGID workspace using a bearer token.
Use for: I need to create a new enquiry from a website lead, List all clients in our JGID workspace, Retrieve the status of job 4421, Find the invoice associated with order 992
Not supported: Does not handle payroll processing, payment capture, or marketing automation - use for trades job management across CRM, quotes, jobs, invoices, and timesheets only.
Jentic publishes the only available OpenAPI specification for JGID API, keeping it validated and agent-ready. JGID is an Australian-built job management and CRM platform used by trades, manufacturers, and field-service businesses to run the full quote-to-invoice workflow. The API exposes 18 endpoints split into a CRM module (clients, contacts, locations, suppliers), a workflow module (enquiries, quotes, orders, jobs, invoices), an inventory module (instruments, services, materials), and a time-tracking surface for timesheets. Authentication is HTTP bearer against https://myjgid.com.
Install Jentic One Beta
Connect the JGID API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the JGID API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmyjgid.com%2Fjgid" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmyjgid.com%2Fjgid" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with JGID API.
Maintain the CRM contact graph across /api/v2/crm/clients, /contacts, /locations, and /suppliers
Open new sales enquiries via POST /api/v2/workflow/enquiries to start the quote-to-invoice journey
Inspect quote, order, job, and invoice records by ID through the /api/v2/workflow/{type}/{id} endpoints
Read inventory across instruments, services, and materials for quote line-item reference data
Pull timesheet data via GET /api/v2/timetracking/timesheets for payroll and job-cost reconciliation
Use Cases
Patterns agents use JGID API for, with concrete tasks.
★ Lead-to-Enquiry Capture
Capture website or chatbot leads as JGID enquiries to kick off the quote-to-invoice workflow. The integration calls POST /api/v2/crm/clients (or finds the existing client), then POST /api/v2/workflow/enquiries with the scope of work and the client ID. This means leads land in the same workflow trades use day-to-day rather than in a separate spreadsheet.
Call POST /api/v2/crm/clients for the new lead, then POST /api/v2/workflow/enquiries with the client ID and the project description.
Quote-to-Invoice Status Tracking
Track the full quote-order-job-invoice chain for a JGID workspace by calling GET /api/v2/workflow/quotes/{id}, /orders/{id}, /jobs/{id}, and /invoices/{id} as records progress. The integration writes status changes to a Slack channel or BI tool so operations leads see live pipeline state without logging into JGID.
Fetch GET /api/v2/workflow/jobs/{id} for active jobs, then GET /api/v2/workflow/invoices/{id} for the linked invoice to confirm whether each job has been billed.
Inventory and Materials Lookup
Surface JGID's inventory across instruments, services, and materials inside a quoting tool or chatbot via GET /api/v2/inventory/instruments, /services, and /materials. The integration powers autocomplete and unit-price lookup so quote line items match what's actually catalogued in JGID.
Call GET /api/v2/inventory/materials, filter by name 'concrete', and return the matching items with their unit prices and SKU codes.
Timesheet Export for Payroll
Pull JGID timesheets into a payroll system using GET /api/v2/timetracking/timesheets. The integration runs nightly, joins entries with internal employee IDs, and writes the gross hours per worker into the payroll inbox. This avoids manual export from the JGID portal at the end of every pay cycle.
Call GET /api/v2/timetracking/timesheets for the current pay period and write the per-employee total hours to the payroll system.
AI Agent Job Management Concierge
An AI agent acts as a back-office assistant for a trades business. It searches Jentic for JGID operations, loads the client and enquiry schemas, and chains GET /api/v2/crm/clients, POST /api/v2/crm/clients, and POST /api/v2/workflow/enquiries to take a phone-call lead from a tradie's voicemail and produce a JGID enquiry. Jentic isolates the bearer token so the agent never holds the workspace secret.
Search Jentic for 'create a JGID enquiry from a new lead', execute POST /api/v2/crm/clients, then POST /api/v2/workflow/enquiries with the project scope.
Key Endpoints
18 endpoints — jentic publishes the only available openapi specification for jgid api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/api/v2/crm/clients
List clients
POST
/api/v2/crm/clients
Create a client
POST
/api/v2/workflow/enquiries
Create a sales enquiry
GET
/api/v2/workflow/quotes/{id}
View a quote
GET
/api/v2/workflow/jobs/{id}
View a job
GET
/api/v2/workflow/invoices/{id}
View an invoice
GET
/api/v2/inventory/materials
List materials
GET
/api/v2/timetracking/timesheets
List timesheets
GET
/api/v2/crm/clients
List clients
POST
/api/v2/crm/clients
Create a client
POST
/api/v2/workflow/enquiries
Create a sales enquiry
GET
/api/v2/workflow/quotes/{id}
View a quote
GET
/api/v2/workflow/jobs/{id}
View a job
GET
/api/v2/workflow/invoices/{id}
View an invoice
GET
/api/v2/inventory/materials
List materials
GET
/api/v2/timetracking/timesheets
List timesheets
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring JGID by hand means managing its bearer token, targeting myjgid.com, and passing the Authorization header across its CRM, workflow, inventory, and timesheet calls yourself. Through Jentic you install once, import JGID from the API Directory, store the token once, and your agent calls it.
Permission scoping
JGID puts the record id in the URL path (/api/v2/workflow/quotes/{id}, /api/v2/workflow/jobs/{id}), so a rule can pin your agent to one quote or job and nothing else. You choose the operations it may call, so writes like creating a client are not included unless you add them.
Credential isolation
Your JGID bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a JGID enquiry' or 'look up a job', and Jentic returns the matching JGID operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Complementary
Stripe API
Stripe handles invoice payment collection that pairs with JGID's invoice generation.
Use Stripe to take card payment on JGID-generated invoices when the business wants online checkout in addition to JGID's payment options.
FAQs
Specific to using JGID API through Jentic.
Why is there no official OpenAPI spec for JGID API?
JGID does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call JGID API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the JGID API use?
The JGID API uses HTTP bearer authentication - every request must include `Authorization: Bearer {Token}`. Through Jentic, the bearer token sits in the encrypted vault and is injected at execution time, so agent code and prompts never see the raw workspace secret.
Can I create an enquiry with the JGID API?
Yes. Call POST /api/v2/workflow/enquiries with the linked client ID and the scope of the job. The created enquiry feeds the standard JGID quote-order-job-invoice workflow, which you can then read back through the /api/v2/workflow/quotes/{id}, /orders/{id}, /jobs/{id}, and /invoices/{id} endpoints.
How do I track a job through Jentic?
Search Jentic for 'view a JGID job', load the GET /api/v2/workflow/jobs/{id} schema, and execute it with the job ID. Chain GET /api/v2/workflow/invoices/{id} for the linked invoice to determine whether the job has been billed.
Can I export timesheets for payroll?
Yes. Call GET /api/v2/timetracking/timesheets to retrieve timesheet entries. Filter by date range and employee, then write the totals into your payroll system. This is the canonical export path - the spec does not include a paginated bulk-export variant beyond the list endpoint.
What are the rate limits for the JGID API?
The published spec does not document explicit rate limits. Treat the API as throttled in production, implement exponential backoff on 429 responses, and contact JGID support for workspace-specific limits before running large bulk syncs of enquiries or jobs.
Can I limit what my agent is allowed to do with the JGID API?
Yes. Because you run Jentic One yourself, your own rules decide which JGID operations and credentials the agent may use. You choose the operations it can call, so read paths like GET /api/v2/workflow/jobs/{id} or GET /api/v2/timetracking/timesheets can be allowed while writes such as POST /api/v2/crm/clients or POST /api/v2/workflow/enquiries stay excluded unless you add them. Since JGID carries the record id in the URL path, a rule can pin the agent to a single quote or job and nothing else.
GET STARTED