API and webhooks
Your CRM hands over your protected customers, your system picks up the companies that responded positively and the postal campaign addresses by itself, fetches the campaign report, and hears about every important event straight away.
This is how you ask about the call log in your own account, and how Apex answers. The addresses are made up.
How you connect it
You create a key in the account menu, your developer connects it using the reference, and from then on your systems keep in touch on their own.
- 1
You start with a test key
The account's Superuser or an Administrator creates the test key in the account menu, under API and webhooks. With a test key every call behaves as it would live, but nothing changes in the account, and reads return sample data.
- 2
Your developer works from the reference
Every call is described on trendizz.com/developers, with curl, JavaScript, Python and PHP examples, and five detailed guides are there too. With the test key your developer can also try the calls in the browser before connecting them.
- 3
Live, your systems do the work
With the live key the CRM hands over the protected customers and takes in the companies that replied positively, and the print shop downloads the postal addresses. Every call goes into the call log, every webhook into the delivery log. The live key works on a paid plan.
What goes across, in both directions
Your system can hand over protected customers, exclude companies and email addresses, take in the positive responders and the postal addresses, and fetch the campaign report.
The API hands over the results of your work: the companies that replied positively and the addresses of your postal campaigns. Every such handover also appears under My exports.
Why this is good for you
Protected customers are left in peace
When someone signs up or subscribes with you, your system hands them over as a protected customer that same minute, and no campaign writes to them. If they cancel, your system removes them, and the company can be contacted again.
The result lands where you work
A company that replied positively arrives in the CRM with its contacts, by webhook, as soon as Trendizz recognises the reply as positive. If the CRM was unreachable in the meantime, the next fetch makes up for whatever was missed.
Every step can be traced back
Every call and every webhook delivery is logged: when, with which key, what was requested and what came back. The account's Superuser and Administrators see the log in detail for 90 days, and Apex can also tell you what happened.
Access, limits, plans
- The API works with a live key on the paid plans, and with a test key on every plan, Free included. On the Free plan or after a missed payment, live calls and webhooks pause, the keys and endpoints are kept, and everything restarts on its own when you subscribe.
- One limit on every plan: 1,000 calls per hour per company, separately for the test key and the live key. A batch counts as one call.
- Each company has one test key and one live key, plus any number of report keys that only read the account and the campaign reports, so one can be given to an agency's system, for example. Keys are created by the account's Superuser or an Administrator, and a key works with its creator's rights. After a new live key is created, the old one keeps working for 7 more days. If the creator leaves the team or loses the Administrator role, the key is kept but rejects every call until the Superuser or an Administrator takes it over.
- With a test key every call behaves as it would live, but nothing changes in the account, and reads return sample data, on every plan.
- No campaign writes to a protected customer, not even one aimed at existing customers. Load the companies you do want to write to into a campaign, for example a repeat-purchase campaign, and mark as protected the ones you want left in peace.
- Finding, analysing and contacting new companies happens in Apex, inside Trendizz; the API hands the results over to your system. When you mark a company as won, your system is notified by webhook.
API reference, with try-it-out
Every call with curl, JavaScript, Python and PHP examples, five detailed guides, the error codes and the event types. With the test key it can also be tried out in the browser.
Open the referenceRelated features
- Existing customers and past contactsYou load your own partners, Apex writes to them too, and each one gets its own record.
- Company recordWhat Apex read from the website, the full story and the suggested next step.
- Event logFor every company you can see who did what and when. Apex can also search across many companies, one colleague or a period of time.
More features
- How you get started with ApexFrom signing in to the first letter: what your part is, and what Apex does.
- Apex knows your companyFrom your introduction it knows what you offer and to whom, and at each target company it puts forward what matters there.
- A target group from the marketApex proposes it, you approve it, and Apex selects company by company.
- Morning reportWhat came in overnight, who is waiting for an offer, what expires today, and what your first step should be.
- Apex handles the repliesApex sorts every reply and decides what it handles itself and what becomes a task for someone.
- Team performanceSystem, group, person: five metrics, with change and trend, for everyone.
- Groups and accessA separate campaign per group, even per language area. A member sees their own group, a leader sees them all.
- Joiners and leaversA new colleague has a chat and Apex brings them on board. When someone leaves or goes on holiday, Apex hands over their tasks from a single sentence.
- Market MirrorWhy you win, why you lose, by segment, from your closed deals.
- Expanding into a new marketThe same target group in several countries, letters in the target market's language, with local holidays and time zone.
Try it free.
Ask Apex. It answers in your own account, tailored to your company.