Trintech API
Trintech is software used by corporate finance and accounting teams to streamline and control the month-end close, balance sheet reconciliation, transaction matching, journal entry management, and compliance certifications. With an unofficial API, you can list and update account reconciliation statu
What is Trintech?
Trintech is a Finance and Accounting (F&A) technology provider focused on the Record-to-Report process. Its platform (including Adra for mid-market and Cadency for enterprise) powers account reconciliation, transaction matching, journal entry workflows, close task management, and balance sheet certification.
Core product families include:
- Account Reconciliation (balance sheet reconciliations, certification, exceptions)
- Transaction Matching (bank and GL transaction ingestion, rules-driven matching)
- Journal Entry Management (preparation, approval, posting, audit evidence)
- Close Management (task calendars, checklists, ownership, sign-offs)
- Compliance and Controls (review workflows, segregation of duties, audit logs)
Common data entities:
- Accounts (GL accounts, bank accounts) and periods (month/quarter/year)
- Reconciliations (status, thresholds, variances, attachments)
- Transactions (bank statements, GL activity) and match groups
- Journal entries (lines, approvals, postings)
- Close tasks and certifications (owners, reviewers, sign-offs)
- Business units/entities, users/roles, policies, and audit artifacts
The Trintech Integration Challenge
Startups selling into customers that already rely on Trintech face several integration hurdles:
- Product mix and entitlements: Capabilities vary across Adra vs. Cadency, modules licensed, and configured workflows
- Enterprise security controls: SSO (e.g., Azure AD/SAML), MFA, IP/VPN restrictions complicate headless automation
- Portal-first experiences: Many actions live in the web app; public APIs may be limited or differ by account
- Close calendar constraints: Freeze periods, certification gates, and approval chains require careful orchestration
- Data normalization: Recon states, match results, journals, and task metadata differ by configuration and need consistent schemas
How Supergood Creates Trintech APIs
Supergood reverse-engineers authenticated browser flows and network interactions to deliver a resilient API endpoint layer for your Trintech workflows.
- Handles username/password, SSO/OAuth, and MFA (SMS, email, TOTP) securely
- Maintains session continuity with automated refresh and change detection
- Normalizes responses so you can integrate once and rely on consistent objects across modules
- Aligns with customer entitlements and licensing constraints to ensure compliant access
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your product mix, licensing, and authentication model.
- Supergood Builds and Validates Your API
We deliver a hardened Trintech adapter tailored to your workflows and entitlements.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as Trintech evolves.
API Endpoints
Authentication
/auth/sessionsEstablish a session using credentials. Supergood manages MFA (SMS, email, TOTP) and SSO/OAuth when enabled. Returns a short-lived auth token maintained by the platform.
Authentication
/auth/sessions/refreshRefresh an existing token to keep sessions uninterrupted.
Accounts
/accountsList GL/bank accounts with reconciliation and certification status for a given period.
Reconciliations
/reconciliationsCreate or upsert an account reconciliation for a specific period, with thresholds and ownership.
Transactions
/transactions/importImport bank or GL transactions into a reconciliation to enable matching.
Journal Entries
/journal-entriesCreate a journal entry with balanced lines and submit for approval.
Use Cases
Account Reconciliation Automation
- List accounts with reconciliation and certification status by period - Create or update reconciliations with thresholds and ownership - Route for review and capture sign-offs with audit evidence
Transaction Matching Orchestration
- Import bank or GL transactions to a reconciliation - Trigger rules-based matching and retrieve exception summaries - Push adjustments and journal entries for unmatched variances
Journal Entry Workflows
- Create journals with balanced lines, attachments, and references - Submit for approval, track status, and export for posting to ERP - Capture evidence and maintain audit trails
Close Task Management and Certifications
- Sync period calendars and task ownership with ticketing tools - Monitor sign-offs, certifications, and bottlenecks - Export close status dashboards to BI and FP&A systems
Technical Specifications
Authentication
Username/password with MFA (SMS, email, TOTP) and SSO/OAuth where enabled; supports service accounts or customer-managed credentials
Response format
JSON with consistent resource schemas and pagination
Rate limits
Tuned for close-cycle throughput while honoring licensing and usage controls
Session management
Automatic reauth and cookie/session rotation with health checks
Data freshness
Near real-time retrieval of reconciliations, transactions, journals, and certifications
Security
Encrypted transport, scoped tokens, and audit logging; respects Trintech entitlements
Webhooks
Optional asynchronous delivery for long-running matching runs, approvals, and certification updates
Latency
Sub-second responses for list/detail queries under normal load
Throughput
Designed for high-volume transaction imports and reconciliation updates
Reliability
Retry logic, backoff, and idempotency keys minimize duplicate actions
Adaptation
Continuous monitoring for UI/API changes with rapid adapter updates
Frequently asked questions
Supergood supports workflows across Adra and Cadency modules—reconciliation, matching, journals, and close management—subject to your licensing and entitlements. We scope coverage during integration assessment.
We support username/password + MFA (SMS, email, TOTP) and can operate behind SSO/OAuth when enabled. Sessions are refreshed automatically with secure challenge handling.
Yes. You can import transactions, run matching, and pull normalized exception summaries. We expose consistent schemas across configurations so your downstream systems don’t need to handle module-specific differences.
We surface period status, task ownership, and certification gates to ensure actions are performed at compliant times. You can route approvals and sign-offs via webhooks or polling endpoints while respecting controls.