canonical: https://jentic.com/apis/swaggerhub.triquestra/accounts-receivable # Triquestra Accounts Receivable Accounts Receivable API. The API exposes 13 endpoints secured with oauth2 authentication. ## For AI agents Programmatically creates a new debtor account, gets all accounts receivable records that have been modified since the specified. Covers 13 operations with oauth2 authentication. ## Scope Does not handle payments, communications, or crm - use for developer tools only. ## Capabilities - Creates a new Debtor Account - Gets all Accounts Receivable records that have been modified since the specified - Updates an existing Debtor Account - Get all address records that have been modified since the specified date/time. - Searches for existing Debtor Accounts - Archives an existing Debtor Account ## Use cases ### Developer Tools Operations Use the Accounts Receivable to perform developer tools operations programmatically. The API provides 13 endpoints covering core functionality including creates a new debtor account, gets all accounts receivable records that have been modified since the specified, updates an existing debtor account. Example prompt: Call POST /accounts_receivable to creates a new debtor account ### Automated Account Categories Management Automate account categories operations by combining multiple Accounts Receivable endpoints. Agents can gets all accounts receivable records that have been modified since the specified and then updates an existing debtor account in a single workflow. Example prompt: Call GET /accounts_receivable to gets all accounts receivable records that have been modified since the specified, then verify the result ### AI Agent Integration via Jentic AI agents discover and call Accounts Receivable endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually. Example prompt: Search Jentic for 'creates a new debtor account', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /accounts_receivable | Creates a new Debtor Account | | GET | /accounts_receivable | Gets all Accounts Receivable records that have been modified since the specified | | PUT | /accounts_receivable | Updates an existing Debtor Account | | GET | /accounts_receivable/addresses | Get all address records that have been modified since the specified date/time. | | POST | /accounts_receivable/search | Searches for existing Debtor Accounts | | GET | /accounts_receivable/{debtor_code} | Gets an existing Debtor Account | | DELETE | /accounts_receivable/{debtor_code} | Archives an existing Debtor Account | | POST | /accounts_receivable/{debtor_code}/addresses | Add or update addresses of a debtor account | ## Key resources - **Account Categories** — Operations related to Account Categories - **Account addresses** — Operations related to Account addresses - **Health Check** — Operations related to Health Check - **accounts_receivable** — Operations related to accounts_receivable ## Why Jentic - **Setup:** Wiring the Triquestra Accounts Receivable API by hand means implementing its OAuth2 flow, managing token refresh, and building your own retries against the debtor and address endpoints. Through Jentic you install once, import Accounts Receivable from the API Directory, store the OAuth2 credentials once, and your agent calls it. - **Permission scoping:** This API puts the debtor code in the URL path (/accounts_receivable/{debtor_code}), so a rule can pin your agent to one debtor: it can read that account and add addresses and nothing else. You choose the operations it may call, so destructive ones like deleting a debtor are not included unless you add them. - **Credential handling:** Your Accounts Receivable OAuth2 credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'create a new debtor account' or 'search accounts receivable', and Jentic returns the matching Accounts Receivable operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Github** — Alternative developer tools API - **Gitlab** — Alternative developer tools API ## FAQ ### What authentication does the Accounts Receivable use? The Accounts Receivable uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context. ### Can I creates a new debtor account with the Accounts Receivable? Yes. Use the POST /accounts_receivable endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the Accounts Receivable? Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer. ### How do I creates a new debtor account through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'creates a new debtor account'. Jentic returns the matching Accounts Receivable operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the Accounts Receivable have? The Accounts Receivable exposes 13 endpoints covering account categories, account addresses, health check operations. ### Can I limit what my agent is allowed to do with the Accounts Receivable API? Yes. Because you run Jentic One yourself, your own rules decide which Accounts Receivable operations and OAuth2 credentials your agent may use. Since the debtor code sits in the URL path (/accounts_receivable/{debtor_code}), you can pin an agent to a single debtor so it only reads that account and adds addresses. You choose the operations it may call, so destructive ones like archiving a debtor stay off unless you explicitly grant them.