RSJ-Labelprinter - follow the QR-Code RSJ-Next Generation Label Printing System - makes workflow easier RSJ-Software, Company Logo

External Application Integration

Web Services

RSJ LPSNG provides the following web services:

  • Submit Print Job

Submit Print Job

titleJob description for display
formatLayout Id
dataData (in CSV, JSON, XML or Excel)
callbackoptional JSONP callback
oauth_tokenOAuth2 access token (if not specified in Authorization HTTP header in OAuth scheme)


RSJ LPSNG uses the standard OAuth2 protocol to securely integrate muliple independed external application for a multitude of users.

RSJ LPSNG uses this authentication as basis for it's routing decisions

External Application Registration

Developers can register an external application with RSJ LPS NG online by providing:

  • Application Name
  • Application Description
  • Application Icon
  • Application Redirect URL

They will receive:

  • Application Id
  • Application Secret

External Application Authorization

End users can online authorize external applications to use RSJ LPS NG on their behalve.

End User View

  1. The user click on a link in the external application, which redirects them to the RSJ LPSNG sign on (if not already logged in) and then to the RSJ LPS NG authorization screen
  2. If the user accepts the application linkage, it is redirected back to the the external application where the authentication information is stored.

External Application View

The external application provides the following information with the redirect:

  • Application Id (assigned during Application Registration)
  • Callback URL (specified during Application Registration)
  • Optional context information (for callback)
client_idClient Id (from application registration)
redir_uriRedirect URI (must match URI in application registration)
stateOptional context information for callback

After succesfull authorization, the end user session is redirected to the external application with the following parameters:

  • Context information (from redirect)
  • Temporary authorization code (valid for 10 minutes)

The external application calls a webservice to exchanges the temporary authorization with the permanent refresh token by providing:

  • Temporary authorization code
  • Application id
  • Application Secret
  • Callback URL

The external application permanently stores the refresh token for the end user

refresh_tokenRefresh token (from application authorization)
ReturnsJSON structure

External Application Requests

The external application must exchange the refresh token for an temporarily (60 minutes) valid access token before accessing RSJ LPSNG for an end user. It calls a webservice with:

  • Refresh token

It receives:

  • Temporary (60 minutes) access token

The external application includes this access token in its web service requests (in the Auth HTTP Header or as a parameter)

RSJ LPSNG associates the access token with the external application and the end user.

The access token can become invalid at any time (even before it is expired). In this case, an 401 error is returned and the external application must retrieve a new access token before retrying the failing request.

codeAuthorization code (from redirect)
client_idClient Id (from application registration)
client_secretClient Secret (from application registration)
refresh_tokenRefresh token (from application authorization)
ReturnsJSON structure

Use Cases


Contact us for more information:

How can we help you?

Or contact us directly:

RSJ Software GmbH
Grubmuehl 20
82131 Stockdorf

Phone: +49 89 89 41 42-0
Fax: +49 89 89 41 42-80

© Copyright 2011-2020 by RSJ Software GmbH Stockdorf. All rights reserved. - Version:1.12.0201