2 Requirements and Limitations

The following data requirements and limitations apply to all utilities using the GraphQL APIs.

Utility Data Requirements and Limitations

The following data requirements and limitations apply to all utilities using the GraphQL APIs.

  • Data Integration: You must complete data integration to use Oracle Utilities Opower data and insights with Opower Integration Hub. Data must be sent to Oracle Utilities in the right schema and according to the established data specifications. Your Oracle Utilities Delivery Team will work with you to identify which data specifications are applicable to your situation.
    • AMI Insights: AMI insights are available if AMI data is provided to Oracle Utilities in the required format. For more information, refer to the Oracle Utilities Opower Data Transfer Standards.
    • Rates: Utility rates must be modeled by Oracle Utilities for rates data and insights to be available. For more information on the Rates Engagement Cloud Service, refer to the Rates Engagement topic of the Oracle Utilities Opower Digital Self Service - Energy Management Cloud Services Overview.
  • Authentication: A utility must configure their instance of Oracle Identity and Access Management to allow for authentication and single sign-on (SSO) integration. This includes enabling the use of OpenID Connect Authorization Code Flow. Information on implementing Authorization Code Flow with Oracle Identity and Access Management and request examples can be found in the Identity and Access Management documentation.
  • GraphQL Introspection and Query Testing: Reviewing the GraphQL schema and building queries can be accomplished on a test instance that provides access to a GraphQL IDE. General access and schema introspection is available to all users. Third-party partners must submit a service request through My Oracle Support for access to execute queries from this testing location. Oracle Utilities responds to these service requests by providing applicable account information, credentials, and access tokens for this test environment. Be aware that access tokens expire and no longer provide query execution access 60 minutes after their creation.
  • API Rate Limiting: The GraphQL API endpoint is limited to 175 queries per second and 250,000 API calls per day for each application instance.
  • Data Querying and Availability: Be aware of the following data querying and availability details.
    • Billing Data:
      • Billing data can be returned for up to 25 bills in a single request.
      • Data is available for the last two years preceding the time of the API request.
      • If the active utility account is associated with multiple service points of the same fuel type, billed usage per service point is returned.
    • Interval Usage:
      • Daily data can be returned for up to 45 days in a single request.
      • Days are defined from midnight to midnight in the local timezone of the site or service point.
      • If the active utility account is associated with multiple service points of the same fuel type, usage data per service point is returned.