canonical: https://jentic.com/apis/adaptek.net/adaptek

# Adaptek KonnexMe API

Jentic publishes the only available OpenAPI specification for Adaptek KonnexMe API, keeping it validated and agent-ready. The KonnexMe API powers Adaptek's virtual advisor and client relationship platform for insurance and financial services agencies. It exposes endpoints to manage advisors, agencies, applications, files, folders, branding assets, and FMO (Field Marketing Organization) hierarchies. Operations cover advisor onboarding, holding-company assignment, affiliation management, and document/asset retrieval across both v1 and v2 path prefixes.

## For AI agents

Manage advisors, agencies, applications, and assets in the Adaptek KonnexMe portal. Useful for automating advisor onboarding, FMO hierarchy lookups, and document workflows in insurance and financial services.

## Scope

Does not handle client portfolio holdings, trade execution, or commission processing - use for advisor, agency, and application record management only.

## Capabilities

- Retrieve and update advisor profiles, including holding-company assignments and authorized-advisor lists
- Map portal user IDs to advisor IDs and look up FMO advisors for search workflows
- Manage advisor app-access affiliations across multiple agencies
- Read agency records, agency images, and agency-level branding configuration
- List and update applications and application output records tied to advisors
- Retrieve agent vault information for a specific FMO

## Use cases

### Advisor onboarding automation

Operations agents at FMOs (Field Marketing Organizations) onboard new financial advisors by combining advisor lookup, holding-company assignment, and application affiliation calls. The KonnexMe API exposes each step as a discrete endpoint under /v1/Advisors, so an automation can complete a multi-step setup without operator clicks. Onboarding that previously took 20-30 minutes per advisor can be reduced to a single API workflow.

Example prompt: Call PUT /v1/Advisors/{advisorId}/holdingCompany to assign the new advisor's holding company, then PUT /v1/Advisors/{advisorId}/Affiliations to add the required app access entries.

### FMO advisor directory and search

Compliance and supervisor agents need a current list of advisors authorized under a specific FMO for audits or assignment routing. The /v1/Advisors/fmoadvisorsforsearch and /v1/Advisors/holdingcompanyadvisors endpoints return advisor rosters scoped to the requesting hierarchy, so an agent can answer 'who reports under FMO X' without exporting CSVs from the portal UI.

Example prompt: Call GET /v1/Advisors/fmoadvisorsforsearch with the FMO context and return advisor names, IDs, and holding-company affiliations as a structured table.

### Document and asset retrieval

Advisors and back-office staff frequently need to fetch branding assets, agency images, or application output documents tied to a specific record. KonnexMe exposes file, folder, asset, and image endpoints, letting an agent locate and surface a document by application or agency ID rather than requiring the user to navigate the portal manually. This reduces context-switching during client conversations.

Example prompt: Look up an agency by ID, then call the agency-images endpoint to retrieve the current logo URL for inclusion in a generated client document.

### AI agent advisor lookup via Jentic

An AI assistant inside an FMO uses Jentic to expose KonnexMe advisor lookup as a tool. The agent searches 'find a KonnexMe advisor by ID', Jentic returns the GET /v1/Advisors/{advisorId} schema, and the agent fills the path parameter from user input. Because KonnexMe has no published OpenAPI spec, Jentic's structured spec is the only way an LLM agent can discover and call these endpoints reliably.

Example prompt: Use Jentic to search 'look up advisor by id', load the GET /v1/Advisors/{advisorId} schema, and execute it for advisor ID 12345 to retrieve the advisor's profile.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /v1/Advisors/{advisorId} | Retrieve advisor details |
| PUT | /v1/Advisors/{advisorId} | Update advisor information |
| PUT | /v1/Advisors/{advisorId}/holdingCompany | Assign advisor to holding company |
| GET | /v2/Advisors/{userId} | Get advisor by portal user ID |
| GET | /v1/Advisors/fmoadvisorsforsearch | List FMO advisors for search |
| PUT | /v1/Advisors/{advisorId}/Affiliations | Manage advisor app access affiliations |
| GET | /v1/Advisors/fmoagentvaults/{fmoId} | Retrieve agent vault information for an FMO |

## Key resources

- **Advisors** — Advisor profile records covering retrieval, updates, holding-company assignment, affiliations, and FMO scoping.
- **Agencies** — Agency entities and agency images used for branding within the portal.
- **Applications** — Insurance/financial application records and their generated outputs tied to advisors.
- **AgencyImages** — Branding assets uploaded per agency for portal display and document generation.
- **Assets** — Static and dynamic assets associated with advisors and agencies.

## Why Jentic

- **Setup:** Wiring the Adaptek KonnexMe API by hand means discovering its advisor, agency, and application endpoints without a published spec and threading advisor and FMO ids through each call. Through Jentic you install once, import the Adaptek KonnexMe API from the API Directory, and your agent calls it.
- **Permission scoping:** Adaptek puts the advisor id in the URL path (/v1/Advisors/{advisorId}/...), so a rule can pin your agent to one advisor: it can read and update that advisor's record and affiliations and nothing else. You choose the operations it may call, so holding-company or affiliation writes are not included unless you add them.
- **Credential handling:** This API requires no credential, so there is nothing to store: your Jentic One instance simply executes the operation on your behalf. Nothing about authentication enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'find advisor by portal user id', and Jentic returns the matching KonnexMe operation with its input schema so the agent calls the right endpoint without browsing the reference docs, which matters because Adaptek does not publish a public spec.

## Related APIs

- **Salesforce REST API** — General-purpose CRM that many financial-advisor orgs use instead of a vertical platform.
- **Envestnet API** — Wealth-management platform that pairs with advisor-records systems for portfolio data.
- **Insightly CRM API** — SMB-focused CRM with contact and project endpoints.

## FAQ

### Why is there no official OpenAPI spec for Adaptek KonnexMe API?

Adaptek does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Adaptek KonnexMe API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Adaptek KonnexMe API use?

The published spec does not declare a security scheme, which typically indicates Adaptek issues credentials directly to FMO partners after onboarding. When credentials are added to Jentic they are stored encrypted in your Jentic One instance and injected at execute time so they never appear in agent context.

### Can I look up advisors by FMO with the Adaptek KonnexMe API?

Yes. Call GET /v1/Advisors/fmoadvisorsforsearch to return advisors scoped to the calling FMO, GET /v1/Advisors/holdingcompanyadvisors for holding-company-scoped lists, and GET /v1/Advisors/fmoagentvaults/{fmoId} to retrieve the FMO's agent vault contents.

### How do I assign an advisor to a holding company through Jentic?

Search Jentic for 'assign advisor to holding company', load the PUT /v1/Advisors/{advisorId}/holdingCompany schema, and execute with the advisor ID and holding-company payload. Jentic handles the request and returns the updated advisor record.

### Are there rate limits on the Adaptek KonnexMe API?

Adaptek does not publish rate limits in this spec. In practice, the API is sized for partner FMO traffic - apply conservative client-side throttling and respect any 429 responses surfaced through Jentic.

### Does this API include client-facing financial transactions?

No. KonnexMe focuses on advisor, agency, application, and asset management. It does not process trades, payments, or client portfolio holdings - those live in separate Adaptek systems or third-party advisor platforms.

### Can I limit what my agent is allowed to do with the Adaptek KonnexMe API?

Yes. Because you run Jentic One yourself, your own rules decide which KonnexMe operations the agent may call. Since Adaptek puts the advisor ID in the URL path (/v1/Advisors/{advisorId}/...), you can pin the agent to a single advisor so it only reads and updates that advisor's record and affiliations. You also choose which operations are allowed, so holding-company writes via PUT /v1/Advisors/{advisorId}/holdingCompany or affiliation changes via PUT /v1/Advisors/{advisorId}/Affiliations are excluded unless you grant them.