JobBOSS Public API: What Integration Options Exist for JobBOSS and JobBOSS2
jobboss public api
Also searched as
- jobboss integrations
- jobboss integration
- jobboss sql access
- jobboss2 api
Short answer
Classic JobBOSS stores data in Microsoft SQL Server, so most custom integrations read it by SQL and write through supported import tools or the vendor's SDK rather than by raw inserts. JobBOSS2 is a newer product and its API and database access depend on how it is hosted and licensed, so confirm with the vendor what is available for your edition before designing around it.
Applies to: JobBOSS (SQL Server edition) and JobBOSS2. Vendor offerings change, so verify API availability and licensing with the vendor for your version.
Plan an integration
- 1Write down the data flow: for example quote data from a CAD or quoting tool into JobBOSS, or job costs out to an accounting system.
- 2Ask the vendor or your reseller which interfaces your edition supports: SDK, API, import utility, or database access, and what licensing applies.
- 3For read-only reporting, create a SQL login with read permission to the JobBOSS database and connect your tool; avoid using the application's own login.
- 4For writing data, use the supported import function or SDK so business rules, numbering and validation are applied.
- 5Build and test against a copy of the database or a test company before touching production.
- 6Schedule and log the integration, with an error report that someone reviews.
- 7Re-test after every JobBOSS upgrade or service pack, since schema or behavior can change.
Direct SQL access for classic JobBOSS
On premises JobBOSS databases are SQL Server, and reporting tools such as Crystal Reports, Power BI and Excel connect directly. Commonly queried tables include Job, Job_Operation, Material, Material_Req, Customer, Vendor, PO_Header, PO_Detail, Delivery, Invoice_Header, Quote and Employee, though exact names should be verified in your database.
Read access is low risk and very productive. Writing with SQL is not: JobBOSS maintains numbering, status and cost fields in code, and a direct update can leave a job in an inconsistent state that is hard to detect later.
-- open jobs with customer (verify table and column names in your database) SELECT j.Job, j.Customer, c.Name, j.Status, j.Order_Date FROM Job j LEFT JOIN Customer c ON c.Customer = j.Customer WHERE j.Status = 'Active'
Import tools, SDK and partner connectors
The supported way to bring data in is the application's import functions or the vendor's SDK or API where one is offered for your edition. Several third-party quoting, CAD and shop-floor products also ship connectors for JobBOSS, which is often cheaper than building one.
Before building, check the connector market: your quoting or e-commerce tool may already support JobBOSS, and the connector will handle edge cases you would otherwise discover in production.
JobBOSS2 considerations
JobBOSS2 is aimed at a more modern deployment model, and direct database access may be restricted or unavailable depending on hosting. Do not assume classic table access applies; ask what API, export or reporting access the vendor supports for your subscription.
If no API is available for a need, consider scheduled exports to a reporting database, or a vendor-supported report feed, and avoid screen scraping, which breaks with every release.
Try it here, free
JobBOSS Classic Private AI Layer Blueprint Generator
Fill in your version, database, hosting and use cases to get an architecture plan for a private, on-prem AI assistant on JobBOSS Classic, ready to share with IT and security.
Common pitfalls
- !Writing to JobBOSS tables with SQL and corrupting job status, numbering or costs.
- !Giving a reporting tool an administrator login instead of a read-only account.
- !Building against a schema that changes with the next upgrade without regression testing.
- !Assuming classic JobBOSS database access applies to JobBOSS2.
- !Running heavy reporting queries on the production server during working hours.
How an ERP-grounded AI assistant handles this
For JobBOSS shops, a private AI layer usually starts with read-only SQL: asking which jobs are late or what margin a customer produced, with the query shown. Netray's ERPray and DataRay can run on-prem against a read-only copy of the SQL Server database, so the data stays inside your network.
Frequently asked questions
Does JobBOSS have a public API?
Classic JobBOSS data is accessible through its SQL Server database and through vendor-supported import tools and SDK offerings. A general public REST API is not something to assume, so confirm with the vendor what applies to your edition.
How do I integrate JobBOSS with another system?
Define the data flow, check for an existing connector, then use read-only SQL for outbound data and supported import functions or the SDK for inbound. Test on a copy and log errors.
Can I connect Power BI or Excel to JobBOSS?
Yes for the SQL Server version, using a read-only SQL login. Query views or tables, and avoid putting heavy queries on the production database during peak hours.
Is it safe to update JobBOSS data with SQL?
Generally no. The application maintains numbering, status and cost logic, and direct updates can leave inconsistent records. Use supported import functions or the SDK for writes.
Related
JobBOSS Custom Reports: Building and Editing Crystal Reports
JobBOSS reports are Crystal Reports (.rpt) files that read the JobBOSS SQL Server database. To customise one, copy the standard report, open the copy in Crystal Reports, point it at your database, change the fields or layout, and place it where JobBOSS looks for custom reports. JobBOSS2 reporting differs, so check the supported report tooling for your edition.
How-toHow to Close a Job in JobBOSS2
A job in JobBOSS2 will not close cleanly until every routing operation is marked complete, all material has been issued or returned, and all labor and cost transactions are posted. Review the job's Work In Process detail first, clear any open items, then change the job status to Complete and run final job costing before it is locked.
Error fixE2 Shop System Error 5093: Causes and How to Troubleshoot
We could not find an authoritative public definition of E2 error 5093, so treat any single-cause answer with caution. In practice, numbered E2 errors raised at login or while opening a module come from the client talking to the database: a changed server name, a SQL permission or login problem, a missing or mismatched driver, or a network or firewall change. Isolate which with the checks below and give Shoptech support the exact context.
How-toE2 Shop System 7.2 (Shoptech): Versions, Manuals, Training, Support and Reporting
E2 Shop System is Shoptech's ERP and MRP software for job shops and make-to-order manufacturers, covering quoting, orders, scheduling, purchasing, inventory, shop floor tracking and accounting integration. Version 7.2 is one release in its line. For manuals, training, support and upgrade eligibility, Shoptech and its resellers are the authoritative source, so confirm details for your own license.
How-toJobBOSS and QuickBooks Online Integration: What Works and What to Check
JobBOSS and JobBOSS2 are job-shop ERP systems that run quoting, job costing, scheduling and shipping; QuickBooks is an accounting package. The usual pattern is that JobBOSS owns jobs, inventory and invoices, and a summarised accounting interface pushes invoices, receipts and bills into the general ledger. Which QuickBooks flavours (Desktop or Online) and which transactions are supported depends on your edition and release, so confirm with ECI before you buy or plan around it.
How-toHow to Back Up the JobBOSS Database
JobBOSS stores its data in a Microsoft SQL Server database, so a backup is a SQL Server backup, not a copy of program folders. Take a full backup on a schedule, verify it with RESTORE VERIFYONLY, copy it off the server, and take an extra one immediately before any upgrade. Practise a restore into a test database at least once so you know it works.
AI for ERPAI for ECI JobBOSS2 and E2 Shop System
Add AI to ECI JobBOSS2 or E2 Shop System for faster quoting, tighter scheduling, and shop-floor answers, without sending your job data to the cloud.
AI for ERPA Private LLM Grounded on Your ERP Data
How a private LLM answers questions on your ERP data: RAG plus text-to-SQL, role-based permissions inherited from the ERP, and where each fits.
Stuck on JobBOSS and JobBOSS2?
Talk to engineers who work inside JobBOSS and JobBOSS2 every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- JobBOSS Classic Private AI Layer Blueprint GeneratorFill in your version, database, hosting and use cases to get an architecture plan for a private, on-prem AI assistant on JobBOSS Classic, ready to share with IT and security.
- JobBOSS Classic AI Assistant Sizing and Value CalculatorEstimate peak concurrency, GPU count, index size, hours saved and payback for a private AI assistant on JobBOSS Classic.
- JobBOSS to E2 Shop System Migration ChecklistA practical checklist for moving a small shop from JobBOSS to E2 Shop System, from data audit through cutover and first month close. Works in reverse too.
ERP fixes and how-tos
- JobBOSS2 API: Documentation, Keys and Integration OptionsWhat integration options JobBOSS and JobBOSS2 offer: API access, SQL reads, reports and file exchange, how to get access, and how to connect apps or AI safely.
- How to Create Custom Reports in JobBOSS and JobBOSS2Create and customise reports in JobBOSS and JobBOSS2: report designer basics, common shop reports, parameters and SQL-based alternatives.
- JobBOSS and QuickBooks Online Integration: What Works and What to CheckHow JobBOSS and JobBOSS2 work with QuickBooks Online and Desktop: what syncs, what does not, the options, and when a job shop outgrows QuickBooks.
AI on your ERP
- AI for JobBOSS2 quoting and schedulingHow AI helps JobBOSS2 job shops quote from past job actuals and explain scheduling conflicts, with read-only access and private hosting options.
- AI for JobBOSS2 in Precision Machining: Quotes, Routings and Job Cost Answers from Your Own DataPrivate AI for JobBOSS2 precision machine shops: quote history, routing actuals, job cost variance and on-time delivery answers, kept on your own network.
Integrations
- How to connect Power BI to ECI JobBOSS2Connect Power BI to JobBOSS2: SQL Server views, on-premises data gateway, a reporting database, key job shop dashboards, and adding natural-language Q&A.
- How to add AI agents to ECI JobBOSS2How to add AI agents to ECI JobBOSS2: a read-first tool layer over the SQL Server data and API, agents for quotes, late jobs and POs, with human approval on writes.