Eventarc delivers events, regardless of provider, to the target
destination in a CloudEvents (cloudevents.io) format
in binary content mode.
CloudEvents is the Cloud Native Computing Foundation's
open standard specification for
describing event metadata in a common way. Using a standard way to describe
event metadata ensures consistency, accessibility, and portability.
A CloudEvent in binary content mode has its context attributes described as HTTP
headers. The names of the HTTP headers are the context attribute names prefixed
with ce-. The Content-Type header reflects the media type in which the event
data is encoded.
For Workflows destinations, the Workflows service
converts the event to a JSON object, and
passes the event into the workflow execution as a runtime argument.
Define a message binding (Eventarc Advanced)
You can define a message binding and construct a new HTTP request. For more
information, see
Transform received events.
Format received events (Eventarc Advanced)
You can configure a pipeline to expect event data in a specific format or,
before events are delivered to a destination, you can convert event data from
one supported format to another. For example, you might need to route events to
an endpoint that only accepts Avro or Protobuf data. The following format
conversions are supported:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-25 UTC."],[[["\u003cp\u003eEventarc delivers events in CloudEvents format, which is an open standard for describing event metadata, ensuring consistency, accessibility, and portability.\u003c/p\u003e\n"],["\u003cp\u003eEvent data in binary content mode has context attributes described as HTTP headers prefixed with \u003ccode\u003ece-\u003c/code\u003e, and the \u003ccode\u003eContent-Type\u003c/code\u003e header reflects the media type.\u003c/p\u003e\n"],["\u003cp\u003eTarget destinations receive events using an HTTP protocol binding, while Workflows destinations receive a JSON object representation of the event.\u003c/p\u003e\n"],["\u003cp\u003eEventarc Advanced allows users to define a message binding to construct a new HTTP request, enabling transformations of received events.\u003c/p\u003e\n"],["\u003cp\u003eEventarc Advanced supports format conversions between Avro, JSON, and Protobuf, allowing events to be delivered in various formats to meet endpoint requirements.\u003c/p\u003e\n"]]],[],null,["# Event format\n\n[Advanced](/eventarc/advanced/docs/overview) [Standard](/eventarc/standard/docs/overview)\n\nEventarc delivers events, regardless of provider, to the target\ndestination in a CloudEvents ([cloudevents.io](http://cloudevents.io/)) format\nin binary content mode.\n\nCloudEvents is the Cloud Native Computing Foundation's\n[open standard specification](https://github.com/cloudevents/spec) for\ndescribing event metadata in a common way. Using a standard way to describe\nevent metadata ensures consistency, accessibility, and portability.\n\nA CloudEvent in binary content mode has its context attributes described as HTTP\nheaders. The names of the HTTP headers are the context attribute names prefixed\nwith `ce-`. The `Content-Type` header reflects the media type in which the event\ndata is encoded.\n\nTarget destinations consume events using an\n[HTTP protocol binding](/eventarc/docs/cloudevents).\n\nFor Workflows destinations, the Workflows service\nconverts the event to a [JSON object](/eventarc/docs/cloudevents-json), and\npasses the event into the workflow execution as a runtime argument.\n\nDefine a message binding (Eventarc Advanced)\n--------------------------------------------\n\nYou can define a message binding and construct a new HTTP request. For more\ninformation, see\n[Transform received events](/eventarc/advanced/docs/receive-events/transform-events#message-binding).\n\nFormat received events (Eventarc Advanced)\n------------------------------------------\n\nYou can configure a pipeline to expect event data in a specific format or,\nbefore events are delivered to a destination, you can convert event data from\none supported format to another. For example, you might need to route events to\nan endpoint that only accepts Avro or Protobuf data. The following format\nconversions are supported:\n\n- Avro to JSON\n- Avro to Protobuf\n- JSON to Avro\n- JSON to Protobuf\n- Protobuf to Avro\n- Protobuf to JSON\n\nFor more information, see\n[Format received events](/eventarc/advanced/docs/receive-events/configure-format-events)."]]
