Skip to main content
Altcraft Docs LogoAltcraft Docs Logo
User guideDeveloper guideAdmin guide
Company siteHelp center
English
  • Русский
  • English
v72
  • v74
  • v73
  • v72
Login
  • User API documentation
  • API interaction
  • Matching
  • Profiles
  • Databases
  • Resources
  • Segments
  • Static segments
  • Suppression lists
  • Templates and fragments
  • Campaigns
  • Automation scenarios
    • Engage profile in scenario
    • Import and engage profile in scenario
    • Batch import and engage profiles in a scenario
    • Task for batch import and engaging profiles in the scenario
    • Get scenarios list
    • Activate scenario
    • Deactivate scenario
  • Promo codes
  • Goals
  • Application push notifications
  • Market
  • Analytic reports
  • SendersDevv71
  • External datatables queries
  • Objects
  • Miscellaneous
  • Importing the API collection in Postman
  • List of API endpoints
  • SDK
This is documentation for Altcraft Platform v72. This documentation is no longer maintained.
The information for up-to-date platform version at this page is available (v74).
  • Automation scenarios
  • Task for batch import and engaging profiles in the scenario
Documentation for version v72

Task for batch import and engaging profiles in the scenario

Description​

Adding or updating multiple profiles and then sending them to the scenario. Returns a response with the task id without waiting for execution.

note

The request body is limited by default to 10mb, exception: files are 100mb.

It is not recommended to transmit more than 10,000 profiles per request.

URL​

Method: POST

https://example.com/api/v1.1/workflows/import_and_start_batch_task

Request parameters​

ParameterTypeExampleRequiredDescription
tokenstring"abcdefghijklmnqrstuvwxyz"YesAPI token
formatstring"json"NoData format (by default - "json")
workflow_idInt1YesWorkflow identifier
matchingString"email"YesProfile matching mode.
By default – email.
profile_idString"5f19953a03e4227216278ba4""matching":"profile_id"Profile identifier
emailString"importStart9219@example.com""matching":"email" - from profile or subscriptions

"matching":"email_profile" - only from profile
Email
phoneString"+79001234567""matching":"phone"Phone number
field_nameString"CRM_ID""matching":"custom"The name of the custom profile field for search.
field_valueAny"12345""matching":"custom"The value of the custom profile field for search.

Search by combination of tags is available. Values are recorded as a string: "tag-1, tag-2".
dataObject
{
   "_fname": "John",
   "_lname": "Doe"
}
NoProfile data, including subscriptions
skip_triggersBooltrueNoSkip triggers and workflows activated by import and update actions
By default – false
skip_invalid_subscriptionsBooltrueNoSkip invalid subscriptions
By default – false
detect_geoBooltrueNoDetect geolocation by IP (it is detected by data from the fields _regip or _ip)
contentObject
"content":{
   "one": "My email = importStart9219@example.com",
   "two": "Timestamp: 1595512477",
   "three": "Three"
}
NoAdditional data to be used in the message template as {apicontent.fieldname} variable. The variable can be used in the "API call" and "API content filter" nodes
custom_dataJSON object
"custom_data": {
   "field": "value",
}
NoAdd some data to be used in Action hooks. The parameter can be passed either at the root of the request or separately in each data object.
attacharray of {name, flie_key, data, mimetype}
NoFile to attach to an Email message (only for Email triggers)
custom_requestJSON object
{
"email": {
"$in": [
"asd@dsfsd.com",
"zxcv@sdfsd.com"
]
}
}
When no matching
specified
Custom MongoDB database query

Returned parameters​

ParameterTypeDescription
error_textstringError text
errorintError code
task_idstringTask identifier

Request example – "matching":"email"​

  • JSON
  • XML
{
"token": "abcdefghijklmnqrstuvwxyz",
"workflow_id": 12,
"matching": "email",
"data": [
{
"data": {
"_fname": "Herbert",
"_lname": "Lambert",
"email": "example@example.com",
"phones": "+79862014852"
}
},
{
"data": {
"_fname": "Bert",
"_lname": "Lambert",
"email": "example@example.com",
"phones": "+79862014853"
}
}
]
}
<xml>
<token>abcdefghijklmnqrstuvwxyz</token>
<workflow_id>12</workflow_id>
<matching>email</matching>
<data>
<_fname>Herb</_fname>
<_lname>Limbert</_lname>
<email>example@example.com</email>
<phones>+79847076617</phones>
</data>
<data>
<_fname>Bert</_fname>
<_lname>Limbert</_lname>
<email>example@example.com</email>
<phones>+79817076617</phones>
</data>
</xml>

Request example – "matching":"custom"​

  • JSON
  • XML
{
"token": "abcdefghijklmnqrstuvwxyz",
"workflow_id": 12,
"matching": "custom",
"field_name": "New_field_7",
"data": [
{
"data": {
"_fname": "Kristina",
"_lname": "Lambert",
"email": "example@example.com",
"phones": "+79568150395",
"New_field_7": "00015"
}
},
{
"data": {
"_fname": "Christopher",
"_lname": "Lambert",
"email": "example@example.com",
"phones": "+79568150396",
"New_field_7": "00016"
}
}
]
}
<xml>
<token>abcdefghijklmnqrstuvwxyz</token>
<workflow_id>12</workflow_id>
<matching>custom</matching>
<field_name>CRM_ID</field_name>
<data>
<_fname>Naomy</_fname>
<_lname>Depp</_lname>
<email>example@example.com</email>
<phones>+798144890880</phones>
<CRM_ID>7830</CRM_ID>
</data>
<data>
<_fname>Nataly</_fname>
<_lname>Depp</_lname>
<email>example@example.com</email>
<phones>+73755334351</phones>
<CRM_ID>0934</CRM_ID>
</data>
</xml>

Response example​

  • JSON
  • XML
{
"error": 0,
"error_text": "Successful operation",
"task_id": "30421978-7f6d-4f39-913f-fb6cad8e2477"
}
<xml>
<error>0</error>
<error_text>Successful operation</error_text>
<task_id>675231ce-63b4-4bca-a153-10d87b938d26</task_id>
</xml>

Example of a response when a request restriction is triggered​

  • JSON
  • XML
{
"error": 400,
"error_debug": "http: request body too large",
"error_text": "Invalid request"
}
<xml>
<error>400</error>
<error_debug>http: request body too large</error_debug>
<error_text>Invalid request</error_text>
</xml>

Checking the status of the task​

URL​

Method: POST

https://example.com/api/v1.1/tasks/status

Request parameters​

ParameterTypeExampleRequiredDescription
tokenstring"abcdefghijklmnopqrstuvwxyz"YesAPI token
task_idstring"task_b2f9fk6a-2479-4a63-b592-f15d4e3b69c5"YesTask ID

Request example​

  • JSON
  • XML
{
"token": "abcdefghijklmnqrstuvwxyz",
"task_id": "task_b2f9fk6a-2479-4a63-b592-f15d4e3b69c5"
}
<xml>
<token>abcdefghijklmnqrstuvwxyz</token>
<task_id>task_b2f9fk6a-2479-4a63-b592-f15d4e3b69c5</task_id>
</xml>

Response example​

  • JSON
  • XML
{
"data": {
"status": "completed",
"progress": 100,
"result": {
"error": 0,
"error_text": "",
"result": [
{
"profile_id": "61e947333f62fc26d384452c"
},
{
"profile_id": "61e947333f62fc26d384452e"
}
]
}
},
"error": 0,
"error_text": "Successful operation"
}
<xml>
<data>
<status>completed</status>
<progress>100</progress>
<result>
<error>0</error>
<error_text></error_text>
<result>
<profile_id>61e947333f62fc26d384452c</profile_id>
</result>
<result>
<profile_id>61e947333f62fc26d384452e</profile_id>
</result>
</result>
</data>
<error>0</error>
<error_text>Successful operation</error_text>
</xml>
Last updated on Aug 20, 2024
Previous
Batch import and engage profiles in a scenario
Next
Get scenarios list
  • Description
  • URL
  • Request parameters
  • Returned parameters
  • Request example – "matching":"email"
  • Request example – "matching":"custom"
  • Response example
  • Example of a response when a request restriction is triggered
  • Checking the status of the task
    • URL
    • Request parameters
    • Request example
    • Response example
© 2015 - 2025 Altcraft, LLC. All rights reserved.