Technical FAQs
Q. How do I get an API license key?

A. You need to register your application development in our developer portal. To access the portal you will need the API developer credentials. You'll need to provide the following information:
  • Application name (mandatory)
  • Application URL where end users can find information about the application (mandatory)
  • Callback URL where end users will be directed with the OAuth access token and secret after authorization. If the page is dynamic, it can be specified during the process using a parameter.
  • Support URL where end users can find application help and support information
  • Registration URL if you want to provide a custom registration portal for new application users

Q. I can’t access protected resources using the API

A. You must first have a valid account on the NTRglobal Cloud platform and complete the Authorization process to obtain a valid token and secret. The request token and secret values will enable you to obtain an access token and secret. Note that these are not valid for signing HTTP requests later, so be sure to use an access token to access protected resources.

Q. Do I have to complete the authorization process every time I want to access the API?

A. No. Access tokens do not expire, so you can keep them until the end user revokes them. Remember that this information is what identifies and validates the user on our platform, so we recommend you store them in a safe place that others can also access in case you are not available.

Q. When I try to create a new resource, it fails with the error message 422 unprocessableentity

A. Be sure you are using a POST. Then check if the body of the request is correct and no information is missing. Finally, check that you are using specific HTTP headers like Content-type to describe the type of information included in the body.

Q. Should we use HTTPs to call your API?

A. We encourage using SSL for all NTRglobal calls in production environments. For development environments, it’s fine to use standard HTTP, and it will be easier for debugging purposes.

Social Media
twitter linkedin youtube