Triquestra Accounts Receivable
Browse all Swaggerhub Triquestra APIs★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controloauth213 EndpointsREST
For 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.
Use for: I need to creates a new debtor account, I want to gets all accounts receivable records that have been modified since the specified, Search for updates an existing debtor account, Find all all address records that have been modified since the specified date/time.
Not supported: Does not handle payments, communications, or crm — use for developer tools only.
Accounts Receivable API. The API exposes 13 endpoints secured with oauth2 authentication.
Install Jentic One Beta
Connect the Accounts Receivable to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Accounts Receivable, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Accounts Receivable API.
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
Patterns agents use Accounts Receivable API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'creates a new debtor account', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
13 endpoints — accounts receivable api.
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
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Accounts Receivable oauth2 credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'creates a new debtor account') and Jentic returns the matching Accounts Receivable operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Accounts Receivable integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
FAQs
Specific to using Accounts Receivable API through Jentic.
What authentication does the Accounts Receivable use?
The Accounts Receivable uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
GET STARTED