# JobBOSS Public API: What Integration Options Exist for JobBOSS and JobBOSS2

> Source: https://netray.co/erp-help/jobboss-public-api-integration-options
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Help

## 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.

## Kind

how-to

## System

job-shop-erp

## Erp

JobBOSS and JobBOSS2

## Module

Integration / API

## Query

jobboss public api

## Alternate Queries

- jobboss integrations
- jobboss integration
- jobboss sql access
- jobboss2 api

## Applies To

JobBOSS (SQL Server edition) and JobBOSS2. Vendor offerings change, so verify API availability and licensing with the vendor for your version.

## Steps

### Plan an integration

**Items:**

- Write down the data flow: for example quote data from a CAD or quoting tool into JobBOSS, or job costs out to an accounting system.
- Ask the vendor or your reseller which interfaces your edition supports: SDK, API, import utility, or database access, and what licensing applies.
- For 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.
- For writing data, use the supported import function or SDK so business rules, numbering and validation are applied.
- Build and test against a copy of the database or a test company before touching production.
- Schedule and log the integration, with an error report that someone reviews.
- Re-test after every JobBOSS upgrade or service pack, since schema or behavior can change.

## Sections

### Direct SQL access for classic JobBOSS

**Body:**

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.

**Code:**

-- 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

**Body:**

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

**Body:**

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.

## 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.

## Ai Angle

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.

## Faq

### Does JobBOSS have a public API?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

jobboss public api, jobboss integration, jobboss integrations, jobboss sql database, jobboss sdk, jobboss2 api, jobboss import, jobboss power bi, jobboss quoting integration, jobboss accounting integration

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json