--- title: Stax.ai API Integration on Truto slug: staxai category: Accounting canonical: "https://truto.one/integrations/detail/staxai/" --- # Stax.ai API Integration on Truto **Category:** Accounting **Status:** Beta ## MCP-ready AI tools Truto exposes 32 tools for Stax.ai that AI agents can call directly. - **list_all_stax_ai_stacks** — List all stacks for the current team in stax. Returns: id. - **get_single_stax_ai_stack_by_id** — Get a single stax stack by identifier. Returns: id. - **create_a_stax_ai_stack** — Create a new stax stack for the current team. Returns: id. - **update_a_stax_ai_stack_by_id** — Update an existing stax stack. Returns: id. - **delete_a_stax_ai_stack_by_id** — Delete a stax stack by identifier. Returns an empty 204 response on success. - **list_all_stax_ai_stack_documents** — List documents in a stax stack. Returns document records from the stack with pagination and filtering support. Returns: id. - **list_all_stax_ai_documents** — Search documents in Stax using Elasticsearch. Returns document objects including id and content-type-specific attributes; full field breakdown depends on the document's schema in Stax. - **get_single_stax_ai_document_by_id** — Get a single document in Stax. Returns the document object including id and content-type-specific attributes; full field breakdown depends on the document's schema in Stax. - **create_a_stax_ai_document** — Create a new document in Stax. Returns the created document object including id and content-type-specific attributes; full field breakdown depends on the document's schema in Stax. - **update_a_stax_ai_document_by_id** — Update an existing document in Stax. Returns the updated document object including id and content-type-specific attributes; full field breakdown depends on the document's schema in Stax. - **delete_a_stax_ai_document_by_id** — Delete a document in Stax.ai. Requires docId. Returns success field indicating if the document was removed successfully. - **stax_ai_documents_upload** — Upload one or more documents (up to 10 files) to Stax.ai. Returns an uploads array with key document fields such as _id, name, format, download URL, and metadata. - **stax_ai_documents_move** — Move a specific document in Stax.ai to another stack. Requires docId and stackId. Returns a success flag indicating whether the operation was successful. - **stax_ai_documents_copy** — Copy a document to another stack in Stax.ai. Requires docId and stackId in the request body. Returns document details including _id, name, stack, format, and metadata fields. - **stax_ai_documents_archive** — Archive a document in Stax.ai using the required docId. Returns the success field indicating whether the document was successfully archived. - **stax_ai_documents_restore** — Restore an archived document in Stax.ai. Requires docId. Returns success field indicating whether the restore operation was completed successfully. - **stax_ai_documents_download** — Download the original document file from Stax.ai using id. Returns the document file in binary format as application/pdf or application/octet-stream. - **list_all_stax_ai_recent_documents** — List recently viewed documents in Stax. Returns: id. - **list_all_stax_ai_document_jobs** — List document_jobs in Stax.ai. Returns job details including _id, team, user, success, working, error, worker, queueTime, startTime, endTime, jobType, jobId, and jobData for each job. - **list_all_stax_ai_document_duplicates** — Find duplicate documents in stax by comparing a document's checksum against all stored documents. Returns an array of matching Document objects; each item includes id. Required: docId. - **list_all_stax_ai_archive_search** — Search archived documents in stax. Returns a list of archived document records from the results collection; the exact field-level shape of each record is document-specific and not enumerated in the available source — consult the stax API docs for the full record schema. - **list_all_stax_ai_tpa_plans** — List all TPA plans in stax. Returns: planId, externalReference. - **get_single_stax_ai_tpa_plan_by_id** — Get TPA plan in Stax.ai by id. Returns planName, planType, active status, internalPlanId, pensionProId, directory, notes, and lastModified fields for the specified plan. - **create_a_stax_ai_tpa_plan** — Create a new TPA plan in stax. Returns: planId, externalReference. - **list_all_stax_ai_tpa_accounts** — List all TPA accounts for a plan in stax. Returns: accountId, accountNumber, planId, externalReference. Required: planId. - **get_single_stax_ai_tpa_account_by_id** — Get a single TPA account in stax by its account ID. Returns: accountId, accountNumber, planId, externalReference. - **create_a_stax_ai_tpa_account** — Create a new TPA account in stax and associate it with a plan. Returns: accountId, accountNumber, planId, externalReference. Required: planId, accountNumber. - **list_all_stax_ai_tpa_statements** — List all TPA statements in stax. Returns: statementId, planId, accountId, accountNumber, externalReference. - **create_a_stax_ai_tpa_statement** — Attach a new TPA statement in stax. Returns: statementId, planId, accountId, accountNumber, externalReference. - **stax_ai_tpa_statements_confirm** — Confirms (locks) a TPA statement by its ID, preventing further modifications to the statement. The endpoint accepts a POST request to /tpa/statement/confirm with a statement ID and requires cookie or bearer token authentication. - **list_all_stax_ai_tpa_transactions** — List TpaTransaction records for a statement in stax. Returns: id, attributes (transaction-specific fields defined in the stax Trust Accounting API schema; each TpaStatement has many TpaTransaction records). - **create_a_stax_ai_tpa_transaction** — Create a new TpaTransaction record in stax. Returns the created transaction including id and attributes (transaction-specific fields defined in the stax Trust Accounting API schema). ## How it works 1. **Link your customer's Stax.ai account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach Stax.ai.** The Proxy API is a 1-to-1 mapping of the Stax.ai API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Automate Form 5500 and ERISA compliance prep** — Compliance and tax software vendors can pull reconciled trust accounting data from Stax.ai to auto-populate Form 5500s and audit packages, eliminating manual transcription from brokerage PDFs. - **Provision TPA workspaces from your CRM** — Practice management and CRM platforms serving retirement TPAs can auto-create Stax.ai plans, accounts, and document stacks the moment a new plan sponsor is onboarded, keeping client environments in lockstep. - **Offload 401(k) census and payroll extraction** — Payroll and benefits aggregators can push raw payroll files into Stax.ai's AI extraction engine instead of building their own parsers, then surface structured census data back to TPA users when processing completes. - **Embed trust accounting ledgers in financial SaaS** — Accounting and reporting tools can mirror Stax.ai's Plan → Account → Statement → Transaction hierarchy to build external ledgers, dashboards, and reconciliation views over retirement plan finances. - **Centralize retirement document intake** — Document portals and client experience tools can route brokerage statements, payroll files, and plan documents into the right Stax.ai stacks with duplicate detection, giving TPAs a single audit-friendly source of truth. ## What you can build - **Async document upload with job status polling** — Upload unstructured PDFs via the documents upload endpoint and track AI extraction progress through the document jobs endpoint to notify users when parsed data is ready. - **Trust accounting hierarchy sync** — Periodically sync TPA plans, accounts, statements, and transactions into your own data model to power reporting, ledgers, or compliance workflows. - **Statement lock and reconciliation workflow** — Let users review extracted transactions inside your app and call the statement confirm endpoint to lock reconciled statements before audits. - **Duplicate-aware document routing** — Check incoming files against the document duplicates endpoint before moving them into client-specific stacks, keeping audit trails clean. - **Programmatic client onboarding** — Trigger creation of Stax.ai stacks and TPA plans from your onboarding flow so every new plan sponsor gets a ready-to-use workspace without manual setup. - **In-app document search and recents** — Surface Stax.ai's indexed documents and recent activity inside your UI so users can find brokerage statements and plan documents without leaving your product. ## FAQs ### How does authentication work for end users connecting their Stax.ai account? Truto handles the credential exchange and token storage for Stax.ai on your behalf, so your end users connect once through your app and you make API calls through Truto without managing secrets directly. ### How do I know when an uploaded document has finished AI extraction? Stax.ai processes documents asynchronously. After calling the document upload endpoint, poll the list document jobs endpoint to watch for `working`, `success`, or `error` states before pulling extracted data. ### Can I sync the full trust accounting hierarchy? Yes. The integration exposes TPA plans, accounts, statements, and transactions as separate resources, so you can walk the hierarchy from a plan down to individual line-item transactions extracted from brokerage statements. ### How do I prevent duplicate brokerage statements from cluttering a client's records? Use the list document duplicates endpoint to run a checksum-based duplicate check before moving a file into a stack with the document move action. ### Can statements be locked for compliance once reconciled? Yes. Call the TPA statements confirm action to finalize a statement after reconciliation, which prevents accidental overwrites ahead of an ERISA audit. ### Can I create new client workspaces programmatically? Yes. Use the create stack and create TPA plan endpoints to provision document silos and plan records on demand, typically triggered when a new plan sponsor is onboarded in your product.