Closer
  • Closer guides and FAQ
  • Back to Closer
  • Guide
    • Onboarding
      • Configure your widget
      • Install the widget on your website
      • Invite your team
      • Get the mobile app
      • Advanced Closer widget integration
    • Zacznij używać Closer
      • Przewodnik po platformie
      • Rozmowy
        • Inbox
    • Zarządzaj doradcami
      • Zaproś doradców firmy
      • Ustawienia doradcy
      • Grupuj doradców
    • Skonfiguruj routing
      • Wprowadzenie
      • Dodaj tagi
      • Reguły tagowania
      • Dodaj reguły tagowania
      • Grupuj tagi
      • Ustawienia grupy tagów
    • Getting deeper in dashboard
      • Conversations
        • Inbox
        • Conversation data
    • Getting deeper in widget
      • Widget guides
    • Notifications
    • How to
      • Schedule online meetings
      • Click to call
      • Tagging
      • Proactive messages
      • Set up skill-based routing
      • Manage your team’s workload
      • Force new user everytime in widget
      • User authorization callbacks
      • On deinit callback
      • Identify leads
      • Reports
      • SLA
      • Customer typing preview
      • Push out data with Webhooks
      • Routing
      • Widget OAuth configuration
      • Forms configuration
      • Org configuration API
      • Org configuration fields
      • Configure OMNI integration
      • Elasticsearch business logs
      • Elasticsearch security logs
      • Manage widget button
    • Contact us
    • Supported browsers
    • Upcoming features drafts
      • Business events structure (JSON) - Draft
  • FAQ
    • General
    • Bots
    • Calendar
    • Random
Powered by GitBook
On this page
  • Configuration
  • /userinfo endpoint

Was this helpful?

  1. Guide
  2. How to

Widget OAuth configuration

Configuration

You can configure oauth authorization for customers on our endpoint: https://spinner.closer.app/api/oauth-config. All requests needs admin's ApiKey in X-Api-Key header. To create a config send a POST with body:

{
	"tokenEndpoint": "http://oauth.com/token",
	"userInfoEndpoint": "http://oauth.com/userinfo",
	"clientId": "clientId",
	"clientSecret": "clientSecret",
	"oauthConfigEnabled": true
}

You can retrieve config by executing GET request. Result should look like this:

{
	"tokenEndpoint": "http://oauth.com/token",
	"userInfoEndpoint": "http://oauth.com/userinfo",
	"clientId": "clientId",
	"clientSecret": "**",
	"oauthConfigEnabled": true
}

To update config you can use PATCH request with body:

{
	"tokenEndpoint": "http://oauth.com/token",
	"userInfoEndpoint": "http://oauth.com/userinfo",
	"clientId": "clientId",
	"clientSecret": "clientSecret",
	"oauthConfigEnabled": true
}

The only field required when updating config is oauthConfigEnabled.

You can also delete your config by simply executing DELETE without body.

/userinfo endpoint

This endpoint should return body:

{
"id": "external_id_2",
"email": "a@example.com"
"phone": { "region": "PL", "number": "666777666" },
"firstName": "Tyler",
"lastName": "Durden",
"backOfficeData": [{
    "key": "office_number",
    "value": ""777666777",
    "displayName": "Office number"}]
}

Only id field is required. In backOfficeData you can specify any additional information you want to display for your agents.

PreviousRoutingNextForms configuration

Last updated 4 years ago

Was this helpful?