How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Epignosis (TalentLMS, eFront, TalentCards) Branch API

The Branch API from Epignosis (TalentLMS, eFront, TalentCards) — 5 operation(s) for branch.

Epignosis (TalentLMS, eFront, TalentCards) Branch API is one of 17 APIs that Epignosis (TalentLMS, eFront, TalentCards) publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Branch. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 5 operations across 5 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://virtserver.swaggerhub.com/Epignosis/Efront-API/1.0.0, https://ssc.efrontlearning.com/API/v1.0.

5 operations 5 paths 12 schemas 2 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://samples.talentlms.com/api/v1/
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

Epignosis (TalentLMS, eFront, TalentCards) Branch API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 2 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Branch 5
GET
/Branch/{Id}
Returns information about the branch with the associated Id.
1 param → 200404
GET
/Branches
Returns the branch list.
→ 200400
POST
/Branch
Create branch
body → 200400
POST
/Branch/AddUser
Adds a user to a branch
body → 200400
PUT
/Branch/{Id}/AddUser
Adds a user to the specified branch. - The Id in the URL, refers to the branch. - The Id of the user is defined as a PUT field, in the request body.
1 param body → 200400

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are createBranch (9 properties), standardResponse (3 properties), coursesList (2 properties). Each schema is shown below with its type and property counts.

public_id
string
login
string
The login username
userName
string
timestampNullable
integernull
createBranch
object
9 properties 1 required
nullableId
integernull
email
string
id
integer
The resource id.
coursesList
object
2 properties
surname
string
booleanInteger
integer
standardResponse
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

epignosis-talentlms-efront-talentcards-branch-api-openapi.yml Raw ↑

Other APIs Epignosis (TalentLMS, eFront, TalentCards) publishes across the network.

TalentLMS API
Epignosis (TalentLMS, eFront, TalentCards) Account API
Epignosis (TalentLMS, eFront, TalentCards) Autologin API
Epignosis (TalentLMS, eFront, TalentCards) Catalog API
Epignosis (TalentLMS, eFront, TalentCards) Category API
Epignosis (TalentLMS, eFront, TalentCards) Content API
Epignosis (TalentLMS, eFront, TalentCards) Course API
Epignosis (TalentLMS, eFront, TalentCards) Curriculum API
Epignosis (TalentLMS, eFront, TalentCards) Extended Field API
Epignosis (TalentLMS, eFront, TalentCards) Group API
Epignosis (TalentLMS, eFront, TalentCards) Job API
Epignosis (TalentLMS, eFront, TalentCards) Plugin API
Where this information came from

This is an independent, third-party profile of Epignosis (TalentLMS, eFront, TalentCards) Branch API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.