500 errors when using the API to update or add LTI Tools

[agschmid]

I'm curious if anyone else is seeing this issue. I've filed a ticket, but it would be good to know if others are also running into this problem.

We use environment variables for most of our LTI tools so they don't need to be updated after a beta/test refresh. We have a few tools that use custom variables, though, and these do need to be updated on beta/test.

Lately, when trying to do a PUT to update a tool, I receive a 500 error. When I look under settings -> apps, I will then see two instances of the tool. One will have the beta config while the other has the production config. Doing a GET call, using search for the tool name, only one instance gets returned, though.

Using POST to add a new tool also results in a 500 error. Sometimes the tool displays under settings -> apps, other times it does not.

When I do a PUT or POST, I use the following, which has worked well for the past several years:

"config_type": "by_url",
"config_url": "url_here"

Is anyone else seeing this?

[agschmid]

After some more testing, it seems a PUT is successful if the parameters to update are all in the json body. I will be testing POST with a new tool shortly, but I'm assuming it'll hopefully also work with the parameters in the json body.

Using a url and updating/adding by xml was a lot simpler! Will post if I hear anything back from support why the config_type=url, and config_url are no longer working with the xml files.

[agschmid · Accepted solution]

It seems Box was the culprit. How files can be accessed has changed and I was using links to the XML file to add/update LTI tools. Since Box changed how files can be accessed/downloaded, this no longer works.

[James]

Thanks for coming back to the Community and providing the solution so that other people who might have this problem know the answer.