Skip to content
All connectors
Unified.to Unified API logo

Unified.to Unified API

Accounting, billing & payments

Keep Unified.to Unified API in step with your orders, invoices and payments without re-keying, with the right person approving what changes.

94 ways to read, 35 ways to write, each write switched on by you.

Quality checks

Built and tested with example responses.

  1. Ready to connect: doneEvery listed action is built in.
  2. Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Unified.to Unified API with Nexra

Connected, approved, proven.

The things teams do most with Unified.to Unified API, an example flow with a person in the loop, and what Nexra keeps as proof.

Top actions

  • Create accountApproval by rule
  • Log candidate noteApproval by rule
  • List chart of accountsRead

Example flow

  1. Unified.to Unified API · List chart of accountsDone
  2. Unified.to Unified API · Create accountNeeds approval
  3. Nexra · Record the decision and result in the evidence chainProven

Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Unified.to Unified API.

What gets logged

  • Whether it ran on its own or who approved it, and under which rule
  • A fingerprint of the exact request sent to Unified.to Unified API
  • Unified.to Unified API's reply: what it created or changed
  • One entry in the evidence chain, linked to the one before

Try this in the sandbox

Run the whole flow with test data in your sandbox, then connect a Unified.to test account before you go live.

For developers

Technical detail

Read and write accounting, CRM, HRIS, ATS, ticketing and file storage data through Unified.to's real-time unified APIs for one end-customer connection.

Unified.to API docs
Source actions
94
Destination actions
35
Data types
57

What you can map

Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.

Accounting connection check1
  • Check accounting connectionSource

    Reads one record ID from the accounting category to prove the token and that category's connection work.

Accounts4
  • Create accountDestinationNot retried automaticallyApproval before production

    Creates a ledger account.

  • Get accountSource

    One account by ID.

  • List chart of accountsSourceIncremental

    Chart of accounts from the connected system, incrementally by updated_gte.

  • Update accountDestinationProvider duplicate protectionApproval before production

    Updates a account (PATCH); only mapped fields are sent.

Ats activities3
  • Log candidate noteDestinationNot retried automaticallyApproval before production

    Adds a private note or task to a candidate or application.

  • Get candidate activitySource

    One candidate activity by ID.

  • List candidate activitiesSourceIncremental

    Candidate activities from the connected applicant tracking system, incrementally by updated_gte.

Ats application statuses1
  • List application statusesSource

    Application statuses (pipeline stages) the ATS uses, optionally for one job.

Ats applications3
  • Create applicationDestinationNot retried automaticallyApproval before production

    Applies a candidate to a job.

  • Get applicationSource

    One application by ID.

  • List applicationsSourceIncremental

    Applications from the connected applicant tracking system, incrementally by updated_gte.

Ats candidates4
  • Create candidateDestinationNot retried automaticallyApproval before production

    Creates a candidate in the connected ATS.

  • Get candidateSource

    One candidate by ID.

  • List candidatesSourceIncremental

    Candidates from the connected applicant tracking system, incrementally by updated_gte.

  • Update candidateDestinationProvider duplicate protectionApproval before production

    Updates a candidate (PATCH); only mapped fields are sent.

Ats companies2
  • Get hiring companySource

    One hiring company by ID.

  • List hiring companiesSourceIncremental

    Hiring companies from the connected applicant tracking system, incrementally by updated_gte.

Ats connection check1
  • Check ATS connectionSource

    Reads one record ID from the ATS category to prove the token and that category's connection work.

Ats documents2
  • Get candidate documentSource

    One candidate document by ID.

  • List candidate document metadataSourceIncremental

    Candidate document metadata from the connected applicant tracking system, incrementally by updated_gte.

Ats interviews2
  • Get interviewSource

    One interview by ID.

  • List interviewsSourceIncremental

    Interviews from the connected applicant tracking system, incrementally by updated_gte.

Ats jobs2
  • Get jobSource

    One job by ID.

  • List jobsSourceIncremental

    Jobs from the connected applicant tracking system, incrementally by updated_gte.

Ats scorecards2
  • Get scorecardSource

    One scorecard by ID.

  • List scorecardsSourceIncremental

    Scorecards from the connected applicant tracking system, incrementally by updated_gte.

Bank transactions2
  • Get bank transactionSource

    One bank transaction by ID.

  • List bank transactions (bank feed, read only)SourceIncremental

    Bank transactions (bank feed, read only) from the connected system, incrementally by updated_gte.

Bills4
  • Create billDestinationNot retried automaticallyApproval before production

    Creates a supplier bill with line items.

  • Get billSource

    One bill by ID.

  • List billsSourceIncremental

    Bills from the connected system, incrementally by updated_gte.

  • Update billDestinationProvider duplicate protectionApproval before production

    Updates a bill (PATCH); only mapped fields are sent.

Categories4
  • Create tracking categoryDestinationNot retried automaticallyApproval before production

    Creates a tracking category (class, department, location or custom).

  • Get tracking categorySource

    One tracking category by ID.

  • List tracking categoriesSourceIncremental

    Tracking categories from the connected system, incrementally by updated_gte.

  • Update tracking categoryDestinationProvider duplicate protectionApproval before production

    Updates a tracking category (PATCH); only mapped fields are sent.

Connection check1
  • Check connectionSource

    Reads one record ID from the category set on the connection (accounting by default) to prove the token and connection work.

Contacts4
  • Create contactDestinationNot retried automaticallyApproval before production

    Creates a customer or supplier contact.

  • Get contactSource

    One contact by ID.

  • List contacts (customers and suppliers)SourceIncremental

    Contacts (customers and suppliers) from the connected system, incrementally by updated_gte.

  • Update contactDestinationProvider duplicate protectionApproval before production

    Updates a contact (PATCH); only mapped fields are sent.

Credit memos2
  • Get credit memoSource

    One credit memo by ID.

  • List credit memos (read only)SourceIncremental

    Credit memos (read only) from the connected system, incrementally by updated_gte.

CRM companies4
  • Create CRM companyDestinationNot retried automaticallyApproval before production

    Creates a company (account) in the connected CRM.

  • Get CRM companySource

    One CRM company by ID.

  • List CRM companiesSourceIncremental

    CRM companies from the connected CRM, incrementally by updated_gte.

  • Update CRM companyDestinationProvider duplicate protectionApproval before production

    Updates a CRM company (PATCH); only mapped fields are sent.

CRM connection check1
  • Check CRM connectionSource

    Reads one record ID from the CRM category to prove the token and that category's connection work.

CRM contacts4
  • Create CRM contactDestinationNot retried automaticallyApproval before production

    Creates a person in the connected CRM.

  • Get CRM contactSource

    One CRM contact by ID.

  • List CRM contactsSourceIncremental

    CRM contacts from the connected CRM, incrementally by updated_gte.

  • Update CRM contactDestinationProvider duplicate protectionApproval before production

    Updates a CRM contact (PATCH); only mapped fields are sent.

CRM deals4
  • Create dealDestinationNot retried automaticallyApproval before production

    Creates a deal (opportunity) in the connected CRM.

  • Get dealSource

    One deal by ID.

  • List dealsSourceIncremental

    Deals from the connected CRM, incrementally by updated_gte.

  • Update dealDestinationProvider duplicate protectionApproval before production

    Updates a deal (PATCH); only mapped fields are sent.

CRM events3
  • Log CRM activityDestinationNot retried automaticallyApproval before production

    Logs a note, task or call against CRM records.

  • Get CRM activitySource

    One CRM activity by ID.

  • List CRM activities (notes, calls, tasks, meetings, emails)SourceIncremental

    CRM activities (notes, calls, tasks, meetings, emails) from the connected CRM, incrementally by updated_gte.

CRM leads4
  • Create leadDestinationNot retried automaticallyApproval before production

    Creates a lead in the connected CRM.

  • Get leadSource

    One lead by ID.

  • List leadsSourceIncremental

    Leads from the connected CRM, incrementally by updated_gte.

  • Update leadDestinationProvider duplicate protectionApproval before production

    Updates a lead (PATCH); only mapped fields are sent.

CRM pipelines2
  • Get pipelineSource

    One pipeline by ID.

  • List pipelines and stagesSourceIncremental

    Pipelines and stages from the connected CRM, incrementally by updated_gte.

Customer payments1
  • List customer payments (read only)SourceIncremental

    Customer payments (read only) from the connected system, incrementally by updated_gte.

Draft bills1
  • Create draft billDestinationNot retried automaticallyApproval before production

    Creates a supplier bill with status DRAFT.

Draft invoices1
  • Create draft invoiceDestinationNot retried automaticallyApproval before production

    Creates a sales invoice with status DRAFT (never sent).

Draft journals1
  • Create draft journal entryDestinationNot retried automaticallyApproval before production

    Creates a manual journal entry with status DRAFT; lines must balance.

Expenses2
  • Get expenseSource

    One expense by ID.

  • List expenses (read only)SourceIncremental

    Expenses (read only) from the connected system, incrementally by updated_gte.

Hris companies2
  • Get employer companySource

    One employer company by ID.

  • List employer companiesSourceIncremental

    Employer companies from the connected HR system, incrementally by updated_gte.

Hris connection check1
  • Check HRIS connectionSource

    Reads one record ID from the HRIS category to prove the token and that category's connection work.

Hris employees2
  • Get employeeSource

    One employee by ID.

  • List employeesSourceIncremental

    Employees from the connected HR system, incrementally by updated_gte.

Hris groups2
  • Get groupSource

    One group by ID.

  • List groups (teams, departments, divisions)SourceIncremental

    Groups (teams, departments, divisions) from the connected HR system, incrementally by updated_gte.

Hris locations2
  • Get work locationSource

    One work location by ID.

  • List work locationsSourceIncremental

    Work locations from the connected HR system, incrementally by updated_gte.

Hris timeoffs3
  • Request time offDestinationNot retried automaticallyApproval before production

    Submits a time-off request with status PENDING.

  • Get time-off requestSource

    One time-off request by ID.

  • List time-off requestsSourceIncremental

    Time-off requests from the connected HR system, incrementally by updated_gte.

Hris timeshifts2
  • Get time shiftSource

    One time shift by ID.

  • List time shiftsSourceIncremental

    Time shifts from the connected HR system, incrementally by updated_gte.

Invoices4
  • Create invoiceDestinationNot retried automaticallyApproval before production

    Creates a sales invoice with line items (never sent to the customer).

  • Get invoiceSource

    One invoice by ID.

  • List invoicesSourceIncremental

    Invoices from the connected system, incrementally by updated_gte.

  • Update invoiceDestinationProvider duplicate protectionApproval before production

    Updates a invoice (PATCH); only mapped fields are sent.

Items2
  • Get itemSource

    One item by ID.

  • List items (read only)SourceIncremental

    Items (read only) from the connected system, incrementally by updated_gte.

Journals4
  • Create journal entryDestinationNot retried automaticallyApproval before production

    Creates a manual journal entry; debits and credits must balance.

  • Get journal entrySource

    One journal entry by ID.

  • List journal entriesSourceIncremental

    Journal entries from the connected system, incrementally by updated_gte.

  • Update journal entryDestinationProvider duplicate protectionApproval before production

    Updates a journal entry (PATCH); only mapped fields are sent.

Organizations2
  • Get organizationSource

    One organization by ID.

  • List organizations (company info)SourceIncremental

    Organizations (company info) from the connected system, incrementally by updated_gte.

Payment terms2
  • Get payment termSource

    One payment term by ID.

  • List payment termsSourceIncremental

    Payment terms from the connected system, incrementally by updated_gte.

Payments2
  • Get paymentSource

    One payment by ID.

  • List payments (read only)SourceIncremental

    Payments (read only) from the connected system, incrementally by updated_gte.

Purchase orders2
  • Get purchase orderSource

    One purchase order by ID.

  • List purchase orders (read only)SourceIncremental

    Purchase orders (read only) from the connected system, incrementally by updated_gte.

Sales orders1
  • List sales orders (read only)SourceIncremental

    Sales orders (read only) from the connected system, incrementally by updated_gte.

Storage connection check1
  • Check storage connectionSource

    Reads one record ID from the storage category to prove the token and that category's connection work.

Storage files3
  • Get fileSource

    One file by ID.

  • List files and folders (metadata)SourceIncremental

    Files and folders (metadata) from the connected file storage system, incrementally by updated_gte.

  • Update fileDestinationProvider duplicate protectionApproval before production

    Updates a file (PATCH); only mapped fields are sent.

Storage folders1
  • Create folderDestinationNot retried automaticallyApproval before production

    Creates a folder (a storage file with type FOLDER).

Taxrates2
  • Get tax rateSource

    One tax rate by ID.

  • List tax ratesSourceIncremental

    Tax rates from the connected system, incrementally by updated_gte.

Ticketing categories2
  • Get ticket categorySource

    One ticket category by ID.

  • List ticket categoriesSourceIncremental

    Ticket categories from the connected ticketing system, incrementally by updated_gte.

Ticketing connection check1
  • Check ticketing connectionSource

    Reads one record ID from the ticketing category to prove the token and that category's connection work.

Ticketing customers4
  • Create ticketing customerDestinationNot retried automaticallyApproval before production

    Creates a customer (requester) in the help desk.

  • Get ticketing customerSource

    One ticketing customer by ID.

  • List ticketing customersSourceIncremental

    Ticketing customers from the connected ticketing system, incrementally by updated_gte.

  • Update ticketing customerDestinationProvider duplicate protectionApproval before production

    Updates a ticketing customer (PATCH); only mapped fields are sent.

Ticketing notes2
  • Get ticket noteSource

    One ticket note by ID.

  • List ticket notesSourceIncremental

    Ticket notes from the connected ticketing system, incrementally by updated_gte.

Ticketing tickets4
  • Create ticketDestinationNot retried automaticallyApproval before production

    Creates a support ticket.

  • Get ticketSource

    One ticket by ID.

  • List ticketsSourceIncremental

    Tickets from the connected ticketing system, incrementally by updated_gte.

  • Update ticketDestinationProvider duplicate protectionApproval before production

    Updates a ticket (PATCH); only mapped fields are sent.

Transactions2
  • Get transactionSource

    One transaction by ID.

  • List transactions (read only)SourceIncremental

    Transactions (read only) from the connected system, incrementally by updated_gte.

Vendor credits1
  • List vendor credits (read only)SourceIncremental

    Vendor credits (read only) from the connected system, incrementally by updated_gte.

Vendor payments1
  • List vendor payments (read only)SourceIncremental

    Vendor payments (read only) from the connected system, incrementally by updated_gte.

Access and limits

Authentication
Unified.to workspace API token plus the end-customer connection ID
Plans and access
A Unified.to workspace plan with the categories you use (Accounting, CRM, HRIS, ATS, Ticketing or Storage) and the target integration enabled. Each connection serves one end-customer connection ID; operations work only for the categories that connection's integration supports. Unified.to calls the downstream API in real time, so object and field support follows the integration's feature matrix.
Test environment
Unified.to workspaces include test connections and sandbox integrations for development.
Rate limits
Unified.to passes through the downstream integration's rate limits as HTTP 429; Nexra honours Retry-After when present.
Pagination
limit (default 100) and offset; Nexra stops when a page returns fewer records than requested.
Provider events
Unified.to webhook subscriptions (native or virtual polling) for accounting objects per connection. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.

Before you build a flow

  • Calls are real time against the downstream system; unsupported objects or fields for an integration return an error from Unified.to.
  • Payments are read from Unified.to's Payment API and items from its Commerce API on the same connection; they work only where the integration supports those objects.
  • Payments, credit memos, vendor credits, transactions, expenses and orders are read only; Nexra never records payments, refunds or credits.
  • Bank transactions are read from Unified.to bank feed transactions and work only where the integration supports bank feeds.
  • Deletes, PUT replacements, reports (balance sheet, profit and loss, trial balance, cash flow, aged receivables and payables) and the free-text query filter are not automated.
  • The maximum limit per page is not documented; Nexra requests at most 100 records per page.
  • Unified.to has no idempotency key; uncertain creates are not repeated automatically.
  • Accounting operations have no prefix; CRM, HRIS, ATS, ticketing and storage operations start with crm_, hris_, ats_, ticketing_ and storage_.
  • The passthrough API (raw calls to the downstream API) is intentionally excluded: it bypasses Nexra's operation-level schemas, write gating and safety rules. The raw response field is never requested or mapped.
  • Deletes, PUT replacements, connection, webhook, secrets-manager and environment management, and the free-text query filter are excluded. The Unified.to connection object is never read because it contains downstream credentials.
  • HRIS: compensation, payslips, payrolls, pay codes, benefits, deductions, bank accounts, documents, devices, SSN or SIN, date of birth, gender, pronouns, marital status, home addresses, personal emails and phones are never read. Employee, company, location and group writes are not offered; time-off requests are created as PENDING only.
  • ATS: date of birth, addresses, job compensation, screening answers and offers are not mapped. Interviews, scorecards, documents and jobs are read only; application status changes and EMAIL activities are not offered.
  • Ticketing notes are read only because the unified model does not distinguish internal notes from public replies that email customers.
  • CRM activities can be logged as NOTE, TASK or CALL only; EMAIL, MARKETING_EMAIL and MEETING events are excluded.
  • Storage: only folder creation and file rename or move are offered; uploads, downloads, file contents and permissions are excluded.
  • The connection test is connection_check.get, which reads one record ID from the configured category (accounting by default, the same organization object as before).

Developer reference

  1. Create the Unified.to credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose Unified.to Unified API, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide

Machine-readable detail: GET /api/public/connect/connectors/unified-to and the Connections API.