Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

TalentLMS API

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    TalentLMS API

    I've had a quick look at the TalentLMS API and their doc and, as usual, if they put a tiny bit more effort into actually testing it they'd find that it's wrong.

    I say as usual because most APIs and their docs seem to be very fancy with lots of automated ways to get various types of code but it seems no one is testing the code output.

    In this case TalentLMS wants you to use Postman to generate code for calls and testing. Really excellent process and once again, very fancy, but it is simply wrong in what it does. Amazing that no one has tested this stuff. They went to all the trouble to document it and it looks beautiful... but it doesn't work.

    So, setup your TalentLMS account and install Postman under Chrome. It's all documented really well... and you can be testing TalentLMS calls in Postman within 30 minutes. They won't work, but you can see how it all goes together.

    Once you've got Postman working and a basic test call to get, for example, users, you can generate cURL code... which turns out to be this...

    Code:
    curl -X GET -H "Authorization: Basic ZGlnaXRhbGFkanVzdGVyOkFhcm9uZGs=" -H "Cache-Control: no-cache" -H "Postman-Token: f30ce9d0-3708-4809-bc91-dfa9120e819d" "https://your_talentlms_username.talentlms.com/api/v1/users"
    I have no idea what "ZGlnaXRhbGFkanVzdGVyOkFhcm9uZGs=" is. It's supposed to be your TalentLMS API key... but it isn't. Replacing it with your actual api key doesn't work and results in an error about using your API key as a username and an empty password.

    Alpha has a cURL to XBasic Genie that provides the XBasic code and it works great. The cURL code is wrong from Postman, but that's nothing to do with XBasic.

    The cURL code converts the "Authorization" header line to this...

    dim slist1[0] as c = [ "Authorization: Basic ZGlnaXRhbGFkanVzdGVyOkFhcm9uZGs=" , "Cache-Control: no-cache" , "Postman-Token: f30ce9d0-3708-4809-bc91-dfa9120e819d" ]

    But... as far as I can see, it's wrong. Not XBasic wrong... Postman cURL wrong. The right code... or at least... the code that works is below.

    Take note to replace the TalentLMS username and apikey as indicated below.
    I've added code to create a new Postman-Token for each call.

    Set this code up as an Ajax Callback and run under the LivePreview tab to walk through the code. Examine the contents var and you'll see a list of user data returned.


    Code:
    function talentLMS as c (e as p)
    	
    debug(1)
    
    dim talentLMS_Token as c
    talentLMS_Token = api_uuidcreate()	
    
    dim cf_1 as extension::CurlFile
    dim flag_1 as l
    dim slist1[0] as c = [ "Cache-Control: no-cache" , "Postman-Token: " + talentLMS_Token ]
    dim ce as extension::Curl
    
    ce = extension::Curl.Init()
    ce.setOpt("URL","https://your_talentlms_username.talentlms.com/api/v1/users")
    ce.setOpt("NOPROGRESS",1)
    ce.setOpt("USERAGENT","curl/7.34.0")
    ce.setOpt("USERPWD","your TalentLMS api key here")
    ce.setOpt("HTTPHEADER",slist1)
    ce.setOpt("MAXREDIRS",50)
    ce.setOpt("CAINFO",a5.Get_Exe_Path()+"\caroot\ca-cert.pem")
    ce.setOpt("CAPATH",a5.Get_Exe_Path()+"\caroot")
    ce.setOpt("CUSTOMREQUEST","GET")
    ce.setOpt("TCP_KEEPALIVE",1)
    ce.SetOpt("FILE",cf_1)		
    flag_1 = ce.Exec()
    if flag_1 then
         
        dim headers as c
    	dim contents as c
    	headers = cf_1.GetHeaders()
    	contents = cf_1.GetContent()
    		
    	'BE SURE TO COMMENT OUT THIS CODE IN A WEB APPLICATION AS showVar() CANNOT BE USED IN WEB APPLICATIONS
    	'dim msg as c 
    	'msg = "Headers: " + crlf() + headers + crlf() + "Content: " + contents
    	'showvar( msg)
    	
    	
    else 
    	dim errors as c 
    	errors = ce.error()
    
    	'BE SURE TO COMMENT OUT THIS CODE IN A WEB APPLICATION AS showVar() CANNOT BE USED IN WEB APPLICATIONS
    	showvar("error: " + errors)
    end if
    ce.close()
    
    end function

    #2
    Re: TalentLMS API

    Good day davidk,

    Thanks for your message, I fixed already with curl in Xbasic


    dim cf_1 as extension::CurlFile
    dim flag_1 as l
    dim ce as extension::Curl

    ce = extension::Curl.Init()
    ce.setOpt("URL",TlntDomain)
    ce.setOpt("NOPROGRESS",1)
    ce.setOpt("USERAGENT","curl/7.34.0")
    ce.SetOpt("HTTPGET",1)
    ce.SetOpt("POSTFIELDS",TlntParams)
    ce.SetOpt("USERPWD",TLMS_APIKEY)
    ce.setOpt("MAXREDIRS",50)
    ce.setOpt("CAINFO",a5.Get_Exe_Path()+"\caroot\ca-cert.pem")
    ce.setOpt("CAPATH",a5.Get_Exe_Path()+"\caroot")
    ce.setOpt("TCP_KEEPALIVE",1)
    ce.SetOpt("FILE",cf_1)
    flag_1 = ce.Exec()
    dim contents as c
    if flag_1 then
    dim headers as c

    headers = cf_1.GetHeaders()
    contents = cf_1.GetContent()
    else
    dim errors as c
    contents = ce.error()
    contents = "Error"
    end if
    ce.close()

    Comment

    Working...
    X