content API


Content API lists the course and curriculum of users who are registered with the company. Based on the parameters entered in the Content URL, the security token is authenticated and throws progress details of all basic course and curriculum for each user. It also showcases achievement details available in the Linchpin application.


Security token and origination url, should be sent as response headers for authentication

  • Once the Linchpin app is purchased, an interface will be provided to generate the security token which will be unique for a company.
  • Content API is authenticated based on the company token and external URL from where the request is sent.


The URL structure (path only, no root url)
api/v1/Content or / Content? filters={”minrange”:”1”,“maxrange”:”10”,”active”:”true”}


The request type

URL Params


Input parameter class structure

public class Filters
public int MinRange { get; set; } -- starting row number
public int MaxRange { get; set; } -- ending row number
public bool Active { get; set; } – Active/Inactive profiles

Input parameter Validation rules

Minimum value expected for MinRange is 1, Max Value should be greater than or equal to MinRange. Active parameter expects either true or false.

Response Codes

Output Response Object

public class ProfileDto { public int UserId { get; set; } public string Name { get; set; } public string Email { get; set; } public DateTime? Dob { get; set; } public string Gender { get; set; } public string Phone { get; set; } public string Profileimage { get; set; } public int Credits { get; set; } public int UserLevel { get; set; } public int NextLevelCredits { get; set; } public string Language { get; set; } public DateTime? CreatedDate { get; set; } public int Rank { get; set; } public string Usage { get; set; } public string Engagement { get; set; } public float EngagementPercentage { get; set; } public List Content { get; set; } } public class Contents { public string Status { get; set; } public int Count { get; set; } }

Success Response

Successful request: { “status”:200, “profile”:[{ "UserId":"UserId", "Name":"Name", "Email":"", "Phone":"+11234567890", "Profileimage":"Profileimage", "Credits":"Credits", "UserLevel":"UserLevel", "NextLevelCredits":"NextLevelCredits", "Rank":"Rank", "Usage":"Usage", "Engagement":"Engagement", "EngagementPercentage":"EngagementPercentage" "Contents":[{ "Status":"Status", "Count":"Count" }, { "Status":"Status", "Count":"Count" }] }] }

HTTP Status Codes

Most endpoints will have many ways they can fail. From unauthorized access, to wrongful parameters etc. Example: Code: 200 OK Description: { Success } Code: 401 UNAUTHORIZED Description: {error: "Authentication credentials were missing or incorrect.”} Code: 400 Bad Request Description: { error : "The request was invalid or cannot be otherwise served" } Code: 404 Not Found Description: { error : "Content details not found" }