servicestack-client
This library contains the Typed ServiceStack Client library that is an idiomatic port of ServiceStack's ss-utils.js JavaScript Client in native TypeScript. It provides integration with many ServiceStack features including TypeScript Add ServiceStack Reference and Server Events.
Web, Node.js and React Native
It contains a clean "jQuery-free" implementation based on JavaScript's new Fetch API standard, utilizing the fetch-everywhere implementation so it can be used in both JavaScript Web apps, Node.js server and test projects as well as React Native iOS and Android Mobile Apps as seen in TypeScript Server Event Examples.
Install
This package is pre-configured in all ServiceStackVS TypeScript VS.NET Templates
Node.js projects can install it with:
npm install --save servicestack-client
or if using jspm:
jspm install servicestack-client
npm install --save-dev servicestack-client
Where you'll also need to install the Type Definitions contained in the servicestack-client
npm package separately.
Ideal Typed Message-based API
The TypeScript JsonServiceClient
enables the same productive, typed API development experience available
in ServiceStack's other 1st-class supported client platforms.
The JsonServiceClient
leverages the additional type hints ServiceStack embeds in each TypeScript Request DTO
to achieve the ideal typed, message-based API - so all API requests benefit from a succinct, boilerplate-free
Typed API.
Here's a quick look at what it looks like. The example below shows how to create a
C# Gist in Gislyn
after adding a TypeScript ServiceStack Reference
to gistlyn.com
and installing the servicestack-client
npm package:
;; ; ;;file.filename = "main.cs";file.content = 'var greeting = "Hi, from TypeScript!";';request.files =; try catche
Where the response
param is typed to StoreGistResponse
DTO Type.
Sending additional arguments with Typed API Requests
Many AutoQuery Services utilize implicit conventions to query fields that aren't explicitly defined on AutoQuery Request DTOs, these can now be queried by specifying additional arguments with the typed Request DTO, e.g:
; //typed to QueryResponse<TechnologyStack> ;
Which will return TechStacks developed by ServiceStack.
Calling APIs with Custom URLs
You can call Services using relative or absolute urls, e.g:
client.get"/technology/ServiceStack" client.get"http://techstacks.io/technology/ServiceStack" // GET http://techstacks.io/technology?Slug=ServiceStackclient.get"/technology",
as well as POST Request DTOs to custom urls:
client.postToUrl"/custom-path", request, ; client.putToUrl"http://example.org/custom-path", request;
Raw Data Responses
The JsonServiceClient
also supports Raw Data responses like string
and byte[]
which also get a Typed API
once declared on Request DTOs using the IReturn<T>
marker:
public class ReturnString : IReturn<string> {}public class ReturnBytes : IReturn<byte[]> {}
Which can then be accessed as normal, with their Response typed to a JavaScript string
or Uint8Array
for
raw byte[]
responses:
; ;
Authenticating using Basic Auth
Basic Auth support is implemented in JsonServiceClient
and follows the same API made available in the C#
Service Clients where the userName/password
properties can be set individually, e.g:
;client.userName = user;client.password = pass; ;
Or use client.setCredentials()
to have them set both together.
Authenticating using Credentials
Alternatively you can authenticate using userName/password credentials by
adding a TypeScript Reference
to your remote ServiceStack Instance and sending a populated Authenticate
Request DTO, e.g:
;request.provider = "credentials";request.userName = userName;request.password = password;request.rememberMe = true; ;
This will populate the JsonServiceClient
with
Session Cookies
which will transparently be sent on subsequent requests to make authenticated requests.
Authenticating using JWT
Use the bearerToken
property to Authenticate with a ServiceStack JWT Provider using a JWT Token:
client.bearerToken = jwtToken;
Alternatively you can use a Refresh Token instead:
client.refreshToken = refreshToken;
Authenticating using an API Key
Use the bearerToken
property to Authenticate with an API Key:
client.bearerToken = apiKey;
Transparently handle 401 Unauthorized Responses
If the server returns a 401 Unauthorized Response either because the client was Unauthenticated or the
configured Bearer Token or API Key used had expired or was invalidated, you can use onAuthenticationRequired
callback to re-configure the client before automatically retrying the original request, e.g:
client.onAuthenticationRequired = ; //Automatically retries requests returning 401 Responses with new bearerToken;
Automatically refresh Access Tokens
With the Refresh Token support in JWT
you can use the refreshToken
property to instruct the Service Client to automatically fetch new
JWT Tokens behind the scenes before automatically retrying failed requests due to invalid or expired JWTs, e.g:
//Authenticate to get new Refresh Token;authClient.userName = userName;authClient.password = password;; //Configure client with RefreshTokenclient.refreshToken = authResponse.RefreshToken; //Call authenticated Services and clients will automatically retrieve new JWT Tokens as needed;
Use the refreshTokenUri
property when refresh tokens need to be sent to a different ServiceStack Server, e.g:
client.refreshToken = refreshToken;client.refreshTokenUri = authBaseUrl + "/access-token";
ServerEvents Client
The TypeScript ServerEventClient is an idiomatic port of ServiceStack's C# Server Events Client in native TypeScript providing a productive client to consume ServiceStack's real-time Server Events that can be used in TypeScript Web, Node.js Server and React Native iOS and Android Mobile Apps.
;.addListener"theEvent", // Add listener for pub/sub event trigger.start; // Start listening for Server Events!
When publishing a DTO Type for your Server Events message, your clients will be able to benefit from the generated DTOs in TypeScript ServiceStack References.
Troubleshooting
If you're getting missing Type Definitions for Headers
, Response
, Request
, etc. You'll need to import
the Type Definitions for W3C's fetch
API, preferably by using the latest version of TypeScript and
referencing the core es2016 and dom libs in TypeScript's tsconfig.json
, e.g:
Alternatively you can import the whatwg-fetch Type Definitions with:
npm install @types/whatwg-fetch --save-dev