Frequently Asked Questions

Most Sage integrations give you raw table names and cryptic column codes — you're left guessing what "RECNUM" or "JC_LN_NMBR" means. OPDC is different. We map every endpoint to real-world field names that make sense: "jobNumber", "vendorName", "costCode", "invoiceAmount". You don't need a Sage data dictionary open in another tab. The API reads like the business domain it represents. This was a deliberate design choice after building 20+ Sage integrations and watching developers waste hours decoding field names.

That's by design. OPDC is more like an SDK than a raw database connector. When you query a job, you get "jobNumber", "description", "contractAmount" — not the 47 Pervasive columns that Sage stores under the hood. We automatically handle field mapping, data type conversion, null handling, and cross-table joins behind the scenes. You get clean, predictable JSON without needing to understand Sage's internal schema. The complexity is still there — you just don't have to deal with it.

Yes. OPDC exposes a standard REST API with JSON responses. Every endpoint is documented with OpenAPI (Swagger), and we host interactive docs where you can test calls directly. Visit the Developers page to explore the full API reference.

Jobs, vendors, cost codes, cost types, GL accounts, AP invoices, purchase orders, payroll records, inventory items, and more. OPDC covers the core Sage 100 Contractor modules that accounting teams and integrators work with daily. If you need access to a table we haven't exposed yet, let us know — we add new endpoints based on customer need.

Yes. OPDC supports validated write operations for specific workflows: payroll import, AP invoice posting, inventory transactions, and more. Every write goes through a validation layer that enforces Sage's own business rules — cost code structures, GL account formats, fiscal period rules — before anything touches the database. This isn't a raw SQL pipe. It's a controlled transaction layer that protects your data integrity.

OPDC returns structured error responses with clear, human-readable messages. If a cost code doesn't exist, a GL account format is wrong, or a fiscal period is closed, you'll get a specific error explaining exactly what failed and why — not a generic database exception. Every error includes the field that failed, the rule that was violated, and a description your team can act on without digging through Sage documentation.

There are no hard rate limits or per-call metering on the standard plan. OPDC is designed to handle the throughput that real integrations demand — bulk payroll imports, report generation, inventory syncs — without throttling. If you're planning an unusually high-volume workload, let us know during onboarding and we'll make sure your server resources are sized appropriately.

Yes. OPDC natively supports multi-company Sage 100 Contractor environments. A single OPDC installation can serve all companies on your Sage instance. You specify which company you're querying via the API, and OPDC routes to the correct dataset. This means one install, one configuration, and full access across all your Sage companies — no need to deploy separate connectors per company.

OPDC connects directly to the SQL database that Sage 100 Contractor uses. It runs as a Windows service on the same server (or a server with network access to the Sage database). No ODBC wrappers, no middleware — it speaks the database's native protocol.

Yes. OPDC supports a wide range of Sage 100 Contractor versions. The underlying database structure is stable across versions, and our field mapping layer handles version-specific differences. If you're unsure about your version, reach out and we'll confirm compatibility.

Absolutely. OPDC is designed to be the single gateway for all your Sage 100 data needs. Reports, inventory apps, payroll integrations, custom dashboards — they all connect through the same API simultaneously. Each connection is authenticated independently with its own API key.

No. OPDC sits on-premise inside your network. No firewall ports need to be opened and no VPN is required, which minimizes IT concerns during deployment. The Sage database itself remains completely isolated — the API layer is accessible through OPDC's secure tunnel, but traffic never touches your database directly. All communication is encrypted using mutual TLS (mTLS), so both the client and server authenticate each other before any data is exchanged.

Users authenticate through Auth0 with support for LDAP and enterprise identity providers before any API key is issued or validated. This applies to both Twinn Reports and the integrations dashboard. Once authenticated, every API request requires a valid API key tied to a specific organization and permission set. Keys are issued through the Twinn dashboard and can be revoked at any time. All traffic is encrypted using mTLS.

Yes. Every API call — read or write — is logged with the authenticated user, timestamp, endpoint, and payload. You can review audit logs through the Twinn dashboard. This makes compliance reviews and troubleshooting straightforward.

OPDC runs as a Windows service with automatic restart capability. If the service stops, it restarts automatically. Your Sage 100 Contractor installation is unaffected — OPDC is read-only by default and never modifies the Sage database unless explicitly performing a validated write operation. Sage continues to operate normally with or without OPDC running.

OPDC requires administrative rights to install on the server. The installer registers a Windows service, configures the secure tunnel, and sets up local certificates for mTLS. All of our code is EV (Extended Validation) signed, meeting the strictest code-signing compliance standards. This means Windows SmartScreen and enterprise security policies will recognize OPDC as trusted software from a verified publisher.

We take security seriously across every layer of the product. OPDC uses mTLS encryption, Auth0 authentication with LDAP support, EV code signing, full audit logging, and on-premise isolation — your data never leaves your network. While we are not currently SOC 2 certified, these controls align with the requirements that enterprise compliance teams evaluate. Members of our team have organized and prepared multiple companies for SOC 2 audits at previous roles, so we know what's involved. If SOC 2 certification is a requirement for your organization, we're happy to start the process. We're also available to walk through our security posture in detail during onboarding or provide documentation for your IT review.

Every OPDC subscription includes direct access to our engineering team for setup, troubleshooting, and ongoing support. We respond within one business day and most issues are resolved in a single session. For integrator plans, support is covered under contracted SLAs with guaranteed response times. If you need priority support on the standard plan, reach out and we'll discuss options.

OPDC starts at $3,000 per year for read-only access, which includes Twinn Reports, our Excel plugin, and the on-premise connector. Full read and write API access starts at $6,500 per year. Both plans include multi-company support and ongoing updates. No per-user fees, no per-call metering — one flat annual subscription. Contact us if you'd like a walkthrough or need a quote tailored to your environment.

We offer time & materials consulting for custom integrations — payroll imports, AP automation, inventory workflows, or anything else that connects to Sage 100 Contractor through OPDC. Engagements start at 15 hours, valid over 60 days. Larger packages are available upon request. You get a dedicated developer who already knows the Sage data model, so there's no ramp-up time.

We don't offer a self-serve trial, but we're happy to run a live demo against sample data so you can see the API in action. If you want to see something specifically tailored to your data, have a recent backup of your Sage company available for upload and we'll configure the demo around it. Reach out through the contact page or book a call and we'll set one up.

Yes — this is exactly what OPDC was built for. If you're a software vendor or integrator and your product needs to read or write Sage 100 Contractor data, OPDC acts as the managed middleware layer between your application and Sage. You build against our API. We handle the database connectivity, field mapping, validation, and infrastructure. Your team never has to learn Sage internals. Authentication is handled through Auth0, so we can accept provisioned users from your identity provider — no separate credential management required.

The integrator plan starts at $11,000 per year. It includes everything in the standard OPDC subscription plus SigNoz observability dashboards, rich structured logging for every API call, and contracted SLAs. You get full visibility into request volume, latency, error rates, and payload details — the same tooling we use internally. SLAs are tailored to your integration requirements and agreed upon during onboarding. We also offer significantly reduced per-customer pricing for additional API keys as you scale.

Either way works. Some integrators route all traffic through their own backend and treat OPDC as an internal service. Others provision API keys per customer and let them connect directly. We'll help you design the architecture that fits your product.

Most installations are completed in a single session. Install the Windows service, point it at your Sage 100 Contractor database, configure your API keys, and you're live. There's no lengthy onboarding, no data migration, and no cloud setup required. If you plan to use OPDC for updating or inserting data, we recommend spinning up a replica of your production instance first to validate all transactions before going live.

No. OPDC installs separately and connects to your existing Sage database. It doesn't modify any Sage files, settings, or database structures. Your Sage installation remains completely untouched.

OPDC runs on Windows Server (2016 or later) or Windows 10/11. It needs network access to the database that Sage 100 Contractor uses. Resource requirements are minimal — it runs comfortably alongside Sage on existing hardware.

Reach out through our contact page or schedule a call. We'll walk you through the setup, confirm compatibility with your Sage version, and get you up and running. Most teams are pulling data through the API within a day of installation.