You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[X] Feature request
[ ] Documentation issue or request
[ ] Other... Please describe:
SMAPI client supports the older and very limited Metrics API v1, but it doesn't support the newest and improved Metrics API v2.
Expected Behavior
Support for Metrics API v2
Current Behavior
Missing support for Metrics API v2. Only Metrics API v1 are supported.
Possible Solution
Implement Metrics API v2 support.
Context
We need to fetch Alexa skill's metrics in order to make statistics and analytics charts about it. We are currently limited to one week (Metrics API v1 limit) and it doesn't fit very well our needs. We would really like to have Metrics API v2 support in order to make statistics about periods longer than one week.
Your Environment
ASK SDK for Node.js used: 2.30.4
Operating System and version: Mac OS X
Node.js and NPM Info
Node.js version used for development: 20.5.0
NPM version used for development: 9.8.0
The text was updated successfully, but these errors were encountered:
I'm submitting a...
SMAPI client supports the older and very limited Metrics API v1, but it doesn't support the newest and improved Metrics API v2.
Expected Behavior
Support for Metrics API v2
Current Behavior
Missing support for Metrics API v2. Only Metrics API v1 are supported.
Possible Solution
Implement Metrics API v2 support.
Context
We need to fetch Alexa skill's metrics in order to make statistics and analytics charts about it. We are currently limited to one week (Metrics API v1 limit) and it doesn't fit very well our needs. We would really like to have Metrics API v2 support in order to make statistics about periods longer than one week.
Your Environment
Node.js and NPM Info
The text was updated successfully, but these errors were encountered: