Create a New inApp

post https://api.indigitall.com/v2/inapp/campaign

Create a new inApp campaign. The user must have permissions to create inApp campaigns in that application

time	status	user agent
Retrieving recent requests…

Loading…

Body Params

new inApp's data

applicationId

integer

required

Application id

schemaId

integer

required

campaign schema id

name

string

required

campaign name

content

string

required

campaign Content web (html).
This content is filtered, so not all html tags are valid.

Tags:

['h1', 'h2', 'h3', 'h4', 'h5', 'h6', 'p', 'a', 'ul', 'ol', 'img', 'nl', 'li', 'b', 'i', 'strong', 'em', 'strike', 'code', 'hr', 'br', 'div', 'caption', 'pre', 'iframe', 'spam']

Attributes:

['href', 'align', 'alt', 'center', 'bgcolor', 'width', 'height', 'style', 'id', 'class', 'scr', 'name', 'target']

enabled

boolean

required

If campaign campaign is enabled

properties

object

required

campaign properties

filters

object

required

campaign filters

customData

array of strings | null

In this array, we define the name of the customizable variables to be used by the campaign

Ex:

["telephone", "age"]

customData

startDate

date-time | null

Start Date for campaign action. The format is ISO 8601, UTC-0

Ex:

2019-02-13T08:18:39.632Z

endDate

date-time | null

End Date for campaign action. The format is ISO 8601, UTC-0

Ex:

2019-02-13T08:18:39.632Z

metadata

string | null

Information necessary to representthe campaign in the edit interface.

This information is only stored, it is not used for any process in the backend.

cacheTtl

integer | null

≥ 600

In seconds. Time to live of the inapp cache on the user's device.

Once the cache lifetime has been exceeded, the device will consult the API to download the campaign again.

If null, a default value will be used.

Responses

Response body

object

statusCode

integer

required

Response code

message

string

required

Response message, usually OK

data

object

required

integer

required

campaign id

createdAt

string

required

Creation date. ISO date format - 8601

updatedAt

string

required

Update date. ISO date format - 8601

applicationId

integer

required

Application id

schemaId

integer

required

campaign Schema id

name

string

required

campaign name

contentUrl

string

required

campaign Content web (html).
This content is filtered, so not all html tags are valid.

Tags:

['h1', 'h2', 'h3', 'h4', 'h5', 'h6', 'p', 'a', 'ul', 'ol', 'img', 'nl', 'li', 'b', 'i', 'strong', 'em', 'strike', 'code', 'hr', 'br', 'div', 'caption', 'pre', 'iframe', 'spam']

Attributes:

['href', 'align', 'alt', 'center', 'bgcolor', 'width', 'height', 'style', 'id', 'class', 'scr', 'name', 'target']

enabled

boolean

required

If campaign is enabled

properties

object

required

campaign properties

Has additional fields

filters

object

required

campaign filters

startDate

date-time | null

Start Date for campaign action. The format is ISO 8601, UTC-0

Ex:

2019-02-13T08:18:39.632Z

endDate

date-time | null

End Date for campaign action. The format is ISO 8601, UTC-0

Ex:

2019-02-13T08:18:39.632Z

metadata

string | null

Information necessary to represent the campaign in the edit interface.

This information is only stored, it is not used for any process in the backend.

cacheTtl

integer | null

≥ 600

In seconds. Time to live of the inapp cache on the user's device.

Once the cache lifetime has been exceeded, the device will consult the API to download the campaign again.

If null, a default value will be used.

customData

array of strings | null

In this array, we define the name of the customizable variables to be used by the campaign

Ex:

["telephone", "age"]

customData

Language

Credentials

Header


xxxxxxxxxx
1
curl --request POST \
2
     --url https://api.indigitall.com/v2/inapp/campaign \
3
     --header 'accept: application/json' \
4
     --header 'content-type: application/json' \
5
     --data '{"enabled":true}'

Click Try It! to start a request and see the response here! Or choose an example:

application/json

201Created

400Parameters missing or not in right format

401Invalid credentials

403Operation forbidden for your user

500Server error