Skip to main content
POST
EBR and Consent Master
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 — use this type whenever a consumer opts in with express written consent (for example, a signed web consent form or a consent checkbox with the required disclosures). 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.
Handling a consumer who opted out and later opts back in? See Handling Opt-Outs and Opt-Ins for how Permission EBRs and the Internal DNC list interact.
To add or refresh EBR records and scrub numbers in a single request, use Scrub + Add EBR instead of calling this endpoint separately.

Request

Headers

string
required
Your API Key
string
required
Must be application/json

Request Body

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).
array
required
Array of EBR records to add.

Example Request

Add Multiple EBRs

Add multiple EBR records in a single request:
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:

Preserve Better EBR Records

Use keepBetterEBR to prevent overwriting existing EBR records that have longer remaining validity:
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

EBR Types

EBR Expiration

EBR exemptions expire based on federal rules:
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. In particular, opt-ins backed by express written consent must be sent as Permission (P) — a Sale or Inquiry EBR will not override an Internal DNC entry.
When bulk importing EBR records, use keepBetterEBR: 1 to preserve existing records with longer validity periods and avoid accidentally reducing your compliance coverage.