Support

Contact

platform@claytonpower.com

Before you write

Most questions are answered by one of these:

• Authentication and scopes - 401 and 403.
• Concepts - why a number looks stale, zero or missing.
• Errors and rate limits - what a status code means and whether to retry.
• API reference - the exact shape of a request or response.

Two things account for most reports:

• The data looks 15 to 30 minutes behind. That is expected for the energy figures. See Freshness and lag.
• Every energy value is zero. The system may not carry the cumulative energy meters those figures come from. See Product families.

What to include

For a problem with a specific request, include:

• The correlationId from the error response. It identifies the exact call in our logs and is by far the most useful thing you can send.
• The full request: method, path and query parameters.
• The response: status code and body.
• The UTC time of the request.
• The first 12 characters of the API key (for example cp_live_Ab3x), which identifies the key.

Never send us a full API key or a webhook secret. If you have sent one anywhere by accident, revoke or rotate it first and tell us afterwards.

For a webhook problem, include the subscription id and what GET /webhooks/{id}/deliveries shows - lastResponseCode and lastError usually identify the cause on their own.

Reporting a security issue

Do not report security issues by ordinary support mail and do not include details in a public forum. Follow the coordinated disclosure process at cra.claytonpower.com.

Requesting changes

New endpoints, new fields and higher rate limits are all reasonable requests. Tell us what you are building and what is missing; that is more useful than a proposed endpoint design.