gRPC API
The gRPC API is EvidentSource’s primary programmatic interface. Every SDK is built on top of it, and the REST surface is generated from the same proto definitions.
Endpoint
Section titled “Endpoint”- Sandbox:
grpcs://sandbox.evidentsource.com:50051 - Your deployment: whatever
:50051exposes behind your ALB
TLS is required in production. The Sandbox uses a public certificate.
Services
Section titled “Services”EventStore
Section titled “EventStore”AppendEvents— append a batch of events with optional DCB conditionsAppendCommand— route a command to its State Change componentQueryEvents— read events by stream, subject, or type, with bi-temporal parametersSubscribeEvents— live tail of the event log with snapshot + follow
StateView
Section titled “StateView”ReadStateView— read a specific state view instance, with optional bi-temporal parametersSubscribeStateView— snapshot + live updates
ListDatabases,CreateDatabase,DeleteDatabaseListComponents,RegisterComponent,UpdateComponentGetSchema— introspect schemas for a database
Finding the proto files
Section titled “Finding the proto files”The canonical proto definitions live in the monorepo under evidentsource/interface/proto/. Each SDK vendors a copy and regenerates language bindings from them.
Bi-temporal parameters
Section titled “Bi-temporal parameters”Every read RPC takes optional as_of_transaction_time and as_of_effective_time timestamps. See Bi-Temporal Indexing.
Authentication
Section titled “Authentication”Bearer tokens are sent in the authorization metadata header. See Security.
Every SDK wraps this surface in language-native types. See SDKs.