Skip to main content

Selecting a Protocol

All of the api.stream API are backed by our GRPC services. In front of those services, we provide gRPC Web and REST gateways. This allows partners to select an API access protocol that optimally fits into their developer workflow.

We encourage development partners to use our GRPC or gRPC Web API interfaces via one of our API SDK offerings. Doing so lets partners focus their development efforts on their market-specific and differentiated business logic rather than implementing REST API wrappers. The auto-generated code stubs in the API SDKs facilitate IDE auto-complete, in-line documentation, and data type and field name validation and marshalling.

If an API SDK is unavailable for your development environment, let us know! We are always interested in providing additional API SDKs to enable our customers to avail themselves of all of the advantages of using a GRPC-based service.

GRPC​

At present, we offer native GRPC API SDKs for the following languages:

  • Java (coming soon!)

gRPC Web​

Native GRPC is not presently available to browser environments. As such, we offer a gRPC Web interface and API SDK offering. This provides all the benefits of our GRPC interface, but via HTTPS/1.1.

At present, we offer gRPC Web API SDKs for the following languages:

  • JavaScript/TypeScript (browser and node)

REST​

Every service can be accessed via REST over HTTPS/1.1