Skip to content
Developer

Receive opportunity notifications

POST
/receive-notifications

To process opportunity notifications we recommend the following.

  1. Call to get notifications in queue (max 50 will be returned, based on provided limit value)
  2. if there are no notifications to process, pause 5 seconds, then try again
  3. if notifications are present, process and acknowledge each one using /ack-notifications, then loop immediately back to step 1 to receive more notifications.

This will ensure that the queue is processed as quickly as possible without overwhelming either system with a constant loop of nothing to process.

Parameters

Section titled “ Parameters ”

Header Parameters

Section titled “Header Parameters ”
dynata-expiration
required
string format: date-time

RFC3339 timestamp indicating request expiration

dynata-access-key
required
string

Dynata provided access key

Example
ADSF23ADF354GFDDS23
dynata-signature
required
string

Signature created using the Dynata methodology

Example
dsklj435kljhfdSAFdsalk34

Request Body

Section titled “Request Body ”
object
limit

Maximum number of opportunities to return per request

integer format: int64
>= 1 <= 50 
25
shards

Sharding options for concurrent consumption

object
count
required

Total number of shards; should equal number of consumers

integer format: int64
>= 1 <= 5 
3
current
required

Requesting consumer identifier; cannot be greater than number of shards

integer format: int64
>= 1 <= 5 
3
visibility_timeout

The period of time, in seconds, during which other consumers will be unable to receive a notification

integer format: int32
<= 600 
300

Responses

Section titled “ Responses ”

200

Section titled “200 ”

List of opportunity notifications

Array
object
id
required

Unique identifier of opportunity

integer format: int64 
12345
status
required

Current opportunity status

string
Allowed values: OPEN PAUSED CLOSED 
OPEN
length_of_interview
required

Estimated length of interview

integer format: int32 
10
incidence_rate
required

Estimated incidence rate (IR) for a quota group. The IR is the percentage of respondents in the general population expected to qualify for the quota group.

integer format: int32 
80
cost_per_interview
required

Offer price per interview

number format: float 
0.55
completes
required

Total fielding completes requested

integer format: int64 
100
group_id
required

Identifier of opportunity group

integer format: int64 
112411272
evaluation
required

Click balancing mode

string
Allowed values: COMPLETES STARTS 
COMPLETES
days_in_field
required

Expected duration of opportunity in days

integer format: int32 
25
locale
required

Localization of the opportunity

object
language
required

Lowercase two-character ISO language value

string
/^[a-z]{2}$/ 
en
country
required

Uppercase two-character ISO country value

string
/^[A-Z]{2}$/ 
US
devices
required

Devices supported by opportunity

Array<string>
Allowed values: mobile desktop tablet 
[
  "desktop",
  "tablet"
]
links
required

Entry links of opportunity

object
live
required

Live entry link

string format: uri 
https://respondent.qa-rex.dynata.com/start?ctx=7321f626-0de5-4d45-b138-29864ce635b4&language=en
created
required

Creation date of opportunity

string format: date-time
project_exclusions
required

Projects that prevent respondent participation in this project

Array<integer>
[
  293847,
  561112
]
category_exclusions

Categories that prevent respondent participation in this project

Array<integer>
[
  23,
  10
]
notified
required

RFC3339 timestamp of notification

string format: date-time
project_id
required

Identifier of opportunity project — opportunities in the same project have mutual participation exclusions

integer format: int64 
1589419
order_number
required

Unique project identifier.

string
/^ORD-\d+-\w+$/ 
ORD-1234-5ab678
requirements
required
object
requires_recontact
required

Requires inviting (recontacting) specific respondents to a follow up survey.

boolean
requires_pii_collection
required

Requires respondents to provide personally identifiable information (PII) within client survey.

boolean
requires_webcam
required

Requires respondents to utilize their webcam to participate.

boolean
requires_eye_tracking
required

Requires use of facial recognition technology with respondents, such as eye tracking.

boolean
requires_cookie_drops
required

Requires partner to allow Dynata to drop a cookie on respondent.

boolean
requires_sample_plus
required

Requires partner-uploaded respondent PII to expand third-party matched data.

boolean
requires_app_vpn
required

Requires respondents to download a software application.

boolean
requires_manual_rewards
required

Requires additional incentives to be manually awarded to respondent by partner outside of the typical online survey flow.

boolean
category_ids

Categories related to opportunity

Array<integer>
[
  123,
  456,
  789
]
client_id
required

Identifier of client requesting the study. (requires permission to view)

integer format: int64
nullable 
54321
cells

Individual target definitions

Array
object
tag
required

Cell reference tag

string
163a74b4-68fd-4bae-b264-03e626a20b2f
attribute_id
required

Identifier of the Dynata attribute. If the value is -1 it means it’s an ineffable cell and it should discarded

integer format: int64 
80
negate
required

Negative evaluation of value(s)

boolean
kind
required

Cell kind

string
Allowed values: RANGE LIST VALUE COLLECTION INEFFABLE ANSWERED INVITE_COLLECTIONS STATIC_INVITE_COLLECTIONS 
LIST
One of:
object
value

Single cell value; populated when cell kind is VALUE

string
filters

Target combinations without a limit or status.

Array<Array<object>>
quotas

Target combinations with a limit and status.

Array<Array>

Headers

Section titled “Headers ”
notification-count
integer format: int64 
50

Number of returned notifications

notification-total
integer format: int64 
100

Number of notifications in the account’s queue

400

Section titled “400 ”

Bad request

object
message
required

A human readable description of the error

string

401

Section titled “401 ”

Invalid credentials

object
message
required

A human readable description of the error

string

403

Section titled “403 ”

Unauthorized

object
message
required

A human readable description of the error

string

500

Section titled “500 ”

Internal server error

object
message
required

A human readable description of the error

string