Connect a plant via inverter cloud

01Create the project

curl -X POST https://sandbox.api.arkreen.com/v1/projects \
  -H "Authorization: Bearer $TOKEN" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "name": "Rooftop — Chonburi Industrial Park",
    "asset_class": "solar_pv",
    "country": "TH",
    "installed_capacity_w": 300000,
    "commercial_operation_date": "2025-01-15"
  }'

Returns a project in status draft. Drafts are private to your organization and cost nothing to create — make one per site rather than trying to model a portfolio as a single project.

02Find your connector

curl "https://sandbox.api.arkreen.com/v1/connectors?country=TH" -H "Authorization: Bearer $TOKEN"

If your manufacturer is not listed, you have two options: push directly (the edge gateway guide covers the L2 path), or ask the manufacturer to publish a connector.

03Authorize

curl -X POST https://sandbox.api.arkreen.com/v1/connectors/sungrow/authorize \
  -H "Authorization: Bearer $TOKEN" \
  -d '{ "project_id": "prj_8fK2mQ", "redirect_uri": "https://yourapp.com/callback" }'

Returns an authorization_url. Send the plant owner there. On completion we discover the devices under that account and register them automatically — you do not call POST /v1/devices on this path.

04Confirm data is flowing

curl "https://sandbox.api.arkreen.com/v1/telemetry?project_id=prj_8fK2mQ&limit=5" -H "Authorization: Bearer $TOKEN"

First readings usually appear within 30 minutes. Cloud connectors poll on the manufacturer's publication cadence — typically 5 to 15 minutes — so this path will never be real-time. For most financing purposes it does not need to be.

05Wait out the baseline window

The project enters status baseline for 7 to 30 days depending on asset class. During this window we establish what normal looks like for this specific site: expected output against irradiance, typical availability, plausible ramp rates. The window is not a queue you are waiting in — it is the model that makes anomaly detection meaningful afterward.

Track it: GET /v1/projects/{id}/assurance

The account has no plants attached, or the credentials are a sub-account without device scope. Re-authorize with an admin account.

Expected. Most inverter clouds stop publishing when production is zero. Nighttime gaps are recognized and do not count against continuity.

The connector could not attach a provenance signature — some vendor APIs do not offer one. Check GET /v1/connectors/authorizations/{auth_id} for provenance: unsupported.