Back

Introducing our new API for project automation

Written by

Sarah Nguyen

Published on

Sep 12, 2025

Why an API became inevitable

For most of the platform’s life, interaction happened only through the interface. That was enough at first. But as teams grew, their requests became louder and more complex. They wanted automation: creating projects automatically, syncing metrics into dashboards, or connecting workflows across tools. Without an API, every request ended with the same limitation—manual effort.

The shift came when we realized that not offering an API meant forcing teams into our way of working. A developer put it simply during a feedback session:

“We don’t want to work around your platform. We want your platform to work inside our world.”

That perspective reframed the challenge. We didn’t need to add more features—we needed to make the features accessible programmatically. That’s how the first version of our API was born.

A simple example

At launch, the API supported creating projects, updating them, and retrieving performance data. To make it approachable, we kept the syntax familiar and the structure clean. Here’s a TypeScript snippet showing how to create a project:

import fetch from "node-fetch";

async function createProject() {
  const response = await fetch("https://api.example.com/v1/projects", {
    method: "POST",
    headers: {
      "Authorization": "Bearer YOUR_API_KEY",
      "Content-Type": "application/json"
    },
    body: JSON.stringify({
      name: "Q4 Campaign",
      description: "Created via API"
    })
  });

  const data = await response.json();
  console.log(data);
}

createProject();

This example may look basic, but it demonstrates the intent: with just a few lines of code, repetitive tasks become automated. Marketing teams can spin up new projects for each campaign. Developers can trigger project creation from CI pipelines. Analysts can pull performance data into existing BI tools without manual exports. The power comes not from complexity, but from accessibility.

Early feedback and unexpected uses

When we quietly released the API to a handful of early adopters, their creativity went further than we expected. Agencies used it to onboard new clients automatically. Startups built scripts that synced platform data with Airtable or Google Sheets. One team even connected it to an internal alerting system that pinged Slack whenever project performance dropped.

The variety of use cases reminded us why APIs matter. No central product team can predict every integration a customer might want. By exposing endpoints like /projects, /metrics, or /users, we stopped trying to anticipate every need and started enabling teams to solve problems their way.

For clarity, here’s how we compared “before API” and “after API” in internal reviews:

Scenario	Before API	After API
New project	Manual input	Automated call
Data sync	CSV export	Direct fetch
Alerts	Not possible	Slack trigger

The table isn’t just a list of tasks—it shows how friction dissolved. What once required multiple manual steps now happens invisibly in the background.

What’s next

The first version is intentionally focused, but the roadmap is broader. We plan to add endpoints for analytics queries, team management, and notification hooks. Security remains a priority, so all calls require proper Authorization headers and use HTTPS exclusively. We’re also exploring OAuth for multi-user setups, making it easier for organizations to manage access at scale.

The philosophy is clear: the API isn’t an add-on, it’s infrastructure. It transforms the platform from a closed product into a flexible foundation. And like any foundation, its value isn’t in what it does alone, but in what others build on top of it.

By giving teams the ability to shape their workflows directly, we stop being the bottleneck. Instead, we become the enabler. That shift—away from control and toward empowerment—is what makes this release feel less like a feature and more like a turning point.

Introducing our new API for project automation

Introducing our new API for project automation

Why an API became inevitable

A simple example

Early feedback and unexpected uses

What’s next

Other posts

Other posts

Inside the process of shaping our product culture

Inside the process of shaping our product culture

What we learned by testing faster iteration cycles

What we learned by testing faster iteration cycles

Introducing our new API for project automation

Introducing our new API for project automation