v13.66.1
16 days ago by Evangelos Kerasidis
✏️ Modifications | 📄 Documentation Updates
✏️ Modifications
- GET /insights/year/{year}/month/{month}
- Updated error codes to align with the weekly endpoint.
- Upon the unavailability of report, the error 195 is thrown, while previously the endpoint would return a successful response with empty body.
- GET /insights/year/{year}/week/{week}
- Potential error codes have been reduced and made more meaningful. Namely the following error codes have been removed:
- 118:
Issue with AWS connection.
- 118:
Issue with AWS connection.
- 120:
Issue with analytics integration service.
- 153:
No valid meter found for user.
- 191:
Document error.
- 265:
Unexpected exception while retrieving customer information.
- 400:
User not provisioned.
- 422:
Invalid input: year is not correct/month is not correct, must be between 0 and 12.
- 118:
- And the following ones have been introduced:
122
,156
,424
.- 122:
Corrupted report.
- 156:
User or meter validation failed.
- 424:
Invalid input: year is not correct/week is not correct.
- 122:
- Potential error codes have been reduced and made more meaningful. Namely the following error codes have been removed:
📄 Documentation Updates
- GET /recommendations/monthly
API documentation has been updated to include the description of the following timestamp attributes, which were previously omitted:- timestamp (part of data object)
Timestamp of the recommendation creation in ISO 8601 format.
- timestamp (outside of data object)
Timestamp of the API response returned by the platform, in ISO 8601 format.
- timestamp (part of data object)