Skip to main content

​
Quickstart

Connect to Simpplr with Nango and see data flow in 2 minutes.
1

Create the integration

In Nango (free signup), go to Integrations -> Configure New Integration -> Simpplr.
2

Authorize Simpplr

Go to Connections -> Add Test Connection -> Authorize, then pick your tenant’s region and enter the Client ID and Client Secret of a Simpplr client application. Later, you’ll let your users do the same directly from your app.
3

Call the Simpplr API

Let’s make your first request to the Simpplr B2B API (the connection test endpoint). Replace the placeholders below with your Environment API key, integration ID, and connection ID:
Or fetch credentials with the Node SDK or API.Every B2B endpoint lives under /v1/b2b/, for example /v1/b2b/identity/users to list users and /v1/b2b/content/sites/contents to list content.You’re connected! Check the Logs tab in Nango to inspect requests.
4

Implement Nango in your app

Follow our Auth implementation guide to integrate Nango in your app.To obtain your own production credentials, follow the connect guide linked below.

​
Simpplr integration guides

Nango-maintained guides for common use cases. Official docs:

​
Pre-built syncs & actions for Simpplr

Enable them in your dashboard. Extend and customize to fit your needs. No pre-built syncs or actions available yet.
Not seeing the integration you need? Build your own independently.

​
API gotchas

  • Simpplr runs two different products. This integration is for Simpplr’s own platform, documented at platform.simpplr.com. Older tenants run as a managed package inside the customer’s Salesforce org and authenticate through Salesforce; use the salesforce integration for those.
  • The API host is per region, and the tenant’s OAuth token URL is the only place the region is stated: platform.app.simpplr.com (United States), platform.eu.simpplr.com, platform.au.simpplr.com and platform.ca.simpplr.com. A wrong Region points the connection at another region’s tenant.
  • Simpplr’s published B2B OpenAPI gives its token URL as https://platform.{env}.simpplr.xyz/v1/identity/oauth/token. The working domain is .com, so a client generated from that spec calls a host that does not resolve.
  • The token response carries only access_token, with no expires_in. The access token is itself a JWT, so Nango decodes it and reads its exp claim to determine the real expiry.
  • Tokens are read-only unless a scope is requested. Simpplr accepts read (the default), write and everything, and read covers GET calls plus the search endpoints that take a POST body. Simpplr grants whichever scope the token request asks for, so a client application is not limited to read access by how it was created.
  • The B2B API covers tenant-level access. Simpplr’s separate User API acts for a signed-in user and expects an authorization code exchange whose token body names the code auth_code, which this integration does not use.
  • GET /v1/b2b/identity/test is the cheapest call for checking a connection.
  • Paging differs by endpoint. The content and sites endpoints page with size and nextPageToken, but GET /v1/b2b/identity/users rejects both with a 400.
  • Content body is HTML, not markdown or plain text.
Contribute API gotchas by editing this page