iptor-base-erp-tables
60
AI ReadinessFoundational (C+)60/100
Community OpenAPI document · agent-readyE CommerceStorefrontbearer7 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Read, add, replace, and delete the multilingual extended description lines of Iptor DC1 ERP items, including which sales and purchase documents each line prints on.
Use for: Get the Spanish description lines for item 5801301, List all extended descriptions that do not print on invoices, I need to add a French description line to an ERP item, Retrieve every language's description for one item
Not supported: Does not handle stock levels, prices, orders, or item master creation. Use for extended item description lines in Iptor DC1 only.
The Iptor Base ERP Tables API reads and maintains extended item descriptions in the Iptor DC1 ERP, the multilingual text lines stored in the SRBPRX table for each item. Each line is keyed by item number, two-letter language code, and line number, and carries up to 60 characters of text plus Y or N print flags that decide whether it appears on sales documents such as quotations, pick lists, and invoices, and purchase documents such as purchase orders and reception notes. Lines can be listed with filters, read per item or per item and language, created in bulk of up to 100 per request, replaced, or deleted.
Install Jentic One Beta
Connect the iptor-base-erp-tables to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the iptor-base-erp-tables, 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%2Fiptor.com%2Fiptor" | 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%2Fiptor.com%2Fiptor" | 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 iptor-base-erp-tables API.
List extended item description lines filtered by item, language, or a print flag such as printOnInvoice=N
Read every description line for one item across all languages, or for one item in one language sorted by line number
Add up to 100 extended description lines for items in one bulk request
Replace a description line's textDescription and print flags by item, language, and lineNumber
Control which documents a line prints on, from quotations and invoices to purchase orders and quality control notes
Delete a single description line without touching other lines for the same item or language
Use Cases
Patterns agents use iptor-base-erp-tables API for, with concrete tasks.
★ Agent-maintained multilingual item text
An AI agent translating product text for a distributor needs to write the result back to the ERP without hand-wiring its auth and headers. Through Jentic the agent searches for 'add an item description line', loads the Iptor create operation, and posts lines with item, language, lineNumber, and textDescription, with the bearer token and Env-Company header handled at call time. It then reads the item back by language to confirm the sequence.
Call POST /extendedItemDescription with item 5801301, language SP, lineNumber 2, and textDescription TAZA DE INODORO, EVAC-90, PISO INCLUYE ANILLO, then call GET /extendedItemDescription/byItem/{item}/{language} for item 5801301 and language SP
Document print-flag audit
An operations team checks that technical description lines appear on the right paperwork. Each SRBPRX line holds Y or N flags for sales documents such as quotations, order confirmations, pick lists, transport notes, and invoices, and for purchase documents such as delivery schedules, purchase orders, reception notes, and quality control notes. The list read filters by printFlag, and a PUT replaces the flags on one line.
Call GET /extendedItemDescription with printFlag printOnInvoice=N, then call PUT /extendedItemDescription/{item}/{language}/{lineNumber} on one returned line with its textDescription and printOnInvoice Y
Item description review before a product sheet export
Before exporting a product sheet, a merchandiser pulls the complete description of an item in every language. The by-item read returns all lines organised by language, so missing translations or stale lines stand out, and an obsolete line can be removed by its composite key.
Call GET /extendedItemDescription/byItem/{item} for item 5801301 and list the languages that have no description lines
Key Endpoints
7 endpoints — the iptor base erp tables api reads and maintains extended item descriptions in the iptor dc1 erp, the multilingual text lines stored in the srbprx table for each item.
METHOD
PATH
DESCRIPTION
GET
/extendedItemDescription
List extended item descriptions with filters
POST
/extendedItemDescription
Create one or more description lines
GET
/extendedItemDescription/byItem/{item}
Get all descriptions for an item
GET
/extendedItemDescription/byItem/{item}/{language}
Get an item's descriptions in one language
PUT
/extendedItemDescription/{item}/{language}/{lineNumber}
Replace a description line
DELETE
/extendedItemDescription/{item}/{language}/{lineNumber}
Delete a description line
GET
/extendedItemDescription
List extended item descriptions with filters
POST
/extendedItemDescription
Create one or more description lines
GET
/extendedItemDescription/byItem/{item}
Get all descriptions for an item
GET
/extendedItemDescription/byItem/{item}/{language}
Get an item's descriptions in one language
PUT
/extendedItemDescription/{item}/{language}/{lineNumber}
Replace a description line
DELETE
/extendedItemDescription/{item}/{language}/{lineNumber}
Delete a description line
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
I
iptor-base-erp-tables
- Foundational (C+)60/100
67
Foundational Compliance74
Developer Experience & Jentic Compatibility34
AI-Readiness & Agent Experience94
Agent Usability75
Security89
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
67
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: BSignals: 4
92%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
75%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
74
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: A-Signals: 4
46%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
34
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
72%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
64%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
75
Security
Trust, risk posture, and security compliance.
Grade: A-Signals: 1
75%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
89
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: ASignals: 1
89%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Iptor by hand means obtaining a JWT bearer token, sending the Env-Company header on every call, and choosing between the test and production hosts. Through Jentic you install once, import the Iptor Base ERP Tables API from the API Directory, store the token once, and your agent calls it.
Permission scoping
Iptor puts the item number in the URL path (/extendedItemDescription/byItem/{item}), so a rule can scope your agent to one item's description reads. You choose the operations it may call, so writes such as the PUT replace or the irreversible DELETE are not included unless you add them.
Credential isolation
Your Iptor 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 'add an item description line' or 'get item descriptions by language', and Jentic returns the matching Iptor operation with its input schema, including the Env-Company header, so the agent calls the right endpoint.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using iptor-base-erp-tables API through Jentic.
What authentication does the Iptor Base ERP Tables API use?
Per its OpenAPI spec, the API uses a bearer token in JWT format on every operation, and each request also needs the Env-Company header naming the environment company. Through Jentic the token is stored by your own instance and attached at call time, so the agent never sees it.
Can I create many item description lines at once with the Iptor API?
Yes. POST /extendedItemDescription accepts either one record or an array of up to 100. Each record needs item, language, lineNumber, and textDescription of at most 60 characters, the item must be active in SROPRG, and lineNumber must be unique per item and language.
What are the rate limits for the Iptor Base ERP Tables API?
The OpenAPI spec does not specify rate limits. Check with Iptor at https://iptor.com for the limits that apply to your DC1 environment.
Is there an Iptor MCP server?
You don't need an MCP server to give your agent the Iptor Base ERP Tables API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls the description operations it needs without loading another server's tool definitions into its context.
Can I limit what my agent is allowed to do with the Iptor Base ERP Tables API?
Yes. For example, write a rule that allows only the two GET operations under /extendedItemDescription/byItem/5801301, and the agent can read that item's descriptions in every language but cannot create, replace, or delete any line. Every call it makes is logged.
How do I read an item's descriptions through Jentic?
Search Jentic for 'get item descriptions by language', load the GET /extendedItemDescription/byItem/{item}/{language} operation, and execute it with the item number and a language code such as EN. Lines come back sorted by line number. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED