Request and response model
Availability: The DevBase runtime and production API are not yet deployed. This page describes the committed v1 contract for integration planning; requests to the API URL will not succeed until the runtime is released.
DevBase uses standard Connect procedure paths and protobuf JSON. Unary calls send one JSON object and receive one JSON object. Server-streaming calls send one JSON request and receive a sequence of JSON response messages; client-streaming and bidirectional streaming are not public.
Protobuf field names use their JSON names. UUID v7 values use the UUIDv7 wrapper message shape, bytes values are base64 strings, timestamps use RFC 3339 strings, durations use protobuf duration strings, and enum values use their protobuf JSON names. Lists use bounded pages with opaque cursors:
Mutations require a UUID v7 requestId. Repeating the same principal, procedure, request ID, and payload returns the original result; changing the payload returns an idempotency conflict. One-time secret plaintext, including webhook signing secrets, is unavailable on replay; if the initial create or rotation response is lost, recover by performing a new rotation rather than expecting the secret value in the replayed response. Mutable resources expose resourceVersion; updates and deletion require the expected version.