Install Jentic One Beta

Connect the ManageTradeX - Peppol API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ManageTradeX - Peppol 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.

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%2Fmanagetradex.my%2Fmanagetradex-peppol" | sh

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%2Fmanagetradex.my%2Fmanagetradex-peppol" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 ManageTradeX - Peppol API.

Submit an invoice transaction to the Peppol network in UBL or native format with POST /transactions, passing a transformationId to convert native payloads

List transactions filtered by direction (I for inbound, O for outbound), state, outcome, and createdAtFrom or createdAtTo, with cursor pagination up to 50 per page

Download a transaction artefact such as OUTBOUND_TRANSFORM, INBOUND_TRANSFORM, or VALIDATION_RESULT by artefactId

Acknowledge a COMPLETED transaction with PUT /transactions/{transactionId}/acknowledge once your system has processed it

GET STARTED

Start building with ManageTradeX - Peppol API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use ManageTradeX - Peppol API for, with concrete tasks.

★ Agent-run inbound invoice intake through Jentic

An accounts payable agent lists inbound transactions in the COMPLETED state, downloads each one's transformed artefact for import, and acknowledges it so it drops out of the next run. Through Jentic the agent finds these operations by intent, the OAuth2 client credentials stay in the developer's own Jentic One instance, and a rule can keep the agent on reading and acknowledging while sending stays out.

Call GET /transactions with direction 'I' and state 'COMPLETED', download each INBOUND_TRANSFORM artefact via GET /transactions/{transactionId}/artefacts/{artefactId}, then PUT /transactions/{transactionId}/acknowledge

Sending invoices over Peppol

Outbound invoices are submitted with POST /transactions carrying senderId, receiverId, docType, and the invoice in UBL or native format. Before sending, GET /lookup/participants/{peppolId} confirms the buyer is on the network, and after sending the outcome filter on GET /transactions surfaces any FAILED deliveries for review.

Call GET /lookup/participants/{peppolId} for the buyer, then POST /transactions with senderId, receiverId, docType 'invoice', and the invoice document

Participant onboarding

Before a company can send or receive on Peppol, it is registered through POST /participants with its companyName, brnType, registrationNumber, address, authorizedPerson, and supporting authorizedDocument. GET /participants/{peppolId} then reads the registration and PUT /participants/{peppolId} keeps contact and address details current.

POST /participants with companyName 'Acme Sdn Bhd', brnType, registrationNumber, address, and authorizedPerson, then GET /participants/{peppolId} to read the registration

Key Endpoints

9 endpoints — the managetradex peppol api sends and receives e-invoices over the peppol network through the managetradex platform.

METHOD

PATH

DESCRIPTION

POST

/transactions

Submit a transaction

GET

/transactions

List transactions

GET

/transactions/{transactionId}

Get transaction details

PUT

/transactions/{transactionId}/acknowledge

Acknowledge a processed transaction

GET

/transactions/{transactionId}/artefacts/{artefactId}

Download an artefact

POST

/participants

Create a participant

GET

/lookup/participants/{peppolId}

Look up a Peppol participant

POST

/transactions

Submit a transaction

GET

/transactions

List transactions

GET

/transactions/{transactionId}

Get transaction details

PUT

/transactions/{transactionId}/acknowledge

Acknowledge a processed transaction

GET

/transactions/{transactionId}/artefacts/{artefactId}

Download an artefact

POST

/participants

Create a participant

GET

/lookup/participants/{peppolId}

Look up a Peppol participant

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the ManageTradeX Peppol API by hand means running the OAuth 2.0 client credentials exchange, building UBL or native invoice payloads, and tracking each transaction from PROCESSING to ACKNOWLEDGED yourself. Through Jentic you install once, import the API from the API Directory, store the client credentials once, and your agent calls it.

Permission scoping

ManageTradeX puts the transactionId and peppolId in the URL path, so a rule can pin your agent to one transaction or one participant and the operations you pick. You choose the operations it may call, so sending new transactions or updating participant details is not included unless you add them.

Credential isolation

Your ManageTradeX client 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.

Intent-based discovery

Agents search Jentic by intent such as 'send an invoice over Peppol' or 'list received invoices', and Jentic returns the matching ManageTradeX operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using ManageTradeX - Peppol API through Jentic.

Is there a ManageTradeX Peppol MCP server?

You don't need an MCP server to give your agent the ManageTradeX Peppol API. Jentic connects it directly from the API Directory: import it, store your OAuth2 client credentials once, and your agent calls it. Operations are discovered on demand, so no extra tool definitions sit in the agent's context.

What authentication does the ManageTradeX Peppol API use?

Per its OpenAPI spec, the ManageTradeX Peppol API uses OAuth 2.0 with the client credentials grant, requesting tokens from the /oauth2/token path. Through Jentic the client credentials are stored encrypted by your own Jentic One instance and the token exchange happens at execution time, so the credentials never enter the agent's context.

Can I limit what my agent is allowed to do with the ManageTradeX Peppol API?

Yes. For example, write a rule that allows GET /transactions, GET on a transaction's artefacts, and PUT on its acknowledge path, so the agent can import and acknowledge received invoices but cannot send invoices or change participant registrations. Every call it makes is logged on your own machine.

What does acknowledging a transaction do?

A transaction moves from PROCESSING to COMPLETED when processing ends. Once your system has stored the result, PUT /transactions/{transactionId}/acknowledge moves it to ACKNOWLEDGED as its final state. Acknowledgement only works on a transaction in the COMPLETED state.

How do I send an invoice over Peppol through Jentic?

Install Jentic One, import the ManageTradeX Peppol API from the directory, and search for 'send an invoice over Peppol'. Jentic returns the submit transaction operation with its input schema; your agent sends senderId, receiverId, docType, and the invoice, adding a transformationId if the payload is in a native format. To run it on your own infrastructure, install Jentic One from its GitHub repo.

What are the rate limits for the ManageTradeX Peppol API?

The OpenAPI spec does not specify rate limits. Check the ManageTradeX documentation at https://managetradex.my for current limits. The list operation returns at most 50 transactions per page through its limit parameter.

Managetradex My ManageTradeX - Peppol API

Browse all Managetradex My APIs

AI ReadinessAI-Aware (B-)61/100

See full scorecard

Community OpenAPI document · agent-readyFinanceAccountingoauth29 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Send e-invoices to the Peppol network, list and download received transactions, acknowledge processed ones, and register or look up Peppol participants.

Use for: Send this invoice to a buyer over Peppol, List all inbound Peppol transactions received since Monday, Find all failed outbound transactions this week, Download the transformed invoice for a received transaction

Not supported: Does not handle MyInvois tax validation, payment collection, or general ledger bookkeeping. Use for sending and receiving Peppol e-invoice transactions and managing Peppol participants only.

The ManageTradeX Peppol API sends and receives e-invoices over the Peppol network through the ManageTradeX platform. It submits transactions in UBL or a native format, with an optional transformationId to convert native payloads, and lists inbound and outbound transactions filtered by direction, state, outcome, and creation date. Each transaction exposes its details and downloadable artefacts such as the transformed UBL or validation result, and is acknowledged once your system has processed it. The API also registers and updates Peppol participants with company and authorised person details and looks up any participant by peppolId.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

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.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

19%

Example Density

How richly the API is illustrated with examples.

77%

Example Validity

Percentage of examples that conform to their schemas.

75%

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.

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.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

63%

Summary Coverage

Coverage of summaries across operations/tags/info.

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.

Security

Trust, risk posture, and security compliance.

Grade: ASignals: 1

85%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B+Signals: 1

69%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the ManageTradeX - Peppol API to your agent

Capabilities

Start building with ManageTradeX - Peppol API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Managetradex My ManageTradeX - Peppol API

Jentic AI Readiness Score

ManageTradeX - Peppol API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness