See if product is eligible for free international shipping via the PAAPI - amazon-product-api

Is there a resource or variation that I could add to a PAAPI (Product Advertising API) request to filter/sort for items that are eligible to ship free internationally: https://www.amazon.com/gp/help/customer/display.html?nodeId=GY48Z9B62JLTAQV2
Such as here, if there could be an additional DeliveryFlag for Free Global/International Shipping: https://webservices.amazon.com/paapi5/documentation/search-items.html#deliveryflags-parameter

Related

Unable to determine type of account from banno consumer api

When my plugin retrieves data from the banno consumer api, Credit Cards, Mortgages, and Investment accounts are all coming through with an account type and subtype that look like this
type: "Third Party"
subtype: "Other"
My plugin needs to be able to determine the difference between these types of accounts, however the Banno consumer api does not define Credit Card or Mortgage as an account type. Furthermore, the documentation states that the subtype field should not be used.
Does the banno consumer api provide any way to accurately determine the type of Credit Card, Mortgage, Investment, or any of these "Third Party" accounts?
The accountType of "Other" is a result of the way that an account is configured within the underlying core (and there are 4 cores that Jack Henry supports..3 for banks and 1 for credit unions).
There often isn't much information available within the core itself about the account, which is how you end up with an accountType of "Other" and accountSubType of "Third Party".
There are credit cards represented (with accountType of "Line of Credit" and accountSubType of "Credit Card"), depending upon the configuration.
Mortgages generally aren't represented directly via accountType and accountSubType and the best that is known from the core is that the account is some type of "Loan".

How to select a Medical Research use case

On the page https://developers.google.com/fit/policy?hl=en#appropriate_access_to_and_use_of_google_fit_apis it says the following:
Do not use Google Fit APIs for applications, services, or features designed to collect or combine user data for human subjects research, medical research, or any other similar research overseen by an Institutional Research Board or Ethics Commission unless you receive prior written approval to such use from Google. Select a "Medical Research" use case during the scope access request process and you will receive additional information on how to proceed.
I'd like to use the Google Fit API for a medical research purpose, but I cannot find where I'd select the "Medical Research" use case. Can anyone show me where I can find this?
I'd be using the Google Fit API to start tracking steps on the user's Android device and read these steps.
Scope = Purpose of your medical research and used API scopes
I think it is rather misleading, in fact when Google documentation talks about medical research scope, they do not mean it at the API level.
What they mean is that you have to state in your app registration application that you would be using your app for a "medical research purpose", along with the fit API scopes that you would be using for your medical research.
You can read the following link that describes the authorization process intended by Google, but I will will detail below how to proceed:
Enable Fitness API and create credentials
After enabling Fitness API in your Google API Console for your project (create a new one if you haven't already) then you have to apply for verification and submit the relevant supporting information for why your app needs "Medical Research" scope (basically documents related to the purpose of your medical research, which University or Lab you are working for etc). This choice happens right after adding credentials to your project when you have to set up OAuth consent screen:
Filling the app registration form
Filling accurately will speed up the verification process
On the first tab, you will likely have to provide a very solid application privacy policy link (stating which data you access and for which purpose):
Select your API scopes
Then you will have to add the scopes (scopes as API) that you would need for the purpose of your medical research:
The one you will need to read the steps is:
scopes your app needs to request.
https://www.googleapis.com/auth/fitness.location.read | Read location data from the Google Fit platform. | Restricted
Enter your Medical Research "Scope"
Finally, and this is where you provide all information related to your medical research, in the optional info - meaning optional for most users, but not so optional for medical research - already briefly stated in your privacy policy link: Its purpose, how it is financed, by which entity, what data your will be using etc. Be as clear as possible as it will speed up the review process.
Provide links about your university or company website, research papers that you have already published, or by yours peers related to the scope of your medical research:

In Azure API Management How are product level policies resolved for APIs when subscriptions are not required?

I have the following setup in Azure API Management:
Two products: Internal and Starter.
One api: Finance, that is included in both the above products. The Finance api also has the Subscription required checkbox cleared, so a subscription is not required.
The Internal product has a policy that does JWT validation. The Starter product does not.
In the test tab of APIs, I can choose a product scope via the Apply Product Scope dropdown. Presumably this decides which product policies are applied.
When calling the API, if I don't supply a valid token, the JWT validation kicks in and rejects my request. However, since I have no subscription key to identify the product, it could be either the Internal or Starter product - how does the system determine it should apply the Internal policy containing the jwt-validation rule rather than the Starter policy which doesn't?
When request comes in, first API and operation are identified. Then APIM tries to identify subscription. If product subscription key is provided, it's used to identify product and it's policies are executed. If API subscription key is provided, it's checked to match identified API and no product policies would be executed at all.
If no subscription key is present in request, APIM checks if there is a product with Subscription required set to false, and if such product includes identified API. If there is such match, product will be used and it's policies executed. If no such match found, APIM will check if API has Subscription required set to false, and if so then call will proceed without product.
The Test tab uses a special key - master key, among other things this key allows you to force a certain product to be used for a call even if API is not included into one. This is mostly useful for testing purposes, and master key should not really be used in production.
The answer is that the Starter product, whilst testable in the API screens, was marked as "Requires Subscription" at the product level, which overrides the API level setting. Because of this it was not an eligible policy.
Trying to change this setting fails with the error Product cannot be made open since it has APIs that are already part of an open product. which makes sense and removes any ambiguity.

UPS API integration- multiple accounts

I'm trying to integrate with UPS API, but would like to integrate with different UPS accounts based on various different rules that span over multiple portals.
Below mentioned are some of the access information to post ship-confirm-request
<AccessRequest xml:lang="en-US">
<AccessLicenseNumber>132</AccessLicenseNumber>
<UserId>XXX</UserId>
<Password>XXX</Password>
</AccessRequest>
<Shipper>
<ShipperNumber>xxx</ShipperNumber>
</Shipper>
Reading the UPS documentation, i see that
Shipper's six digit account number. Must be associated with the UserId specified in the AccessRequest XML
My Question
To integrate with multiple accounts do i have to request for Shipper account number and info (below), for every single UPS account we have to integrate with?
<AccessRequest xml:lang="en-US">
<AccessLicenseNumber>132</AccessLicenseNumber>
<UserId>XXX</UserId>
<Password>XXX</Password>
</AccessRequest>
Or is there an easier way to do this?
I spoke to the tech support at UPS,
There are two ways to handle multiple accounts.
Create access info at "https://www.ups.com/upsdeveloperkit/" for all accounts. (tedious)
Create access-keys at https://www.ups.com/upsdeveloperkit/ Then
add all your related accounts to this account and you should be able
to use the same info below and just vary your shipper account number.
<AccessRequest xml:lang="en-US">
<AccessLicenseNumber>132</AccessLicenseNumber>
<UserId>XXX</UserId>
<Password>XXX</Password>
</AccessRequest>
You have to request different times for the information. It is quite quick with 4 steps involved (see the guide to request UPS API credentials)

Delivery place by client relationship

I have this test schema:
A client can have multiple addresses and multiple contacts
For example, a secretary (contact) will receive a product purchased by the company (client) she works for.
So, the delivery needs a contact, an address and also needs to be bounded to a client. What's the best way to a Delivery know where and whom to deliver its produtcs?
If I attach Delivery to Address and Contact, I'll have 2 Client id's.