Do You Need a Developer to Use the Apricot API? A Skills Guide for Nonprofits

Your Apricot data no longer has to stay locked inside Apricot. With the new public API, your nonprofit can connect Apricot to nearly any other system you rely on, so information moves between them automatically instead of by copy and paste. This API (which is simply a doorway that lets two software systems pass information back and forth automatically) was, until recently, closed to outside developers. Now it’s open, which opens up a lot of possibilities.
The one thing worth knowing up front is that connecting to Apricot isn’t generic developer work. It takes someone who understands the platform, so a good part of this comes down to who’s doing the building. This guide walks through what those connections can do, what it takes to build one, and how to tell whether that’s a job for your team or a job to hand off.

Who Has Access to the Apricot API?

Access depends on your Bonterra license tier. According to Bonterra’s documentation, the API is available to Apricot Enterprise (formerly called 360) and Apricot Pro (formerly called Core) customers. Enterprise includes it. Pro customers can add it by purchasing Bonterra’s Data Integration option, which also covers automated file imports. If you’re not sure which tier you have, your account manager can tell you.

What Problem Are You Actually Solving?

Before you get into the how, get clear on the why. If information moved into or out of Apricot on its own, on a schedule, without anyone touching it, what would that free up for your team?
This is the same discipline good Apricot setup requires. You don’t put every field on a Tier 1 form just because you can. You think about structure first.
Connections raise the stakes, because complexity adds up over time. An automation that quietly watches for one thing and sends a notification is a very different animal from a two-way connection that keeps two systems in step, each updating the other. And when two systems are tied together, either one can change and break the link. Something will eventually go wrong, and someone has to notice and fix it. So define the problem before the solution, and pick the simplest version that solves it. The most sophisticated option is rarely the right one.
Keep in mind, too, that not every automation needs a custom connection. Plenty of what nonprofits want can be handled without one, and even the ones that do use the API don’t have to be complicated.
One practical thing to check early: the API handles Apricot’s core features well, but some of its newer or more specialized areas can’t be connected this way yet. If your whole project depends on automating something unusual, confirm it’s actually supported before you build a plan around it. You can check Bonterra’s developer documentation.

What Skills Do You Need to Use the Apricot API?

Coding ability isn’t the first thing to look at. The better question is whether you’re already doing a version of this work without calling it that. A few signs you’re closer than you’d guess:
  • You’re strong in Results Reporting. It’s the closest cousin to this work inside Apricot. Building advanced reports means understanding how your data is structured and how the pieces relate, and that’s the same picture a connection depends on.
  • You reshape data between systems. If you regularly wrangle Excel files so Apricot will accept them, or reformat Apricot reports so another program will, you’re already doing the core task. Connecting two systems is mostly translation.
  • You can make sense of JSON, or you’re willing to learn. JSON is just the format information takes as it travels between systems. It looks like code and puts people off, but think of it as a spreadsheet folded into a compact shape. You don’t have to write it. You only need to look at a chunk and recognize “that’s a person, that’s their ID, that’s their status.” If that feels doable, you’re most of the way there.
  • You’ve used a tool like Zapier. Zapier, Make, and Microsoft Power Automate let you build simple automations by pointing and clicking instead of coding. If you’ve ever set one up to watch your inbox for a certain subject line and drop a row into a spreadsheet, you’ve done a smaller version of this already. Our post on low-code integrations for Apricot and ETO shows what that looks like.
  • You think in “if this, then that.” You don’t need a computer science background, just the habit of asking what should happen when the information shows up looking different than you expected.
There’s one more sign that isn’t a skill at all: interest. Nobody starts out knowing this, and the people who get good at it are the ones curious enough to keep going after the first try flops. If that list left you a little intrigued, that matters more right now than what you already know. If it left you tired, that tells you something too.

What Happens When Your Data Isn’t Clean?

This is the question that separates automations that last from the ones that quietly fall apart a few months in.
Your data will never be perfect, and an automation has to be built to handle the mess. Staff will type things in the wrong place. Fields you were sure were required will somehow turn up empty. Someone will paste in a phone number with letters in it. Every one of those is a situation your automation has to know how to handle, and that means deciding ahead of time what should happen. Skip the record? Flag it for review? Fill in a default? Stop everything and send an alert?
Building for the tidy version is easy. Building for the messy version is where most of the real thinking goes, and it’s the difference between an automation your team trusts and one they quietly stop relying on. Think through the messy cases before you build, and assume your data is messier than you expect, because it usually is.

Should You Build In-House or Hire Out?

There are really three ways to go about this, and the right one depends on what your team can take on and how much you want to keep in-house.

Option 1: Build it in-house. If someone on your staff has the skills and the time, this is your strongest long-term answer. It costs less, and the know-how stays with you. Outside developers finish the job and move on. Your automations don’t. The catch is capacity: being able to build something and having the hours to keep it running for the next three years aren’t the same thing.

Option 2: Hire one outside developer for the whole thing. This is the simplest to manage, since one person owns the entire job. The thing to watch for is fit. A developer who’s connected systems before can usually learn a new one, but Apricot isn’t a generic system, and connecting to it well takes someone who knows how it actually behaves. That’s why Bonterra works through certified partners instead of pointing organizations at just any developer. Someone who already knows the platform works faster, costs less, and makes fewer mistakes, because they’ve already run into its quirks.

Option 3: One developer for each side. Plenty of nonprofit projects land here. One person handles the Apricot side, another handles the system you’re connecting it to, and someone coordinates how the two sides communicate. This makes sense when the other system is as specialized as Apricot and no single person knows both ends well.

Whichever route you pick, you can also bring in an expert to advise rather than build. That’s often where we come in; on some projects Treadwell does the building, and on others we’re the Apricot specialist guiding an in-house team or an outside developer so they don’t lose a month to trial and error. And if you want to grow this skill on your team rather than hand it off for good, say so while you’re hiring, and find a partner willing to build and to teach.

Apricot API Skills – The Path Forward

These questions aren’t really about the API. They’re about your team, your capacity, and whether automation is even the right answer to the problem in front of you. Sometimes it isn’t, and that’s a fine outcome. A setup change, a tweak to how your team works, or a different way of framing the whole thing can get you most of the way there for a fraction of the cost. We’d rather help you understand all of your options than sell you a connection you didn’t need.

And if the answer turns out to be that you can do this yourself, that’s worth knowing too. Some of the best conversations we have end with someone walking away with a plan and no invoice. Whether you want a fully custom connection or the training to build it yourselves, the place to start is a conversation, not a proposal.

Need help with Apricot API or automation work?

Treadwell is Bonterra’s only certified implementation partner for both Apricot and ETO software. Treadwell also develops the most advanced automations using Apricot’s built-in API, SFTP, and reporting capabilities.

SUBSCRIBE TO
our newsletter

Stay up to date with the latest Treadwell and industry news .