Efekta Cz EFEKTA API
19
AI ReadinessNon-Ready (F)19/100
Community OpenAPI document · agent-readyFinanceBankingapiKey, bearer, oauth2304 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Retrieve client investment accounts and portfolio holdings, read charges and statistics, and manage onboarding, questionnaires, and approval workflows for a securities brokerage. Covers 304 operations across clients, accounts, and compliance.
Use for: Retrieve a client's portfolio by account number, Get portfolio holdings for a specific ISIN, Read the charges on a client's account, Get time-series graph data for a portfolio
Not supported: Does not handle market data feeds, order execution on exchanges, or payment settlement. Use for brokerage client, portfolio, and compliance operations only.
The EFEKTA API powers a Czech securities brokerage (OCP) platform, exposing client investment accounts, portfolio holdings, and the onboarding and compliance workflows around them. Agents retrieve portfolios by account, ISIN, or currency, read account charges, statistics, and time-series graph data, and generate portfolio PDFs. The API also manages client acquisitions, MiFID and ESG investment questionnaires, and front-office, back-office, and compliance approval and authorization requests. Authentication supports an API key, a JWT bearer token, and OAuth2 client-credentials and password flows.
Install Jentic One Beta
Connect the EFEKTA API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the EFEKTA 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%2Fefekta.cz%2Fefekta" | 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%2Fefekta.cz%2Fefekta" | 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 EFEKTA API.
Retrieve client investment accounts and portfolio holdings by account, ISIN, or currency
Read account charges, statistics, and time-series graph data for a portfolio
Manage client acquisitions and their onboarding attributes
Handle MiFID and ESG investment questionnaires for suitability and AML
Process approval and authorization requests through front-office and compliance workflows
Generate portfolio PDFs and download client documents and files
Use Cases
Patterns agents use EFEKTA API for, with concrete tasks.
★ AI Agent Portfolio Reporting
Let an AI agent produce a client portfolio report on request: it retrieves the holdings for an account, reads the account's statistics and time-series graph data, and generates the portfolio PDF. Through Jentic the agent discovers the right EFEKTA operation by intent and calls it with the account number, so a reporting task runs without a developer navigating hundreds of endpoints by hand.
Retrieve a client's portfolio by account number, read its statistics and graph data, then generate the portfolio PDF
Client Onboarding and Suitability
Brokerages must confirm a client's suitability and AML status before acting on their behalf. The API fetches a client's acquisition record and their latest valid investment questionnaire, including MiFID and ESG answers, so an agent can confirm the paperwork is current. This keeps a suitability check tied to live records rather than a stale copy.
Fetch a client's acquisition record and their latest valid investment questionnaire to confirm suitability before an action
Approval and Authorization Workflows
Brokerage operations route requests through front-office, back-office, and compliance stages. The API lists pending approval requests, approves or rejects one by its uid, and checks the status of related authorization requests. An agent uses this to move items through the pipeline and surface anything stuck in compliance.
List pending approval requests, approve one by its uid, then check the status of a related authorization request
Holdings Lookup by Instrument
Analysts often start from an instrument rather than an account to see exposure. The API returns portfolio holdings for a given ISIN across accounts and lists the currencies a portfolio holds. An agent assembles an instrument-level view without exporting the whole book.
Get portfolio holdings for a given ISIN across accounts, then list the portfolio currencies
Key Endpoints
304 endpoints — the efekta api powers a czech securities brokerage (ocp) platform, exposing client investment accounts, portfolio holdings, and the onboarding and compliance workflows around them.
METHOD
PATH
DESCRIPTION
GET
/api/v2/clients/accounts/portfolio/get-by-account/{accountNumber}
Get a client's portfolio by account number
GET
/api/v2/clients/accounts/portfolio/get-by-isin/{isin}
Get portfolio holdings by ISIN
GET
/api/v2/clients/accounts/get-charge/{accountNumber}
Get the charges on a client's account
POST
/api/v2/clients/accounts/portfolio/get-pdf
Generate a portfolio PDF
GET
/api/v2/approval-requests/list
List approval requests
POST
/api/v2/approval-requests/approve/{uid}
Approve an approval request
GET
/api/v2/authorization-requests/status/{uid}
Get an authorization request's status
POST
/api/v2/auth/access-token
Get an OAuth2 access token
GET
/api/v2/clients/accounts/portfolio/get-by-account/{accountNumber}
Get a client's portfolio by account number
GET
/api/v2/clients/accounts/portfolio/get-by-isin/{isin}
Get portfolio holdings by ISIN
GET
/api/v2/clients/accounts/get-charge/{accountNumber}
Get the charges on a client's account
POST
/api/v2/clients/accounts/portfolio/get-pdf
Generate a portfolio PDF
GET
/api/v2/approval-requests/list
List approval requests
POST
/api/v2/approval-requests/approve/{uid}
Approve an approval request
GET
/api/v2/authorization-requests/status/{uid}
Get an authorization request's status
POST
/api/v2/auth/access-token
Get an OAuth2 access token
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.
E
EFEKTA API
- Non-Ready (F)19/100
47
Foundational Compliance50
Developer Experience & Jentic Compatibility11
AI-Readiness & Agent Experience43
Agent Usability40
Security6
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
47
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: D+Signals: 4
88%
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).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
50
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: C-Signals: 4
8%
Example Density
How richly the API is illustrated with examples.
47%
Example Validity
Percentage of examples that conform to their schemas.
46%
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.
11
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
39%
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.
6%
Summary Coverage
Coverage of summaries across operations/tags/info.
43
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: D-Signals: 1
43%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
40
Security
Trust, risk posture, and security compliance.
Grade: D-Signals: 1
40%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
6
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: FSignals: 1
6%
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 EFEKTA by hand means choosing among its API key, JWT bearer, and OAuth2 client-credentials and password flows, and learning its client, account, and approval-request model across hundreds of operations. Through Jentic you install once, import EFEKTA from the API Directory, store the credential once, and your agent calls it.
Permission scoping
EFEKTA puts the account number, ISIN, and request uid in the URL path (/clients/accounts/portfolio/get-by-account/{accountNumber}), so a rule can pin your agent to specific accounts or requests and the operations you pick. You choose the operations it may call, so reading portfolios and statistics can be allowed while actions like approving or rejecting requests are not included unless you add them.
Credential isolation
Your EFEKTA 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 'get a client's portfolio' or 'list approval requests', and Jentic returns the matching EFEKTA 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.
FAQs
Specific to using EFEKTA API through Jentic.
What authentication does the EFEKTA API use?
The EFEKTA API supports several schemes per its OpenAPI spec: an API key passed as a query parameter, a JWT bearer token, and OAuth2 client-credentials and password flows that issue an access token from its auth endpoint. Through Jentic the credential is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's context.
Can I read a client's portfolio with the EFEKTA API?
Yes. The portfolio operations return a client's holdings by account number, by ISIN, or across currencies, with optional details, and related operations return account charges, statistics, and time-series graph data. A separate operation generates a portfolio PDF.
What are the rate limits for the EFEKTA API?
The OpenAPI spec does not specify rate limits; see https://efekta.cz for current limits. Many list operations accept date ranges and filters, so scope queries narrowly rather than pulling the full client base on each call.
Is there an EFEKTA MCP server?
You don't need an MCP server to give your agent the EFEKTA API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls operations like reading a portfolio or listing approval requests. Operations are discovered on demand, so no extra server's tool definitions sit in your agent's context.
Can I limit what my agent is allowed to do with the EFEKTA API?
Yes. Write a rule that allows only the portfolio and statistics read operations, so the agent can report on accounts but cannot approve, reject, or intervene in approval requests. Because EFEKTA addresses accounts and requests by id in the URL path, a rule can also pin the agent to specific accounts, and every call is logged.
How do I read a client's portfolio with the EFEKTA API through Jentic?
Search Jentic for 'get a client's investment portfolio' to find the portfolio-by-account operation, pass the account number, then read the holdings and generate a PDF if needed. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED