Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Epignosis (TalentLMS, eFront, TalentCards) Curriculum API

The Curriculum API from Epignosis (TalentLMS, eFront, TalentCards) — 3 operation(s) for curriculum.

Epignosis (TalentLMS, eFront, TalentCards) Curriculum 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 Curriculum. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 3 operations across 3 paths, and defines 7 schemas. It is described by OpenAPI 3.0.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.

3 operations 3 paths 7 schemas 1 GET2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.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) Curriculum API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

Paths & Operations 3

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

Curriculum 3
GET
/curriculums
Returns a list of the available curriculums.
→ 200400
PUT
/Curriculum/{Id}/AddUser
Adds a user to the specified curriculum. - The Id in the URL, refers to the curriculum. - The Id of the user is defined as a PUT field, in the request body.
1 param body → 200400
PUT
/Curriculum/{Id}/RemoveUser
Removes a user from the specified curriculum. - The Id in the URL, refers to the curriculum. - The Id of the user is defined as a PUT field, in the request body.
1 param body → 200400

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed is standardResponse (3 properties). Each schema is shown below with its type and property counts.

id
integer
The resource id.
price
number
nullableId
integer
standardResponse
object
3 properties
booleanInteger
integer
timestampNullable
integer
public_id
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

epignosis-talentlms-efront-talentcards-curriculum-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) Branch 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) Extended Field API
Epignosis (TalentLMS, eFront, TalentCards) Group API
Epignosis (TalentLMS, eFront, TalentCards) Job API
Epignosis (TalentLMS, eFront, TalentCards) Plugin API