Get desktop application:
View/edit binary Protocol Buffers messages
Used in: ,
Used in:
Used in:
Used in: ,
Used in:
Used in:
Used in:
Used in:
Used in: , , , , ,
logical expressions
basic comparison
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used as response type in: stub.EventChannel.Poll, stub.Watch.Watch
Used as field type in: , , ,
CREATE,UPDATE - records are for incoming and outgoing records GET - there will be only one record LIST - result of the list operation
LIST - search params for the list operation
If true, this will be last event on operation list
If true, backend will wait for processing this event before sending next one on operation list
Request annotations
Used in: ,
for special cases
Used in:
Used in:
Events pass through selectors, if selector returns true, event will be processed Selector returns true if no selector fails. For example, if you passed empty selector, it will return true for all events.
Used in:
star means all
star means all, empty means proceed
Used in: ,
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
defaults to 10 seconds
defaults to 1 day
Used in:
Used in:
Used in:
Used as request type in: stub.Record.WriteStream
Used as response type in: stub.Record.ReadStream
Used as field type in: , , , , , , , , , , , , ,
Used in:
Used in:
referenced resource namespace
referenced resource name
Used in: , , , , , , , , , , , , ,
unique resource id; read only
unique resource name, it is unique per namespace
each resource is kept inside a namespace. One namespace can have multiple resources
list of properties of resource. This properties will be used by records of resource. Properties is columns on sql databases. For schemaless data structures properties is only managed by API Brew itself
list of resource indexes. Its implementation is depending on data source backend and may not be supported by some backends.
If virtual is true. Operations will not phisically affect datasource/backend. Virtual resources is for extension purposes. Their behaviors can be extended and altered. It can also be used to integrate 3rd party systems.
if true, delete and update will not be allowed on this resource
if abstract, resource is only available to internal and extension side operations
Used in:
list of properties inside single index. Normally you will need only single property. Multi property will be needed for multi property indexes(for complex indexes)
Index type(BTREE, HASH)
if true index will be unique index
Used in:
Used in:
Used in:
Used in:
Used in:
(message has no fields)
Used in:
Used in:
Used in:
Used in:
(message has no fields)
Used in:
Used in:
Used in:
Used in:
Used in:
Resource properties is used to describe its schema. Each resource property is corresponding to a field in a record API Brew is responsible to validate data according to property types. For example, when you call create record and if you send 123.45 for int64
Used in: ,
property name
type of property
type ref
type ref, is only applicable to Struct
this is to mark property as required
length property is only valid and required for String typed properties
immutable is to mark property as immutable. If marked, updates on this field on records will be discarded
virtual is to mark property as virtual. Virtual properties are not stored on backend. They are calculated on the fly
defaultValue is default value.
exampleValue is example value. It is an informative column
enumValues is used if property type is an enum
reference property is only valid and required for Reference types.
reference property is only valid and required for Reference types.
item is used for complex types(list, map). For list, subType is element type. For map, it is value type(key type is always string)
It is an informative column
It is an informative column
Used in:
source config is to configure resource and bind it to data-source and an entity inside data source. An entity is like a table on sql databases or collection on mongodb etc.
Used in:
data source name: where resource structure and its data will be physically exists. Data source name is required if resource is not virtual
catalog is like a folder/schema/database. It is changing from backend to backend. Basically it is for grouping entities
entity name an item on datasource backend where resource will be bound. For sql databases it is table name, for mongo it is collection name, etc.
Used in:
list of properties of resource. This properties will be used by records of resource. Properties is columns on sql databases. For schemaless data structures properties is only managed by API Brew itself
Used in:
Used in:
Used in: ,
Used in:
Used in: ,
issue term
jwt token
expiration time
Used in: , ,
1 minute
20 minutes
2 days
60 days
2 years