We're trying to get information from the RDC endpoints but we seem to only be receiving a 500 error. This is the case for all of the RDC endpoints. Below is an example URL;
https://banno.com/a/mobile/api/v0/institutions/xxxxx/users/xxxxxxxxxxxx/rdcAccounts
Below is the documentation I'm following when sending the request:
https://jackhenry.dev/open-api-docs/admin-api/api-reference/v0/rdc/details/
I can authenticate and hit basically any other endpoints, it's just this RDC endpoint that seems to be giving us trouble. Is there a reason I'm getting a 500 back on these requests, even though I should be getting some data back?
I had sent a message to JHA support on this, and they responded back saying "JHA does not support automation for RDC". So now I'm a little confused - do these RDC endpoints do anything?
Hoping someone here can shed some light.
Thanks!
#bzbz the Engineering team has deployed a fix and this should be working.
Related
We are occasionally seeing an issue with some projects where, when we try to do a GetPublishJob on a BIM360 model, we get back a 403 error, like this:
{"jsonapi":{"version":"1.0"},"errors":[{"id":"ad23cbc6-dc82-4dfd-83f9-6acd14bac6d2","status":"403","code":"C4R","detail":"Failed to get publish model job"}]}
In the docs, it says it could be whitelisting or permissions. We know our app is whitelisted, because we would not have made it this far if it wasn't. We're using 3-legged OAuth, and we believe that the user is able to manually perform the Publish. Can you tell us what specific other permissions might need to be investigated?
I am not typing answer, while I want to check some information with you:
if what you are using is this endpoint, it is public, so it does not need whitelisted. https://forge.autodesk.com/en/docs/data/v2/reference/http/GetPublishModelJob/ .
Since you are using 3 legged token, I doubt it may due to the expired token, while normally it should be 401 error.
With the same token, can your code perform Publish Model?
https://forge.autodesk.com/en/docs/data/v2/reference/http/PublishModel/
was this workflow working well in the past? or just failed recently?
To use this endpoint, the logged user (for 3 legged token) should have access with the folder.
When trying to getting response from https://developer.api.autodesk.com/bim360/admin/v1/projects/:projectId/activities it rises 403 error with details - Route not enabled for account. But, for example, request https://developer.api.autodesk.com/bim360/admin/v1/projects/:projectId/users has successfully responsed. User has all admin permissions.
Can every one help with that? :) Are there another ways to get project activities?
Unfortunately, activity API is not released yet, so you cannot use it currently. Please stay tuned with our official announcement in the further. Apologies for the inconvenience!
I recently got access to the Amazon Product API, and I was trying to experiment with some requests both on my Node.JS environment and on ScratchPad.
But all my requests come back as Error 429 - Too many requests. So far, I haven't been able to make any successful requests using the API.
Has anyone had this issue before? How can I solve this?
I had this error message when trying to access the API via the python SDK. I figured out that besides acces_key, secret_key, and partner_tag I needed to set host, region, and marketplace to the country-specific values according to https://webservices.amazon.com/paapi5/documentation/common-request-parameters.html#host-and-region.
While this seems obvious in retrospective, the error message 429 "too many requests" does not really hint to fix that.
We've got an Autodesk Forge application that uses an initial 3-legged OAuth to get a token, and then keeps refreshing it as needed to get things done.
We're running into occasions where we get back a GATEWAY TIMEOUT error from the RefreshToken call.
We do retry up to 3 times after encountering it - but it seems like we immediately get BAD REQUESTs.
We feel like the Refresh is actually happening (so a new refresh token is generated) - but because of the Gateway Timeout, we're not getting the new refresh token back.
I feel like the Gateway timeout is being reported in Autodesk's API wrapper service (Apogee?) - so there's nothing I can control about it - is that correct? Any recommendations for what to do?
Thanks,
Matt
I'm using the v1 version of the API. When I make a call to get_group_users, I'm getting a 500 internal server error response back. It has been working in the past - is this a new issue?
Incidentally, returning this page for an API call breaks XML formatting (we noticed this from an error message "string "--" is not permitted within comments" when trying to parse the response body.
We also had the same issue suddenly with the API V1. When we investigated the issue with the API team it was for us to do with the size of the result.
There was no solution for us but to move to the API V2 which by default pages results and hence caps the issue.
However as you are aware Groups are not get exposed in the new API but I understand they are coming and just in the backlog along with the other missing features that can be found in API V1.
I am sure one of the API developers reading this can give some advice on an ETA for Groups reaching GA in API V2