OpenADR Alliance · Arazzo Workflow

Publish a program and dispatch a demand response event

Version 1.0.0

BL/VTN-side flow against an OpenADR 3.1.1 VTN: authenticate with the client-credentials grant, create (or reuse) a program, publish an event carrying priced intervals against it, then read the event back. Every operationId is verified against the OpenADR 3.1.1 specification. The base URL is implementer-supplied — the OpenADR Alliance hosts no API.

1 workflow 3 source APIs 1 provider
View Spec View on GitHub EnergyUnited StatesUtilitiesElectricityDemand ResponseGridDEROpenADRStandardsSmart GridEV ChargingCertificationArazzoWorkflows

Provider

openadr-alliance

Workflows

dispatch-demand-response-event
Authenticate, create a program, publish an event on it, and verify.
Requires a token with write_programs, write_events and read_all — that is a BL client. NOTE - OpenADR 3 has no idempotency key; step 3 will create a second event if replayed.
5 steps inputs: clientID, clientSecret, eventName, programName, targets outputs: eventID, programID
1
discover-auth-server
Ask the VTN where its token endpoint is (3.1.0+; skip on a 3.0.x VTN).
2
get-token
Client-credentials grant. Body is application/x-www-form-urlencoded, not JSON.
3
create-program
Create the demand response program the event will hang off.
4
publish-event
Publish the event. This dispatches real load — do not replay blindly.
5
verify-event
Read the event back to confirm the VTN accepted it as published.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Publish a program and dispatch a demand response event
  version: 1.0.0
  description: >-
    BL/VTN-side flow against an OpenADR 3.1.1 VTN: authenticate with the client-credentials
    grant, create (or reuse) a program, publish an event carrying priced intervals against
    it, then read the event back. Every operationId is verified against the OpenADR 3.1.1
    specification. The base URL is implementer-supplied — the OpenADR Alliance hosts no API.
  x-realizes-capability-ids:
  - BC-3840.30
  x-capability-derivation:
    method: 'deterministic join: sourceDescriptions -> per-tag OpenAPI -> tag/capability edge. No classification at this step.'
    min_confidence: 0.7
    sources:
    - capability_id: BC-3840.30
      capability_name: Demand Response Operations
      spec: openadr-alliance-programs-api-openapi.yml
      confidence: 0.72
    model: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
sourceDescriptions:
- name: authApi
  url: ../openapi/openadr-alliance-auth-api-openapi.yml
  type: openapi
- name: eventsApi
  url: ../openapi/openadr-alliance-events-api-openapi.yml
  type: openapi
- name: programsApi
  url: ../openapi/openadr-alliance-programs-api-openapi.yml
  type: openapi
workflows:
- workflowId: dispatch-demand-response-event
  summary: Authenticate, create a program, publish an event on it, and verify.
  description: >-
    Requires a token with write_programs, write_events and read_all — that is a BL client.
    NOTE - OpenADR 3 has no idempotency key; step 3 will create a second event if replayed.
  inputs:
    type: object
    required: [clientID, clientSecret, programName]
    properties:
      clientID: {type: string, description: OAuth 2.0 client id issued by the VTN}
      clientSecret: {type: string, description: OAuth 2.0 client secret issued by the VTN}
      programName: {type: string, description: 'short program handle, e.g. ResTOU'}
      eventName: {type: string, description: human label for the event}
      targets: {type: array, items: {type: string}, description: target strings the event applies to}
  steps:
  - stepId: discover-auth-server
    description: Ask the VTN where its token endpoint is (3.1.0+; skip on a 3.0.x VTN).
    operationId: getAuthServerInfo
    successCriteria:
    - condition: $statusCode == 200
  - stepId: get-token
    description: Client-credentials grant. Body is application/x-www-form-urlencoded, not JSON.
    operationId: fetchToken
    requestBody:
      contentType: application/x-www-form-urlencoded
      payload:
        grant_type: client_credentials
        client_id: $inputs.clientID
        client_secret: $inputs.clientSecret
        scope: read_all write_programs write_events
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      accessToken: $response.body#/access_token
  - stepId: create-program
    description: Create the demand response program the event will hang off.
    operationId: createProgram
    parameters:
    - name: Authorization
      in: header
      value: Bearer $steps.get-token.outputs.accessToken
    requestBody:
      contentType: application/json
      payload:
        programName: $inputs.programName
        targets: $inputs.targets
    successCriteria:
    - condition: $statusCode == 201
    outputs:
      programID: $response.body#/id
  - stepId: publish-event
    description: Publish the event. This dispatches real load — do not replay blindly.
    operationId: createEvent
    parameters:
    - name: Authorization
      in: header
      value: Bearer $steps.get-token.outputs.accessToken
    requestBody:
      contentType: application/json
      payload:
        programID: $steps.create-program.outputs.programID
        eventName: $inputs.eventName
        targets: $inputs.targets
    successCriteria:
    - condition: $statusCode == 201
    outputs:
      eventID: $response.body#/id
  - stepId: verify-event
    description: Read the event back to confirm the VTN accepted it as published.
    operationId: searchEventsByID
    parameters:
    - name: eventID
      in: path
      value: $steps.publish-event.outputs.eventID
    - name: Authorization
      in: header
      value: Bearer $steps.get-token.outputs.accessToken
    successCriteria:
    - condition: $statusCode == 200
  outputs:
    programID: $steps.create-program.outputs.programID
    eventID: $steps.publish-event.outputs.eventID

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/openadr-alliance-dispatch-event"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.