Add User Integration

To initiate the integration flow and allow a user to connect data providers, applications must redirect the user to Spike's integration initialization page.
Open URL address in the browser
GET
Params
Query Parameters
provider
required
String
Name of data provider
user_id
required
String
A unique ID representing the end user. Typically this will be a user ID number from your application.
client_id
required
String
App ID for your team
HTML
|
RESPONSES
200
|
﻿
﻿
﻿
﻿
Post a user information and start the integration process.
POST
Params
Form Parameters
client_id
required
String
App ID for your team
provider
required
String
Name of data provider
user_id
required
String
A unique ID representing the end user. Typically this will be a user ID number from your application.
HTML
|
RESPONSES
200
|
﻿
Users will be redirected to a data provider website and users will be asked to submit authentication details. Once the user authorizes access to their data, Spike returns the user back to the application using the postback URL. (You can edit it on the developer console). Appended to the postback URL is the Spike user ID. Following is an example of the postback URL with the user ID highlighted:
https://my_test_app.com/callback?provider=fitbit&user_id=fa1e3803-6068-4ea7-9788-eccce210d30c﻿
Please save it and use it for all user data requests.
Recommendations for mobile web views elementsTo enable Oauth with GoogleFit on mobile phones, you must specify the User-Agent attribute on your web view component. For example:
User-Agent: Mozilla/5.0 (iPhone; CPU iPhone OS 13_1_2 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.0.1 Mobile/15E148 Safari/604.1

User-Agent: Mozilla/5.0 (Linux; Android 6.0; Nexus 5 Build/MRA58N) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Mobile Safari/537.36
﻿
Did this page help you?
Yes
UP NEXT
Get User Data
Docs powered by archbee
TABLE OF CONTENTS
GET
Star User Integration
POST
Start user integration
Recommendations for mobile web views elements