Client ID Type and Redirect URIs

[Lee Savidge]

I'm trying to set up a new application in the app registry. I'm trying to add a URI for the redirect which will be a localhost address served over HTTPS - https://localhost:48488. The documentation states this:

"

1. Enter a Redirect URI as a full https URL. During the authorization process, users will be redirected to this URL after authorizing your application to access their data in Sage Intacct. Your application needs to have a script or code at this URL that is ready to receive an OAuth authorization code and use it to request a token. You can provide multiple URLs as a comma-separated list.

"

There will be a script at this URL. Is there any reason why I can't populate it in this field? It just says there is an error.

The second problem I have is the Client ID Type. It seems all I can do is make calls to non-production companies. I thought the REST API was now fully available or did I misunderstand the release notes when it said the REST API is now available with 2024 R2?

Edited May 20 by Lee Savidge
Add more data

[Lee Savidge]

It seems the input box for the redirect URI is happy if there is at least some character followed by a dot and then another character so I could put in https://x.x which passes the test, but https://localhost fails. However, I can put in https://127.0.0.1 but I can't add a port. Why not? Why can't Intacct handle applications held on a different port? It's bad enough that trigggers and smart events can only send to HTTP port 80 or HTTPS port 443, but why restrict this?

[Lee Savidge]

What triggers replies to be forced for approval? If I knew I'd avoid writing posts that trigger it

Edited May 20 by Lee Savidge

[Lee Savidge]

Actually I don't even think my approach would work. It has worked on a different system that used authorisation codes and access tokens but the client side was ultimately installed on a desktop and my module lauched the browser to do the log in to get the auth code.

I don't see any way to use the REST API with smart event and triggers that do HTTP POSTs because there is no way to get the authorisation code in the first place unless it is done outside the system via Postman or something equivalent and the auth code copied across manually to get the access token. That's not a usable solution. For this API to be usable and, ultimately, useful, it needs to be seamless and it must be possible to initiate and manage to authorisation process and token creation purely by the end user. If that can't be done, I might as well go back to the XML gateway which does allow that.

 

[Sterio, Louis]

On 5/20/2024 at 8:29 AM, Lee Savidge said:

I'm trying to set up a new application in the app registry. I'm trying to add a URI for the redirect which will be a localhost address served over HTTPS - https://localhost:48488. The documentation states this:

"

1. Enter a Redirect URI as a full https URL. During the authorization process, users will be redirected to this URL after authorizing your application to access their data in Sage Intacct. Your application needs to have a script or code at this URL that is ready to receive an OAuth authorization code and use it to request a token. You can provide multiple URLs as a comma-separated list.

"

There will be a script at this URL. Is there any reason why I can't populate it in this field? It just says there is an error.

The second problem I have is the Client ID Type. It seems all I can do is make calls to non-production companies. I thought the REST API was now fully available or did I misunderstand the release notes when it said the REST API is now available with 2024 R2?

I will run this feedback by our team for your first point.

For your second issue:

The REST API is in beta mode, while it is available for everyone to test and provide feedback. It is not GA ready and we're only allowing open beta users to interface with non-production companies only. This is documented in the FAQ:

https://developer.sage.com/intacct/docs/developer-portal/guides/rest-api-faq/

[Sterio, Louis]

On 5/20/2024 at 8:40 AM, Lee Savidge said:

What triggers replies to be forced for approval? If I knew I'd avoid writing posts that trigger it

I am also investigating this sporadic approval issue on forum posts. I will try to turn that off, if not I will get the logic so we can avoid it.

[Sterio, Louis]

6 hours ago, Lee Savidge said:

Actually I don't even think my approach would work. It has worked on a different system that used authorisation codes and access tokens but the client side was ultimately installed on a desktop and my module lauched the browser to do the log in to get the auth code.

I don't see any way to use the REST API with smart event and triggers that do HTTP POSTs because there is no way to get the authorisation code in the first place unless it is done outside the system via Postman or something equivalent and the auth code copied across manually to get the access token. That's not a usable solution. For this API to be usable and, ultimately, useful, it needs to be seamless and it must be possible to initiate and manage to authorisation process and token creation purely by the end user. If that can't be done, I might as well go back to the XML gateway which does allow that.

 

Lee I would love to unpack this use case more with you. Maybe even get a demo of how one of your existing applications operate today.

I will setup a call that is convenient to your time-zone to review.