The API Version 4 category contains all posts related to using and understanding version 4 of Bronto’s API
Those of you who use Workflow Automation, that snazzy drag-and-drop canvas for visually architecting campaign workflows, know that there is a set of triggers we give you in the Workflow Toolbar to initiate your workflows.
If you have been sending personalized messages to your contacts, then you already understand how useful this marketing technique can be. If you would like to start exploring how to use personal information you have about your contacts, take a look at this post by Frank Chapman on Getting Personal With Your Contacts.
There are a lot of cool things you can do with version 4 of our API. Outside of the neat custom things that can be done, lies the core functionality of the API. Of these core functions is the ability to send email. In this post, I'll go over how to send email using version 4 of our API, and provide some example code to help you get started.
If you are using the API and want a quick way to find out which contacts are on a particular segment, this post is for you.
One of the first things you will want to do with your Bronto account is add contacts. Using the API, you can add new contacts that you have in a system outside of Bronto. The Bronto API allows you to create up to 5000 contacts in a single request.
If you use the API to add or update your contacts, you may have wondered what that customSource property in the contactObject was. Wonder no more. This post will explain what the customSource property is.
I think we all know the old adage to wait 30 minutes after you eat before going into the water isn't necessary, but the idea is a good one. Sometimes it is best to wait. This applies to adding objects using the API.
It's sad, but true. Occassionally, there are times when a contact may no longer want to receive your messages. Bronto handles these "unsubscribes" for you, but if you are using the Bronto API, you may need to transfer this information to your other systems for reference. You can do this using the readContacts function.
If you have used the Agency Level API access with the Bronto API v3 in the past, and want to transition those powerful capabilities to your new API v4 integration, this post is for you.
Recently, there has been some confusion as to how version 4 our API handles timezones. In this post, I'll explain how timezones work in the Bronto API, and what you need to do to ensure that you are using the correct timezone.
Where In The World Is Bronto?
The default timezone used in the Bronto API is GMT (Greenwich Mean Time). For example, December 14 1984 12:14:37 would be 1984-12-14T12:14:37.