Can anyone tell me, when I create the analytics account, in Property Settings, Default URL, should I be using our DNS name (vanity URL) or our <DOMAIN>.instructure.com address?  Support told me "the vanity would be preferred actually as it appears all of the bulk of requests are going to be made through there". The instructions above say to use to use our Canvas url in the website url field (eg: https://example.instructure.com) ... View more

Hi Jeff, I would have never thought to look at tabs. It worked like a charm. Note that under the PUT call to update a tab for course there is a note that says "The Home and Settings tabs are not manageable, and can't be hidden or moved". I found this to be true for Announcements (position 2) as well. Thank you ... View more

Hi. Does anyone know if there is there a property that will set the order of the menu item in course nav? ... View more

Lindy, If you're using Linux, don't bother with PowerShell. Install CanvasDataCLI from GitHub - instructure/canvas-data-cli: Command line tool to connect and download files from Canvas Data and use cron to fetch your data. The README explains the dependencies, how to install and how to use it. Cheers ... View more

I'm joining the conversation as we will be working on this very soon. ... View more

Tyler, How do you connect with Postman? ... View more

Hi Tyler, That great info. Is there any chance I could see an example of your API call to enable_sis_reactivation for a user? Thank you. ... View more

Hello, I use Perl and Canvas APIs to do all my SIS work. Here are some examples: Create a course: /usr/bin/curl -s 'https://$DOMAIN.instructure.com/api/v1/accounts/$account_id/courses' -X POST -H '$AUTH_HEADER' -F 'course[name]=$course_name' -F 'course[course_code]=$course_code' -F 'course[sis_course_id]=$course_id' -F 'course[term_id]=$term_id' Create the course section: /usr/bin/curl -s 'https://$DOMAIN.instructure.com/api/v1/courses/$canvas_course_id/sections' -X POST -H '$AUTH_HEADER' -F 'course_section[name]=$course_name' -F 'course_section[sis_section_id]=$section_id Apply a template: /usr/bin/curl -s 'https://$DOMAIN.instructure.com/api/v1/courses/$canvas_course_id/content_migrations' -X POST -H '$AUTH_HEADER' -F 'migration_type=course_copy_importer' -F 'settings[source_course_id]=$template_number' Enroll user: /usr/bin/curl -s 'https://$DOMAIN.instructure.com/api/v1/courses/$canvas_course_id/enrollments' -X POST -H '$AUTH_HEADER' -F 'enrollment[user_id]=$canvas_user_id' -F 'enrollment[type]=$role' -F 'enrollment[course_section_id]=$course_section_id' -F 'enrollment[enrollment_state]=active' The enrollment and template calls are dependent on getting the the canvas_course_id and the canvas_section_id respectively. To do that, I stuff the json message returned from each call into a variable called $messages. From here I can located the "id" and store it in a variable. This is the code: my $char = "id\":"; my $begin = index($messages,$char);       $begin+=4; my $end = 10; my $canvas_course_id = substr($messages,$begin,$end);    $canvas_course_id =~ s/\D+//g; I do the same to get the canvas_section _id so I can enroll my users. ... View more

Here's my idea: ... View more

Will do Stefanie ... View more

I'm going to submit a idea to add a parameter to the API call. Thank you all for your input.  ... View more

Please add me to the Canvas Hacks class. tom.lamy@unh.edu. Thanks ... View more