Create Customer Contact

post

https://server:port/spl/rest/apis/customer/interactions/customerContacts/

Request

There are no request parameters for this operation.

Supported Media Types
Request Body - application/xml ()
Root Schema : schema
Type: object
Show Source
Nested Schema : account
Type: object
Show Source
  • Maximum Length: 10
    Account ID displays the account's unique, system-generated ID. The account must be associated to the person when the contact is created or updated. There should be no value if the Customer Contact Type indicates that an account is not allowed on customer contacts of this type.
    Example: 5922116763
Nested Schema : characteristics
Type: object
Show Source
Nested Schema : contactDetail
Type: object
Show Source
  • Maximum Length: 10
    Contact Detail ID is a system-assigned, unique identifier of the person contact associated with the customers preferred contact method.
Nested Schema : customerContactType
Type: object
Show Source
  • Maximum Length: 4
    Contact Class categorizes customer contacts into larger groupings for reporting purposes.
    Example: CSS
  • Maximum Length: 12
    Every customer contact has a Contact Type that classifies the record for reporting purposes. Every contact type, in turn, references a Contact Class. The customer contact type controls the relationship validation among person, account, and premise. You can set up a customer contact type to generate a form letter whenever a customer contact of this type is added. In fact, this is the only way to generate a letter in the system.
    Example: ACCESS
Nested Schema : letterTemplate
Type: object
If the customer contact references a customer contact type that, in turn, references a letter template, the template controls the type of information that is merged into the 'form letter' and how the letter is physically produced.
Show Source
  • Maximum Length: 12
    If the customer contact references a customer contact type that, in turn, references a letter template, the template controls the type of information that is merged into the 'form letter' and how the letter is physically produced.
Nested Schema : logs
Type: object
Show Source
Nested Schema : person
Type: object
Show Source
  • Maximum Length: 10
    Person ID displays the associated person's unique, system-generated ID. If the customer contact is Person-based the Person ID cannot be changed. There should be no value if the Customer Contact Type indicates that a person is not allowed on customer contacts of this type.
    Example: 5775933103
Nested Schema : premise
Type: object
Show Source
  • Maximum Length: 10
    Premise ID field displays the associated premise's unique, system-generated ID. If the customer contact is Premise-based the Premise ID cannot be changed. There should be no value if the Customer Contact Type indicates that a premise is not allowed on customer contacts of this type.
Nested Schema : user
Type: object
Show Source
  • Maximum Length: 8
    User ID of the user who created the contact.
    Example: SYSUSER
Nested Schema : _data
Type: array
Show Source
Nested Schema : items
Type: object
Show Source
Nested Schema : characteristicType
Type: object
Show Source
Nested Schema : characteristicValue
Type: object
Show Source
Nested Schema : _data
Type: array
Show Source
Nested Schema : items
Type: object
Show Source
  • assignedToUser
  • Maximum Length: 2000
    Log Entry can be used to describe the reason for the log entry.
  • toDoRole
  • Trigger Business Process is a true or false value for reminders.
  • Trigger Date is only used if you want the system to remind a user about this customer contact on a future date. The system will create a To Do entry to remind the user about the customer contact. This value defines the latest date on which the To Do entry should be created because the background process that's responsible for creating these To Do entries has a parameter called Lead Time that is used to define the number of days before the Trigger Date that the To Do entry should be created.
  • user
  • Minimum Value: -99999
    Maximum Value: 99999
    Version number is used for internal concurrency checks.
    Example: 1
Nested Schema : assignedToUser
Type: object
Show Source
Nested Schema : toDoRole
Type: object
Show Source
Nested Schema : user
Type: object
Show Source
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
Nested Schema : account
Type: object
Show Source
  • Maximum Length: 10
    Account ID displays the account's unique, system-generated ID. The account must be associated to the person when the contact is created or updated. There should be no value if the Customer Contact Type indicates that an account is not allowed on customer contacts of this type.
    Example: 5922116763
Nested Schema : characteristics
Type: object
Show Source
Nested Schema : contactDetail
Type: object
Show Source
  • Maximum Length: 10
    Contact Detail ID is a system-assigned, unique identifier of the person contact associated with the customers preferred contact method.
Nested Schema : customerContactType
Type: object
Show Source
  • Maximum Length: 4
    Contact Class categorizes customer contacts into larger groupings for reporting purposes.
    Example: CSS
  • Maximum Length: 12
    Every customer contact has a Contact Type that classifies the record for reporting purposes. Every contact type, in turn, references a Contact Class. The customer contact type controls the relationship validation among person, account, and premise. You can set up a customer contact type to generate a form letter whenever a customer contact of this type is added. In fact, this is the only way to generate a letter in the system.
    Example: ACCESS
Nested Schema : letterTemplate
Type: object
If the customer contact references a customer contact type that, in turn, references a letter template, the template controls the type of information that is merged into the 'form letter' and how the letter is physically produced.
Show Source
  • Maximum Length: 12
    If the customer contact references a customer contact type that, in turn, references a letter template, the template controls the type of information that is merged into the 'form letter' and how the letter is physically produced.
Nested Schema : logs
Type: object
Show Source
Nested Schema : person
Type: object
Show Source
  • Maximum Length: 10
    Person ID displays the associated person's unique, system-generated ID. If the customer contact is Person-based the Person ID cannot be changed. There should be no value if the Customer Contact Type indicates that a person is not allowed on customer contacts of this type.
    Example: 5775933103
Nested Schema : premise
Type: object
Show Source
  • Maximum Length: 10
    Premise ID field displays the associated premise's unique, system-generated ID. If the customer contact is Premise-based the Premise ID cannot be changed. There should be no value if the Customer Contact Type indicates that a premise is not allowed on customer contacts of this type.
Nested Schema : user
Type: object
Show Source
  • Maximum Length: 8
    User ID of the user who created the contact.
    Example: SYSUSER
Nested Schema : _data
Type: array
Show Source
Nested Schema : items
Type: object
Show Source
Nested Schema : characteristicType
Type: object
Show Source
Nested Schema : characteristicValue
Type: object
Show Source
Nested Schema : _data
Type: array
Show Source
Nested Schema : items
Type: object
Show Source
  • assignedToUser
  • Maximum Length: 2000
    Log Entry can be used to describe the reason for the log entry.
  • toDoRole
  • Trigger Business Process is a true or false value for reminders.
  • Trigger Date is only used if you want the system to remind a user about this customer contact on a future date. The system will create a To Do entry to remind the user about the customer contact. This value defines the latest date on which the To Do entry should be created because the background process that's responsible for creating these To Do entries has a parameter called Lead Time that is used to define the number of days before the Trigger Date that the To Do entry should be created.
  • user
  • Minimum Value: -99999
    Maximum Value: 99999
    Version number is used for internal concurrency checks.
    Example: 1
Nested Schema : assignedToUser
Type: object
Show Source
Nested Schema : toDoRole
Type: object
Show Source
Nested Schema : user
Type: object
Show Source
Back to Top

Response

Supported Media Types

200 Response

Success response
Body ()
Root Schema : C1-CustCntct
Type: object
Show Source
Nested Schema : account
Type: object
Show Source
  • Maximum Length: 10
    Account ID displays the account's unique, system-generated ID. The account must be associated to the person when the contact is created or updated. There should be no value if the Customer Contact Type indicates that an account is not allowed on customer contacts of this type.
    Example: 5922116763
Nested Schema : characteristics
Type: object
Show Source
Nested Schema : contactDetail
Type: object
Show Source
  • Maximum Length: 10
    Contact Detail ID is a system-assigned, unique identifier of the person contact associated with the customers preferred contact method.
Nested Schema : customerContactType
Type: object
Show Source
  • Maximum Length: 4
    Contact Class categorizes customer contacts into larger groupings for reporting purposes.
    Example: CSS
  • Maximum Length: 12
    Every customer contact has a Contact Type that classifies the record for reporting purposes. Every contact type, in turn, references a Contact Class. The customer contact type controls the relationship validation among person, account, and premise. You can set up a customer contact type to generate a form letter whenever a customer contact of this type is added. In fact, this is the only way to generate a letter in the system.
    Example: ACCESS
Nested Schema : letterTemplate
Type: object
If the customer contact references a customer contact type that, in turn, references a letter template, the template controls the type of information that is merged into the 'form letter' and how the letter is physically produced.
Show Source
  • Maximum Length: 12
    If the customer contact references a customer contact type that, in turn, references a letter template, the template controls the type of information that is merged into the 'form letter' and how the letter is physically produced.
Nested Schema : logs
Type: object
Show Source
Nested Schema : person
Type: object
Show Source
  • Maximum Length: 10
    Person ID displays the associated person's unique, system-generated ID. If the customer contact is Person-based the Person ID cannot be changed. There should be no value if the Customer Contact Type indicates that a person is not allowed on customer contacts of this type.
    Example: 5775933103
Nested Schema : premise
Type: object
Show Source
  • Maximum Length: 10
    Premise ID field displays the associated premise's unique, system-generated ID. If the customer contact is Premise-based the Premise ID cannot be changed. There should be no value if the Customer Contact Type indicates that a premise is not allowed on customer contacts of this type.
Nested Schema : user
Type: object
Show Source
Nested Schema : _data
Type: array
Show Source
Nested Schema : items
Type: object
Show Source
Nested Schema : characteristicType
Type: object
Show Source
Nested Schema : characteristicValue
Type: object
Show Source
Nested Schema : _data
Type: array
Show Source
Nested Schema : items
Type: object
Show Source
Nested Schema : assignedToUser
Type: object
Show Source
Nested Schema : toDoRole
Type: object
Show Source
Nested Schema : user
Type: object
Show Source

400 Response

Bad Request
Body ()
Root Schema : problemDetailDocument
Type: object
Show Source
  • Maximum Length: 60
    The long message description from the Oracle Utilities Application Framework in CDATA format.
  • Minimum Value: 0
    Maximum Value: 9999
    The HTTP Status code for the error.
  • Maximum Length: 60
    Fully qualified URL consisting of the Base URI Timestamp of error in ISO format, the User used for the transaction, the Message Category within Oracle Utilities Application Framework, the Message Number within Oracle Utilities Application Framework, the Request URL and the HTTP method used for the transaction.
  • Maximum Length: 60
    URL of the format "A/message/X/Y" where A is the base URI, X is the Message Category and Y is the Message Number within Oracle Utilities Application Framework.
  • serverMessage
  • Maximum Length: 60
    The stack trace shows where the error occurs during the execution of a program.
  • Maximum Length: 60
    Fully qualified error message from Oracle Utilities Application Framework in CDATA format.
Nested Schema : serverMessage
Type: object
Show Source
  • Maximum Length: 60
    Delimited sequence of programs called.
  • Maximum Length: 60
    The long message description from the Oracle Utilities Application Framework in CDATA format.
  • Minimum Value: 0
    Maximum Value: 0
    Message Category within Oracle Utilities Application Framework.
  • Minimum Value: -99999
    Maximum Value: 99999
    Message Number within Oracle Utilities Application Framework.
  • Maximum Length: 60
    Fully qualified error message from Oracle Utilities Application Framework in CDATA format.
  • Maximum Length: 60
    Name of the program that encountered the error.

500 Response

Internal Server Error
Body ()
Root Schema : problemDetailDocument
Type: object
Show Source
  • Maximum Length: 60
    The long message description from the Oracle Utilities Application Framework in CDATA format.
  • Minimum Value: 0
    Maximum Value: 9999
    The HTTP Status code for the error.
  • Maximum Length: 60
    Fully qualified URL consisting of the Base URI Timestamp of error in ISO format, the User used for the transaction, the Message Category within Oracle Utilities Application Framework, the Message Number within Oracle Utilities Application Framework, the Request URL and the HTTP method used for the transaction.
  • Maximum Length: 60
    URL of the format "A/message/X/Y" where A is the base URI, X is the Message Category and Y is the Message Number within Oracle Utilities Application Framework.
  • serverMessage
  • Maximum Length: 60
    The stack trace shows where the error occurs during the execution of a program.
  • Maximum Length: 60
    Fully qualified error message from Oracle Utilities Application Framework in CDATA format.
Nested Schema : serverMessage
Type: object
Show Source
  • Maximum Length: 60
    Delimited sequence of programs called.
  • Maximum Length: 60
    The long message description from the Oracle Utilities Application Framework in CDATA format.
  • Minimum Value: 0
    Maximum Value: 0
    Message Category within Oracle Utilities Application Framework.
  • Minimum Value: -99999
    Maximum Value: 99999
    Message Number within Oracle Utilities Application Framework.
  • Maximum Length: 60
    Fully qualified error message from Oracle Utilities Application Framework in CDATA format.
  • Maximum Length: 60
    Name of the program that encountered the error.
Back to Top