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.

Quickstart

Get started with Eleusoft EfBin.org in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a bin in EFormBin"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

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

Pull error-handler logs, login logs, and grabbed-URL records for audit and diagnostics

GET STARTED

Start building with Eleusoft EfBin.org API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Eleusoft EfBin.org, keeping it validated and agent-ready.

Eleusoft EfBin.org is the API surface for the EFormBin platform — a server for storing, querying, and transforming structured form data, schemas, and binary attachments organised into bins. The 177-endpoint surface covers bin and bin-attribute management, bin instances, profiles, roles, users, OAuth app users, login and error logs, bookmarks, CSRF tokens, schema-from-form generation (form2schema, xsd2schema), and a Swagger admin surface. Most calls require the user to be authorised through the platform's session-based mechanism.

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 though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Any session credentials or CSRF tokens used against EFormBin are stored encrypted in the Jentic vault (MAXsystem). Jentic injects them at execution time, so the raw secrets never enter the agent's context.

Intent-based discovery

Agents search Jentic by intent — 'create a bin', 'generate a schema from XSD', 'list error handler logs' — and Jentic returns the matching EFormBin operation with its input schema, narrowing 177 endpoints to the right one for the task.

Time to first call

Direct integration: 5-10 days to model bins, attributes, users, and the form/XSD converters across 177 endpoints. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Typeform API

Typeform is a hosted form builder and response store with a much narrower, modern API surface.

Choose Typeform when you need a hosted form-and-response service rather than self-hosted bin storage with admin-grade APIs.

Alternative

JotForm API

JotForm offers hosted form creation, submission storage, and reporting in a SaaS model.

Pick JotForm for SaaS form management; pick EFormBin for self-hosted, schema-driven bin storage.

Complementary

Auth0 API

Auth0 manages identity for systems that consume an EFormBin deployment as a downstream form store.

Pair with EFormBin when the client application needs modern OAuth/OIDC identity in front of EFormBin's session-based access.

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.