Salt Edge Account Information API
✓ Official Vendor SpecDeveloper ToolsSource ControlapiKey46 EndpointsREST
For Agents
Programmatically list of accounts, list of assets. Covers 46 operations with apiKey authentication.
Use for: I need to of accounts, I want to of assets, Search for of attempts, Find all attempt object
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
API Reference for services. The API exposes 46 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the Salt Edge Account Information API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Salt Edge Account Information 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%2Fsaltedge.com%2Fsaltedge" | 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%2Fsaltedge.com%2Fsaltedge" | 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 Salt Edge Account Information API.
List of accounts
Attempt object
Improve transaction categorization
Create Connect session
Monitor Salt Edge Account Information API operational status and events
Use Cases
Patterns agents use Salt Edge Account Information API for, with concrete tasks.
★ Developer Tools Operations
Use the Salt Edge Account Information API to perform developer tools operations programmatically. The API provides 46 endpoints covering core functionality including list of accounts, list of assets, list of attempts.
Call GET /accounts to list of accounts
Automated Accounts Management
Automate accounts operations by combining multiple Salt Edge Account Information API endpoints. Agents can list of assets and then list of attempts in a single workflow.
Call GET /assets to list of assets, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Salt Edge Account Information 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 'list of accounts', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
46 endpoints — api reference for services.
METHOD
PATH
DESCRIPTION
GET
/accounts
List of accounts
GET
/assets
List of assets
GET
/attempts
List of attempts
GET
/attempts/{attempt_id}
Attempt object
POST
/categories/learn
Improve transaction categorization
GET
/categories
List of categories
POST
/connect_sessions/create
Create Connect session
POST
/connect_sessions/reconnect
Create Connect session to reconnect
GET
/accounts
List of accounts
GET
/assets
List of assets
GET
/attempts
List of attempts
GET
/attempts/{attempt_id}
Attempt object
POST
/categories/learn
Improve transaction categorization
GET
/categories
List of categories
POST
/connect_sessions/create
Create Connect session
POST
/connect_sessions/reconnect
Create Connect session to reconnect
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Salt Edge Account Information API by hand means sending both the App-id and Secret headers on every request to www.saltedge.com/api/v5 and handling paging and retries yourself. Through Jentic you install once, import Salt Edge from the API Directory, store the App-id and Secret once, and your agent calls it.
Permission scoping
Salt Edge puts the resource id in the URL path (/attempts/{attempt_id}), so a rule can pin your agent to specific attempts and connections: it can read the ones you allow and nothing else. You choose the operations it may call, so actions like creating connect sessions are not included unless you add them.
Credential isolation
Your Salt Edge App-id and Secret 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 'list accounts' or 'get an attempt', and Jentic returns the matching Salt Edge 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
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
FAQs
Specific to using Salt Edge Account Information API through Jentic.
What authentication does the Salt Edge Account Information API use?
The Salt Edge Account Information API uses an API key passed in the `App-id` 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 list of accounts with the Salt Edge Account Information API?
Yes. Use the GET /accounts endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Salt Edge Account Information 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 list of accounts through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list of accounts'. Jentic returns the matching Salt Edge Account Information API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Salt Edge Account Information API have?
The Salt Edge Account Information API exposes 46 endpoints covering accounts, assets, attempts operations.
Can I limit what my agent is allowed to do with the Salt Edge Account Information API?
Yes. Because you run Jentic One yourself, your own rules decide which Salt Edge operations and credentials the agent may use. Since Salt Edge puts the resource id in the URL path, such as GET /attempts/{attempt_id}, you can pin the agent to specific attempts and connections and let it read only the ones you allow. You also pick the operations it may call, so write actions like POST /connect_sessions/create stay out of reach unless you add them.
GET STARTED