Troubleshoot
I need to debug my cURL app
Use the cURL debugging options, such as:
- "-v" for verbose output,
- the built-in trace options for detailed tracing of API calls.
I can't authenticate to make API calls
Read through the options below to see what you can do when you can't authenticate to make API calls.
If you don't have the Client ID and Secret: Reach out to your system administrator to get that information. Typically, the system administrator should give you that information. You have to store the client ID and Secret somewhere safe, so you can use them to authenticate later.
If you have the Client ID and Secret: Follow these steps to make sure you're all set to authenticate:
- Reach out to your delegated administrator to make sure you're provisioned in Oracle Life IAMS with the umtscim.call role.
- Check with your system administrator that the Client ID and Secret they provided are correct.
- Check with the Oracle InForm User Management Tool global user manager to make sure you're using the correct study name in Oracle InForm User Management Tool.
- Double-check that your cURL is set up the right way. For more details, see Install and configure cURL.
If none of the above options work for you: Go to Life Sciences Cloud Support and expand the entry for Oracle InForm User Management Tool. You can open a support request on Oracle InForm User Management Tool Support Cloud or call us for urgent issues.
The data I got back after an API call isn't what I need
If the data you got back in the Response section isn't what you need, then you might have called the wrong version of an API. In general, we recommend that you use the latest version of an API request to make sure you get the best and most accurate data from the study in your system.
Moreover, make sure you are using the correct query parameters, as specified in the REST API Guide for every API request. If you use an invalid query parameter, the system does not notify you of any errors. Instead, it may generate an incorrect or unexpected output.