integration-data-back
close

Få en præsentation.

Så enkel er processen:

  • Udfyld formularen
  • En af vores customer experience eksperter vil derefter kontakte dig
  • Du vil opleve vores Customer Experience Platform og få svar på dine spørgsmål
Close

Log In

Forgot password?

Hvis du har glemt dit password, så KLIK HER.

For at login i vores løsning til Paneler, så KLIK HER

A RESTful webservice
The API is a RESTful web service and strives to conform to the design principles of Representational State Transfer (REST).
REST is now the most popular Web service design model. As a developer, you should have at least a basic understanding of
REST. Here’s what Wikipedia has to say about RESTful web services:
http://en.wikipedia.org/wiki/Representational_State_Transfer
Methods

Description
This method gets a report list of respondents that match one or more conditions or filters. Each report will be headed by a summary section providing aggregate information of the respondent list.

Request
The Request will be of type GET and the URI for the send method is:

https://www.relationwise.com/rls/restapi2/get/respondents/?

Note:

  • “?” is necessary if you intend to include at least one parameter (filter).
  • “&” between parameters is necessary if you intent to use multiple parameters (filters).

Request headers

Header Required Value/Description
key YES Your authentication API key:

b66iPU7oGsW2BTNA/nfqlA==

Filtering the data returned by the request
The query string part of the request may contain several parameters for filtering purposes. Multiple parameters can be used in a request to refine filtering and conditions for the resulting respondent list.

Note: Each query string value must be properly url-encoded to escape special characters that could break the link.

Required Parameter description
NO [variablename]-uid

Filter for respondents using Unique identifier part of a respondent variable.
Example:
Filter respondents who have an associated store number as a unique identifier

NO[variablename]-value

Filter for respondents using Value part of a respondent variable.
Example:
Get a respondent who has a specific customer number

NOname

Filter for respondents using Name part of respondent.
Example:
Get a respondent with a specific name

If multiple respondents have the same name, multiple respondents will be returned.NOemail

Filter for respondents using Email part of respondent.
Example:
Get a respondent with a specific email

NOscore

Filter for respondents who have given a certain score.
Example:
Get detractors (have a given a loyalty score of 6 or less)

Example:
Get respondents who have given a score of 1 or 10

NOtime

Filter for respondents within a given period.
Example:
Get all respondents within the third quarter of 2012

Example:
Get all respondents on New Year’s morning

Example:
Get all respondent’s on New Year’s day

NOrespondents

Filter for respondents who occur at given positions of the report list (paging mechanism for optimizing large queries).
Example:
Get respondents that occur at positions 50 to 100 in the report list

NOorder-by-asc
order-by-desc

Order respondents in ascending or descending order by score, name or time.
Example:
Order report list by time, latest first

Example:
Order report list by score, lowest scoring respondents first

Example:
Order report list by name, with respondents in alphabetical order

 

Code example
The following code example use


in the most
direct “no frills” way possible to get the job done.

This code example uses the custom variables that you’ve already configured. To edit these variables
click here.