Move contact to another playbook
Moves a contact to a different playbook and creates a new submission.
Authorization
ApiKeyAuth API key generated from your Vayaflow dashboard Settings page
In: header
Path Parameters
The contact ID
Request Body
application/json
Target playbook ID
Response Body
application/json
application/json
application/json
application/json
package mainimport ( "fmt" "net/http" "io/ioutil" "strings")func main() { url := "https://api.vayaflow.com/api/v1/contacts/string/move-to-playbook" body := strings.NewReader(`{ "playbookId": "string" }`) req, _ := http.NewRequest("POST", url, body) req.Header.Add("Content-Type", "application/json") res, _ := http.DefaultClient.Do(req) defer res.Body.Close() body, _ := ioutil.ReadAll(res.Body) fmt.Println(res) fmt.Println(string(body))}{
"success": true,
"message": "string"
}{
"success": false,
"error": {
"code": "VALIDATION_ERROR",
"message": "Invalid input data",
"details": [
"string"
]
}
}{
"success": false,
"error": {
"code": "UNAUTHORIZED",
"message": "Authentication required"
}
}{
"success": false,
"error": {
"code": "NOT_FOUND",
"message": "Resource not found"
}
}Repost a failed contact
Retries delivery for a contact with status failed, rejected, or error. Two modes are supported: simple retry (resends with the same or provided delivery info, skips qualification) and modified retry (provide a modifiedPayload and playbookId to re-qualify with updated data). For simple retry, the previous delivery info is reused automatically if not provided.
Send contacts to auto dialer
Schedules one or more contacts for the next available auto-dialer call slot. Each contact is matched to its playbook's auto-dialer configuration, and the service determines the optimal call time based on the contact's timezone, the sequencing rules, and attempt history. Contacts that cannot be scheduled (e.g. inactive config, max attempts reached, excluded status) are reported in the failed array. Processes up to 200 contacts per request with controlled concurrency.