Create and publish a demand response program and event as a VTN using the OpenADR 3.0 REST API.

Verified steps

1. Confirm which OpenADR REST generation your target VTN implements — OpenADR 3.1 has since been published and is not wire-compatible with 3.0, so verify the version before reusing paths/schemas.
2. Obtain an OAuth2 client-credentials bearer token for the role that will author programs and events on the VTN.
3. POST a Program object to /programs to define the DR program's metadata and payload descriptors.
4. POST an Event object to /events, referencing the programID and containing an intervals array with payloads (e.g. simple signal, price, or load-shed level) and timing.
5. Manage lifecycle via PUT/DELETE on /events/{id} and /programs/{id} as conditions change.
6. Note this is distinct from VEN-side behavior: VENs independently GET /events (optionally filtered by programID/venID) and separately POST /reports back to the VTN — the VTN does not push events unless the implementation adds an optional subscription feature.