Banno Admin API Report Exports - banno-digital-toolkit

Within Banno Digital Toolkit Admin API, the reports api seems to only support the retrieval of reports that have been already created. Is there a way to create a report through the Admin API in the same way one can create a report in the Banno.com dashboard (Reports->Create request)? It seems the admin API can only call reports already created and not make new ones on its own. Any clarification on this would be helpful. Thanks
[banno-digital-toolkit]
Currently I have been leveraging the documentation here https://jackhenry.dev/open-api-docs/admin-api/api-reference/v0/reports/exports/
I have been unable to find documentation of and api call that can create reports.

Correct, the Admin API does not offer a way to create a report.
We'll take this feedback to the Product & Engineering teams.

Related

Simple Esri/ArcGIS Online connection using a link or iframe

I was asked by a potential client if I can have my software interact with Esri/ArcGIS Online.
Use case: users is logged into SomeRandomSoftwareApp and is looking at a Widget, this Widget includes an Esri asset id, the user clicks a link that passes that ID to Esri/ArcGIS Online and behind the scenes the user is logged into Esri and they see the data associated with the Esri/ArcGIS Online.
Thanks, Keith
If I understand correctly, you have two options for this: API Keys or Application Credentials.
The first one, is a permanent token generated by the owner of the data that will allow the application easy access to it. This is still in beta, and it was not ready for use the last time I check some time ago.
The second one, the owner of the data will generate credentials for your application. With this credentials you will have to request a token each time you want to access the data, all this via OAuth 2.0.
Check the docs for more details ArcGIS Services - Security

problem : Azure Logic App is not visible in Azure API management

I am facing one issue. I am not able to find logic app in API management application.
I am 10 different workflows with HTTP trigger. Through Postman, they are working fine.
Both apps (logic app and API management app) are under same subscription and resource group. but when I am searching logic app it is not visible.
In API management ->backend, I am able to find it but not sure how to connect back-end with Front end in this approach.
please help
I've had the same and it took me a while to find out that the Logic App also needs to run under a "consumption plan":
https://learn.microsoft.com/en-us/azure/api-management/import-logic-app-as-api#prerequisites
When creating the Logic App you can chose between a Standard or Consuption plan.
Similar problem. I have a Logic App workflow defined as:
And yet this logic app does not show up when I attempt to import it into API Management:
The Logic App and API Management instances are in the same account and resource group.

How do i create api keys for users on my client instead of developer portal offered in azure api management?

I have an enpoint in my MERN app which I would like to expose to developers.
I came across APIM and would like to use it.
After going to the documentation I would like to know how do I can use APIM for my specific enpoint and where I allow users to generate API's in my client side react app.
I am also going through the API management API. but don't know how to generate user specific API keys...
You could simply mimic what the Developer Portal does using APIMs REST API.
If you are using the Consumption Tier of APIM, you can just create a standalone subscription using the Create or Update Subscription API. Yon don't have to set properties.ownerId in the request payload here.
On the other tiers, standalone subscriptions are not supported yet (but will be as mentioned in the official announcement blog under New Features), so you will have to create a user first using the Create or Update User API and then create a new subscription mentioning this user under properties.ownerId as /users/{userId}.
Since these REST APIs call the Azure Management API, you shouldn't be making these requests from the client and instead should be calling this from your backend.

billing clients for google api's

Questions regarding billing for Google API's or more specifically the places and maps Google API's.
We have an app which is part of a SAAS package. When clients use our Software we have maps and place's API built it, however we want to offset the cost of the bill using these API's to that particular client using the software.
Currently we have a single Google Project we created and enabled the API's on our own google account however this means we will foot the bill as its using our token.
Can clients somehow connect to our google project etc or do we simply need them to create their own google project and pass that token through? Is there a streamlined approach that covers this...
When we did for our multi tenant application we did create only one google project and billing was getting accumulated into a single account. We looked at what you're talked about but since google does not allow to bill separately without having separate google project. Google API billing works on google project id. We decided to bill our clients separately and handled all calls to Places API on a single google project.
Long story short - it was not easy to have our clients connect to our project without having them create their own google project we ended up with one google api project.
edit: also missed another important point - Google My Business API needed whitelisting for each project id so it was another reason to keep it as a single project
Passing the token to the application is a probably very bad idea and will result in a security risk for your client and their token if it is intercepted.
As a developer for the client they should create a token on their account and then they will be charged. They can then give it to you as the developer for use. This is however a gray area as technically you are not allowed to share your tokens with anyone TOC However i believe that client and developer relationship should be secure enough for sharing the token.
Ideally you should give the client the code they can then use their own token and run the application themselves.

Google CRUD Migration from SQL API to Fusion Tables API

I used Ferris Argyle's CRUD from the Google Apps Developer Blog and now must migrate this SQL API to Fusion Tables API. The full code is here. So far my efforts have left me with a code 404 error and lots of this:' <HTML><HEAD><TITLE>Not Found.' Ideally this example CRUD would be updated by Google but lacking an update perhaps someone could offer guidance.
What i've updated from the migration guide.
Turned on API, Removed numberic ID's, Updated libraries (None for me), updated URL end point.
added '&alt=csv' to query parameter.
added '&key=MyEncriptedAPIKey'.
I am unsure if OAuth in the CRUD must be updated.
I am unsure of the relationship between API Key and OAuth, do i need both or one.
Can anyone look at the example CRUD and tell me what i'm missing? i'm a novice with Javascripts, Google Apps, OAuth so examples or links are welcome.
thanks,
Scott "if it ain't broken don't fix it" B
Unfortunately Google Apps Script doesn't currently doesn't have native support OAuth2 authentication, which is required to by the new Fusion Tables API to access private data. Some users have had success implementing parts of the OAuth2 flow themselves in Apps Script, but as a novice this may not be feasible. If you are only accessing public data then you should be able to get by just using the API key.