Skip to main content
POST
https://www.dncscrub.com
/
app
/
main
/
rpc
/
ebr
EBR and Consent Master
curl --request POST \
  --url https://www.dncscrub.com/app/main/rpc/ebr \
  --header 'Content-Type: <content-type>' \
  --header 'loginId: <loginid>' \
  --data '
{
  "keepBetterEBR": 123,
  "ebrList": [
    {
      "phoneNumber": "<string>",
      "type": "<string>",
      "dateOfLastContact": "<string>",
      "dateObligationEnds": "<string>",
      "referenceNum": "<string>",
      "brand": "<string>",
      "email": "<string>"
    }
  ]
}
'
{
  "success": true
}
An Existing Business Relationship (EBR) provides an exemption to DNC rules under certain conditions. The EBR API allows you to add and manage EBR records for phone numbers. In addition the EBR API can be used to store Consent. A consent record is a Permission “P” EBR record. You should ensure you have the proper consent from the customer for the customer’s jurisdiction before sending this. This will allow you to contact the customer for the purposes of marketing and sales until you remove the Permission EBR or Add to Internal DNC.

​
Request

​
Headers

​
loginId
string
required
Your API Key
​
Content-Type
string
required
Must be application/json

​
Request Body

​
keepBetterEBR
integer
When set to 1, if an EBR record already exists for the phone number being added and the existing EBR is “better” than the one being added, the existing EBR will not be overwritten. Federal EBR expiration dates are used to determine which EBR is better (longer remaining validity = better).
​
ebrList
array
required
Array of EBR records to add.

​
Example Request

curl --location 'https://www.dncscrub.com/app/main/rpc/ebr' \
  --header 'loginId: YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
    "ebrList": [
      {
        "phoneNumber": "5039367187",
        "type": "I",
        "dateOfLastContact": "11/11/2020"
      }
    ]
  }'

{
  "success": true
}

​
Add Multiple EBRs

Add multiple EBR records in a single request: 
curl --location 'https://www.dncscrub.com/app/main/rpc/ebr' \
  --header 'loginId: YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
    "ebrList": [
      {
        "phoneNumber": "5039367187",
        "type": "S",
        "dateOfLastContact": "06/14/2023"
      },
      {
        "phoneNumber": "7072842774",
        "type": "I",
        "dateOfLastContact": "07/02/2023"
      }
    ]
  }'
This adds:
  1. Phone 5039367187 with a Sale EBR dated 06/14/2023
  2. Phone 7072842774 with an Inquiry EBR dated 07/02/2023

​
Multiple Phone Numbers Per Record

You can also add the same EBR to multiple phone numbers in one record: 
{
  "ebrList": [
    {
      "phoneNumber": "5039367187,7075276405",
      "type": "I",
      "dateOfLastContact": "11/11/2020"
    }
  ]
}

​
Preserve Better EBR Records

Use keepBetterEBR to prevent overwriting existing EBR records that have longer remaining validity: 
{
  "keepBetterEBR": 1,
  "ebrList": [
    {
      "phoneNumber": "5039367187",
      "type": "I",
      "dateOfLastContact": "11/11/2024"
    }
  ]
}
When keepBetterEBR is set to 1, the system compares federal and state EBR expiration dates. If the existing EBR expires later than the new one would, the existing record is preserved. This is useful when importing EBR data to avoid accidentally downgrading your compliance coverage.

​
Response

Status CodeMeaning
200Success
4xxError - response body contains the reason

​
EBR Types

TypeDescription
SSale/Purchase
IInquiry
PPermission
TTrial (currently only for Newspaper Trials in North Dakota)

​
EBR Expiration

EBR exemptions expire based on federal rules:
EBR TypeExpiration Period
Sale/Purchase (S)18 months from date of last transaction
Inquiry (I)3 months from date of inquiry
State rules may vary. Some states have shorter exemption periods or additional requirements.

​
Best Practices

Use the referenceNum parameter to store your internal tracking ID for audit purposes.
The dateOfLastContact should be the actual date of the business relationship event, not the current date.
Select the appropriate EBR type - using the wrong type could result in compliance issues.
When bulk importing EBR records, use keepBetterEBR: 1 to preserve existing records with longer validity periods and avoid accidentally reducing your compliance coverage.