Blackleaf Help Center
Platform and texting FAQ
Direct answers about Blackleaf, customer messaging, contacts, campaigns, delivery, compliance, billing, and troubleshooting.
Compliance information is general guidance, not legal advice. Requirements vary by jurisdiction, sender, content, and use case.
integrations
Integrations and API
POS data, synchronization, matching, and API access.
What can an integration sync?
Short answer: Depending on the connector, Blackleaf can receive customer, transaction, loyalty, order, product, and event data. Fields and timing vary by integration.
Is POS data synchronized in real time?
Short answer: Not always. Timing depends on the connector, source, data type, and processing state. Use the integration’s documented cadence for time-sensitive rules.
Can an integration create duplicate contacts?
Short answer: Blackleaf matches available identifiers, but missing, changed, shared, or inconsistent identifiers can produce separate records. Names alone are not unique.
Does being a POS customer mean someone consented to texts?
Short answer: No. Customer/transaction data and SMS consent are separate.
Where are the API docs?
Short answer: Use the public Blackleaf API documentation. Keep credentials secret and never put a key in browser code, a public repository, or an FAQ.