Skip to main content
PUT
Save notice response sender

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

consumer
integer
required

Consumer account ID.

Body

application/json
terms_and_conditions
boolean
required

Must be accepted before sender details are saved.

Example:

true

sender_type
enum<string>

Present when the frontend uses a searched sender row.

Available options:
company,
creditor_profile
Example:

"company"

sender_id
integer

ID from GET /notice-responses/senders. Required with sender_type.

Example:

15

company_name
string

Required when creating a manual sender instead of using sender_type/sender_id.

Required string length: 3 - 30
Example:

"Manual Sender"

company_phone
string
Maximum string length: 255
Example:

"9005091111"

company_address1
string
Maximum string length: 255
Example:

"123 Sender St"

company_address2
string
Maximum string length: 255
Example:

"Suite 10"

company_city
string
Maximum string length: 255
Example:

"Dallas"

company_state
string
Example:

"TX"

company_zip
string
Pattern: ^\d{5}(?:-\d{4})?$
Example:

"75001"

company_email
string<email>
Maximum string length: 255
Example:

"manual-sender@example.com"

company_url
string<uri>

URL is normalized to https:// when the scheme is omitted.

Maximum string length: 255
Example:

"https://manual-sender.test"

Response

Sender details saved.

message
string
required
Examples:

"Notice response started."

"Sender details saved."

"Account details saved."

"Notice uploaded."

data
object
required
Last modified on July 19, 2026