TDox Web Services API
✓ Official Vendor SpecE CommerceStorefrontapiKey18 EndpointsREST
For Agents
Programmatically check authentication token, insert or update a customer. Covers 18 operations with apiKey authentication.
Use for: I need to check authentication token, I want to insert or update a customer, Search for customers, Find all disable a customer
Not supported: Does not handle payments, communications, or crm - use for e-commerce only.
TDox turns business processes and paper forms into mobile apps. The designer allows creating forms, which are filled in using the mobile app. This API provides access to manage centers, customers, documents, products, and agenda items. The API exposes 18 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the TDox Web Services API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the TDox Web Services API, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftdox.com%2Ftdox" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftdox.com%2Ftdox" | 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 TDox Web Services API.
Check authentication token
Insert or update a customer
Search customers
Disable a customer
Subscribe to a document model
Unsubscribe from a document model
Get last instance data for a document model
Use Cases
Patterns agents use TDox Web Services API for, with concrete tasks.
★ E-Commerce Operations
Use the TDox Web Services API to perform e commerce operations programmatically. The API provides 18 endpoints covering core functionality including check authentication token, insert or update a customer, search customers.
Call GET /api/Centers/CheckToken/{token} to check authentication token
Automated Agenda Management
Automate agenda operations by combining multiple TDox Web Services API endpoints. Agents can insert or update a customer and then search customers in a single workflow.
Call POST /api/Customers/InsertOrUpdate/{key} to insert or update a customer, then verify the result
AI Agent Integration via Jentic
AI agents discover and call TDox Web Services API 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 apiKey tokens manually.
Search Jentic for 'check authentication token', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
18 endpoints — tdox turns business processes and paper forms into mobile apps.
METHOD
PATH
DESCRIPTION
GET
/api/Centers/CheckToken/{token}
Check authentication token
POST
/api/Customers/InsertOrUpdate/{key}
Insert or update a customer
POST
/api/Customers/Search
Search customers
POST
/api/Customers/Disable
Disable a customer
POST
/api/Documents/Subscribe/{idModel}
Subscribe to a document model
POST
/api/Documents/Unsubscribe/{idModel}
Unsubscribe from a document model
GET
/api/Documents/GetLastInstanceData/{idModel}
Get last instance data for a document model
GET
/api/Documents/GetDownloadId/{instance}
Get download ID for a document instance
GET
/api/Centers/CheckToken/{token}
Check authentication token
POST
/api/Customers/InsertOrUpdate/{key}
Insert or update a customer
POST
/api/Customers/Search
Search customers
POST
/api/Customers/Disable
Disable a customer
POST
/api/Documents/Subscribe/{idModel}
Subscribe to a document model
POST
/api/Documents/Unsubscribe/{idModel}
Unsubscribe from a document model
GET
/api/Documents/GetLastInstanceData/{idModel}
Get last instance data for a document model
GET
/api/Documents/GetDownloadId/{instance}
Get download ID for a document instance
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the TDox Web Services API by hand means sending your token in the Authorization header, targeting the tdox-webapi-public.azurewebsites.net host, and building your own retry handling across its customer and document endpoints. Through Jentic you install once, import the TDox Web Services API from the API Directory, store the token once, and your agent calls it.
Permission scoping
The TDox Web Services API puts the model id in the URL path (/api/Documents/Subscribe/{idModel}, /api/Documents/GetLastInstanceData/{idModel}), so a rule can pin your agent to one document model: it can read its last instance data. You choose the operations it may call, so state changes like subscribing, unsubscribing, or disabling a customer are not included unless you add them.
Credential isolation
Your TDox token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'check an authentication token' or 'get the last document instance data', and Jentic returns the matching TDox Web Services API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe
Alternative e commerce API
Choose Stripe when you need a different approach to e commerce operations
FAQs
Specific to using TDox Web Services API through Jentic.
What authentication does the TDox Web Services API use?
The TDox Web Services API uses an API key passed in the `Authorization` header. 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 check authentication token with the TDox Web Services API?
Yes. Use the GET /api/Centers/CheckToken/{token} endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the TDox Web Services API?
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 check authentication token through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'check authentication token'. Jentic returns the matching TDox Web Services API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the TDox Web Services API have?
The TDox Web Services API exposes 18 endpoints covering agenda, centers, customers operations.
GET STARTED