Bulk Contacts by Id

POST 
/contacts/bulk/id

The bulk endpoints offer an efficient way of importing/updating large amounts of contacts with just a single API call. When using the bulk id endpoint, the contacts are identified by id. If a contact doesn't already exist, it will be created. If it does exist, the contact found will be updated.

Contact bulk endpoints support bulk change of contact attributes for multiple contacts as well. To learn more about Attributes, go here.

Contact bulk endpoints support bulk change of pricing for multiple contacts as well. To learn more about Pricing, go here.

A single contact attributes can be modified as explained in Bulk resource attribute values by resource lookup key, but if it's needed to modify attributes for multiple contacts, this endpoint should be used.

Fields

Name	Required
contacts (array of contact objects)	yes
id	yes
debtorId (deprecated)	no
firstName	no
middleName	no
lastName	no
abbreviation	no
title	no
dateOfBirth	no
gender	no
ssn	no
phone	no
email	no
parent	no
pricelistAmount	no
pricelistPercentage	no
primaryLanguage	no
sourceId	no
source	only when sourceId is provided
attributes Read more about attributes	no
pricing Read more about pricing	no

Request

application/json

Body

contacts

object[]

Array [

abbreviation string

attributes

object[]

Array [

class string

name string

type string

value string

]

company string

dateOfBirth string

debtorId number

email string

firstName string

gender string

id number

language string

lastName string

middleName string

mobile string

parent

object

id number

phone string

primaryLanguage string

title string

]

Responses

200

Bulk Contacts by Id - 200

Response Headers

• Alt-Svc

  string

• Via

  string

• alt-svc

  string

• content-length

  string

• date

  string

• return-format

  string

• x-request-id

  string

application/json

Schema

Schema

data

object[]

Array [

action string

id number

key number

lookupKey string

success boolean

]

messages string[]
total number

Example (from schema)

{
  "data": [
    {
      "action": "update",
      "id": 25492,
      "key": 25492,
      "lookupKey": "id",
      "success": true
    }
  ],
  "messages": [
    "Completed"
  ],
  "total": 1
}

Bulk Contacts by Id - 200

{
  "data": [
    {
      "action": "update",
      "id": 25492,
      "key": 25492,
      "lookupKey": "id",
      "success": true
    }
  ],
  "messages": [
    "Completed"
  ],
  "total": 1
}

400

Bulk Contacts by Id - 400 (invalid schema)

Response Headers

• Alt-Svc

  string

• Via

  string

• alt-svc

  string

• content-length

  string

• date

  string

• return-format

  string

• x-request-id

  string

application/json

Schema

Schema

error

object

code number

messages string[]

moreInfo string

status number

type string

Example (from schema)

{
  "error": {
    "code": 10007,
    "messages": [
      "#/contacts/0: extraneous key [company] is not permitted"
    ],
    "moreInfo": "https://www.propel.us/docs/errors/10007",
    "status": 400,
    "type": "SchemaValidationException"
  }
}

Bulk Contacts by Id - 400 (invalid schema)

{
  "error": {
    "code": 10007,
    "messages": [
      "#/contacts/0: extraneous key [company] is not permitted"
    ],
    "moreInfo": "https://www.propel.us/docs/errors/10007",
    "status": 400,
    "type": "SchemaValidationException"
  }
}

Loading...