Skip to main content
PATCH
Update a data request

Authorizations

Authorization
string
header
required

Path Parameters

project_id
string
required

The project's friendly ID (e.g. prj_aBcD1234eFgH5678).

id
string
required

The data request's friendly ID (e.g. req_AaBbCcDdEeFfGgHh).

Pattern: ^req_[A-Za-z0-9]{16}$

Body

application/json
data_request
object
required

start_time and end_time are required unless the request is a template (it has a recurring schedule). A request needs at least one entry in inputs_attributes.

Response

OK

id
string
Example:

"req_AaBbCcDdEeFfGgHh"

name
string | null
role
enum<string>

template for a request with a recurring schedule, which sends a copy on each run; otherwise sendable.

Available options:
sendable,
template
start_time
string<date-time> | null
end_time
string<date-time> | null
sent_at
string<date-time> | null

When the request email was first sent, or null.

message
string | null
url
string<uri>

The submission link sent to recipients. Anyone holding it can submit data without signing in, so treat it as a secret.

Example:

"https://app.gomangrove.com/nexus/data_requests/SIGNED_ID"

template_id
string | null

The friendly ID of the template this request was sent from, if any.

Example:

"req_AaBbCcDdEeFfGgHh"

recurring_schedule_friendly_id
string | null

The friendly ID of the recurring schedule that sent this request, if any.

schedule
object | null

The attached schedule, or null when there is none.

created_at
string<date-time>
updated_at
string<date-time>