Efbin Eleusoft EfBin.org

Name: Eleusoft EfBin.org API
Brand: Eleusoft EfBin.org
Availability: InStock

★ Only Publicly Available OpenAPI DocumentStorageDocument Managementnone177 EndpointsREST

For Agents

Manage EFormBin bins, attributes, users, and schema-conversion utilities for structured form storage.

Install Jentic One Beta

Connect the Eleusoft EfBin.org to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Eleusoft EfBin.org, 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%2Fefbin.org%2Fefbin" | 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%2Fefbin.org%2Fefbin" | 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 Eleusoft EfBin.org API.

Manage bins and the attributes attached to them across an EFormBin server

List, create, and inspect bin instances that hold concrete records inside a bin

Administer users, roles, profiles, and OAuth app users for an EFormBin deployment

GET STARTED

Start building with Eleusoft EfBin.org API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Eleusoft EfBin.org API for, with concrete tasks.

★ Form-data ingestion service

An EFormBin deployment ingests submissions from a variety of forms across an organisation. Operators use the bin and bin-attribute endpoints to model the data, the bin-instance endpoints to query stored records, and the activity timegraph endpoint to monitor traffic. The 177-endpoint surface mirrors the full admin UI, so operations work that previously required a browser session can run as automated jobs.

GET /bin to list all bins, then GET /bininstance/{bin} for the target bin to enumerate its stored records.

Schema generation from existing assets

Teams adopting EFormBin often have legacy HTML forms or XSD documents and need matching Eleusoft schemas to onboard them. The form2schema and xsd2schema endpoints accept the source document and return a schema definition, which can be persisted back into EFormBin as a new bin. This shortens migration projects from days to minutes per form.

POST the existing XSD to /xsd2schema and persist the resulting Eleusoft schema by creating a new bin via POST /bin.

User and role administration

An admin tool driven by the EFormBin API provisions users, assigns roles, and manages profiles and OAuth app-user records without UI clicks. The login-log and error-handler-log endpoints support investigations when users report access problems. Because the spec exposes 177 admin operations, an automation can perform bulk changes that would otherwise require manual session work.

Use the user, role, and profile endpoints to provision a new user and assign their role, then read /loginLog to confirm a successful first login.

EFormBin admin agent through Jentic

An operations agent fields admin requests for an EFormBin deployment - adding bins, generating schemas, and pulling logs - and must do so against a 177-endpoint surface. Through Jentic, the agent searches by intent, receives the matching operation, and executes it. Jentic shields the agent from the full breadth of the spec.

Search Jentic for 'create a bin attribute in EFormBin', load the schema, execute the call, and verify with a follow-up listing.

Key Endpoints

177 endpoints — eleusoft efbin.

METHOD

PATH

DESCRIPTION

GET

/bin

List bins and attributes

POST

/bin

Create a bin

DELETE

/delete/*

Delete a bin

GET

/activity

Time-graph of activity for a bin query

POST

/xsd2schema

Generate a schema from an XSD

GET

/csrf.do

Expose a CSRF token

POST

/changePassword.do

Change a user's password

GET

/bin

List bins and attributes

POST

/bin

Create a bin

DELETE

/delete/*

Delete a bin

GET

/activity

Time-graph of activity for a bin query

POST

/xsd2schema

Generate a schema from an XSD

GET

/csrf.do

Why Jentic?

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

Setup

Wiring EFormBin by hand means tracking its session and CSRF handling and stitching the bin, schema, and log operations together across a wide surface yourself. Through Jentic you install once, import the Eleusoft EfBin.org API from the API Directory, store any session credential once, and your agent calls it.

Permission scoping

These EFormBin operations identify targets through the request or a wildcard delete path rather than a stable resource id, so scope the agent by operation: limit it to the calls it needs, such as GET /bin and POST /xsd2schema. You choose the operations it may call, so DELETE /delete/* is not included unless you add it.

Credential isolation

Any EFormBin session credential or CSRF 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 'create a bin' or 'generate a schema from XSD', and Jentic returns the matching EFormBin operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Eleusoft EfBin.org API through Jentic.

What authentication does the Eleusoft EfBin.org API use?

The OpenAPI spec does not declare a security scheme, but the API documentation states that most calls require the user to be authorised. Authorisation is handled by the EFormBin server itself, typically via a session and CSRF token retrieved from /csrf.do. Jentic stores any provided credentials encrypted and injects them at execution time.

Can I generate a schema from an existing form with this API?

Yes. POST /form2schema generates an Eleusoft schema from an HTML form, and POST /xsd2schema generates one from an XSD. Both endpoints accept the source document and return a schema definition you can persist back into EFormBin.

How do I list and manage bins through the API?

GET /bin lists bins and their attributes, POST /bin creates a new bin, and DELETE /delete/* removes one. Bin attributes are managed through the dedicated BinAttribute endpoints, and the BinInstance endpoints expose concrete records stored inside each bin.

What are the rate limits for the EfBin.org API?

Rate limits are not declared in the spec. As a self-hosted Eleusoft deployment, practical limits depend on the operator's server. Build retries with exponential backoff and avoid tight polling on the activity timegraph and log endpoints.

How do I create a bin through Jentic?

Run pip install jentic, search Jentic for 'create a bin in EFormBin', load the POST /bin schema, and execute the call with the bin name and attributes. Jentic handles credential and CSRF-token injection so the agent does not need to manage either directly.

Does the API expose audit and error logs?

Yes. The ErrHandlerLog endpoints return error-handler log entries and the LoginLog endpoints expose login history. Use these together with /activity to investigate access or processing problems.

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

Yes. Because you run Jentic One yourself, you decide which EFormBin operations your agent may call, so you can allow only what a task needs, such as GET /bin to list bins and POST /xsd2schema to generate a schema, while withholding everything else. Since these operations identify their target through the request rather than a stable resource id, scoping is done per operation, which means a destructive call like DELETE /delete/* is not available to the agent unless you explicitly add it. Any EFormBin session credential or CSRF token is held by your own instance and injected only when an allowed call runs.

Efbin Eleusoft EfBin.org

Connect the Eleusoft EfBin.org to your agent

Capabilities

Start building with Eleusoft EfBin.org API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs