Transports and codegen

Both services are served from a single endpoint at , in three transports.

Transport	Base URL	Use from
gRPC over HTTP/2	Servers, CLIs, any native gRPC client.
gRPC-web	Browsers. CORS is open, so a page can call it directly.
JSON over HTTP	Anything that speaks HTTP. Same methods, REST-style routes.

The JSON transport is the same gRPC service behind a transcoder, not a second API: identical methods, identical field names, identical status codes. Read methods are GETs with query or path parameters, mutating methods are POSTs with a JSON body, and revocation is a DELETE. The routes are in the API reference.

curl <API_JSON_URL>/v1/chains \
  -H "x-api-key: $APSIS_API_KEY"

Errors arrive as the gRPC status mapped onto HTTP, with the code in the body:

{ "code": 3, "message": "unsupported pair", "details": [] }

Services

Service	Auth	Purpose
`apsis.v1.ApsisApi`	Optional `x-api-key`	Quoting, catalog, order state. Public.
`apsis.v1.PartnerApi`	`authorization: Bearer <session>`	Partner sign-in, API keys, referral claims.
`grpc.health.v1.Health`	None	Liveness and readiness.
`grpc.reflection.v1.ServerReflection`	None	Schema discovery, v1 and v1alpha.

Generating a client

The protobuf definition is the contract. Fetch it from and generate stubs for your language.

TypeScript
Go
Rust
grpcurl

The SDK ships generated types and a configured transport:

npm install <SDK_PACKAGE>

import { createApsisClient } from "<SDK_PACKAGE>";

const client = createApsisClient({
  baseUrl: process.env.APSIS_API_URL!,
  apiKey: process.env.APSIS_API_KEY,
});

To generate your own instead, use buf with protoc-gen-es and Connect’s createGrpcWebTransport in browsers or createGrpcTransport on Node.

protoc --go_out=. --go-grpc_out=. apsis/v1/api.proto

conn, err := grpc.NewClient(apsisHost, grpc.WithTransportCredentials(creds))
client := apsisv1.NewApsisApiClient(conn)

ctx := metadata.AppendToOutgoingContext(ctx, "x-api-key", key)
quote, err := client.GetQuote(ctx, req)

tonic-build compile_protos("apsis/v1/api.proto")

let mut client = ApsisApiClient::connect(apsis_api_url).await?;
let mut request = Request::new(quote_request);
request.metadata_mut().insert("x-api-key", key.parse()?);
let quote = client.get_quote(request).await?;

Server reflection is enabled, so no proto file is needed:

grpcurl $APSIS_HOST list

grpcurl \
  -H "x-api-key: $APSIS_API_KEY" \
  -d '{}' \
  $APSIS_HOST apsis.v1.ApsisApi/GetChains

Calling it without writing code

Reflection means any gRPC client can discover the schema and call the API with no local setup.

Tool	How
Playground	Every method in this reference has a Send button. Fill the body, add your key, run it against mainnet.
`grpcurl`	`grpcurl <API_HOST> list` to enumerate, then call a method as above.
`grpcui`	`grpcui <API_HOST>` opens a local browser UI over the live schema.
Postman	Create a gRPC request, point it at the endpoint, and let it import the schema by reflection.
Buf Studio	A hosted browser client that speaks gRPC-web against the endpoint directly.

There is no sandbox. Every one of these hits mainnet: quotes are real quotes, and partner methods really create keys, revoke them, and mark referral orders claimed.

Field naming

Protobuf field names are snake_case on the wire and in grpcurl payloads. Most generated clients expose them as camelCase, which is what the TypeScript examples in these docs use. Both refer to the same field.

Value conventions

Kind	Representation
Token amounts	Decimal strings in base units. Never floats.
USD values	Integer strings in micros. `1000000` is one dollar.
Chain names	Lowercase strings: `arbitrum`, `solana`.
EVM addresses	`0x`-prefixed hex.
Solana addresses	Base58.
Quote hashes	`0x`-prefixed 32-byte hex.
Timestamps	RFC 3339 strings with microsecond precision.

Amounts are strings because they exceed the precision of a JSON number. Parse them into a big integer type, not a float, at every boundary.

Health

grpc_health_probe -addr $APSIS_HOST

The health service reports readiness, which flips to not-serving when the API cannot reach its dependencies. Use it for load balancer checks rather than polling GetChains.

Get started

Build a swap

Extend

Transports and codegen

Services

Generating a client

Calling it without writing code

Field naming

Value conventions

Health

​Services

​Generating a client

​Calling it without writing code

​Field naming

​Value conventions

​Health

Services

Generating a client

Calling it without writing code

Field naming

Value conventions

Health