Appends data to the specified data source

POST 
/data-sources/:dataSourceId/rows

Data can be appended to the specified data source using this API call.

The operation may work in two ways: synchronous or asynchronous. By default the operation is synchronous if only one data row is sent in the request body. If more than one data row is sent, the operation is asynchronous. You can force the operation to be asynchronous even if only one row is sent by setting the Prefer header to respond-async. Asynchronous operation returns http code 202 Accepted, while synchronous operation returns http code 201 Created.

Request

Path Parameters

dataSourceId uuidrequired

Id of the specified data source

application/json

Body

required

oneOf

MOD1

Array [

oneOf

DataSourceRowArrayInput

Array [

oneOf

MOD2

Array [

oneOf

MOD1

string

MOD2

boolean

MOD3

number

NullableObject

object

]

]

DataSourceRowObjectInput

property name*

DataRowNestableColumn

oneOf

MOD2

Array [

oneOf

MOD1

string

MOD2

boolean

MOD3

number

NullableObject

object

]

]

DataSourceRowObjectInput

property name*

DataRowNestableColumn

oneOf

MOD2

Array [

oneOf

MOD1

string

MOD2

boolean

MOD3

number

NullableObject

object

]

Responses

201

Created

application/json

Schema

Schema

rows

object[]

Array [

id int32

triggered_actions

object[]

Array [

oneOf

CustomerRequestTriggerAction

type stringrequired

Possible values: [customer-request]

request

CustomerRequest

id stringrequired

Request id

url string

Request url to be sent to customer

interactionId string

customerId string

]

]

Example (from schema)

{
  "rows": [
    {
      "id": 0,
      "triggered_actions": [
        {}
      ]
    }
  ]
}

202

Accepted

401

Unauthenticated

application/problem+json

Schema

Schema

title string

A short, summary of the problem type. Written in english and readable for engineers (usually not suited for non technical stakeholders and not localized); example: Service Unavailable

status int32

Possible values: >= 100 and < 600

The HTTP status code generated by the origin server for this occurrence of the problem.

detail string

A human readable explanation specific to this occurrence of the problem.

instance uri

An absolute URI that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.

Example (from schema)

{
  "title": "string",
  "status": 503,
  "detail": "Connection to database timed out",
  "instance": "string"
}

403

Unauthorized

application/problem+json

Schema

Schema

title string

A short, summary of the problem type. Written in english and readable for engineers (usually not suited for non technical stakeholders and not localized); example: Service Unavailable

status int32

Possible values: >= 100 and < 600

The HTTP status code generated by the origin server for this occurrence of the problem.

detail string

A human readable explanation specific to this occurrence of the problem.

instance uri

An absolute URI that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.

Example (from schema)

{
  "title": "string",
  "status": 503,
  "detail": "Connection to database timed out",
  "instance": "string"
}

404

Not found

application/problem+json

Schema

Schema

title string

A short, summary of the problem type. Written in english and readable for engineers (usually not suited for non technical stakeholders and not localized); example: Service Unavailable

status int32

Possible values: >= 100 and < 600

The HTTP status code generated by the origin server for this occurrence of the problem.

detail string

A human readable explanation specific to this occurrence of the problem.

instance uri

An absolute URI that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.

Example (from schema)

{
  "title": "string",
  "status": 503,
  "detail": "Connection to database timed out",
  "instance": "string"
}

422

Unprocessable Entity

application/problem+json

Schema

Schema

title string

A short, summary of the problem type. Written in english and readable for engineers (usually not suited for non technical stakeholders and not localized); example: Service Unavailable

status int32

Possible values: >= 100 and < 600

The HTTP status code generated by the origin server for this occurrence of the problem.

detail string

A human readable explanation specific to this occurrence of the problem.

instance uri

An absolute URI that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.

Example (from schema)

{
  "title": "string",
  "status": 503,
  "detail": "Connection to database timed out",
  "instance": "string"
}

500

Unknown error

application/problem+json

Schema

Schema

title string

A short, summary of the problem type. Written in english and readable for engineers (usually not suited for non technical stakeholders and not localized); example: Service Unavailable

status int32

Possible values: >= 100 and < 600

The HTTP status code generated by the origin server for this occurrence of the problem.

detail string

A human readable explanation specific to this occurrence of the problem.

instance uri

An absolute URI that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.

Example (from schema)

{
  "title": "string",
  "status": 503,
  "detail": "Connection to database timed out",
  "instance": "string"
}

Loading...