Netlify API

Name: Netlify API API
Brand: Netlify API
Availability: InStock

✓ Official Vendor SpecCloud InfrastructureServerlessoauth2134 EndpointsREST

For Agents

Trigger deploys, manage sites, environment variables, and DNS, and stream build logs across a Netlify account.

Quickstart

Get started with Netlify API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"trigger a Netlify deploy"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Netlify API API.

Trigger a new build for a site or restart a stuck deploy

Promote a deploy to production or roll back to a previous deploy

Set, update, and rotate environment variables across sites and contexts

Attach a custom domain and manage DNS records for a Netlify-hosted site

Stream build logs to investigate a failing deploy

GET STARTED

Start building with Netlify API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Netlify API API for, with concrete tasks.

★ Programmatic Deploys from CI

Trigger a Netlify build from an external CI pipeline or content workflow when something outside Git changes (a CMS publish, a translation job, a scheduled rebuild). The API exposes site-level build hooks and deploy endpoints so the CI step can start a build, poll status, and pull logs without touching the Netlify dashboard.

POST to /sites/{site_id}/builds to start a new build, then poll /builds/{build_id} until state is 'done' and return the resulting deploy URL.

Multi-Environment Variable Management

Manage environment variables across production, deploy-preview, and branch-deploy contexts for many sites at once. The account-level env endpoints let a script or agent set, rotate, or remove a variable everywhere it appears, which is essential when secrets like API keys need rotating across an organisation.

Update STRIPE_KEY across all sites in account ACC-1 to a new value scoped to the production context only, and confirm the update on each site.

Custom Domain and DNS Automation

Provision a new custom domain on a Netlify site, attach a managed SSL certificate, and update DNS records via the API. Useful for white-label platforms that spin up a Netlify site per customer and need to attach customer-supplied domains automatically.

Attach customer.example.com to site SITE-99, provision an SSL certificate, and verify DNS resolution succeeds.

Build and Deploy Observability

Surface deploy success rates, build durations, and recent failures across all sites in an account into a dashboard or chatops channel. Combine /sites, /sites/{site_id}/deploys, and /builds endpoints to compute deploy frequency and mean time to recovery without scraping the dashboard.

List all deploys for site SITE-7 in the last 24 hours, count failures, and post a summary to the team's chat channel.

AI Agent Deploy Assistant

Let an AI agent answer 'why did my deploy fail?' and 'roll it back' through Jentic. The agent fetches the failing deploy, retrieves the build log, identifies the failing step, and either restarts the build or restores the prior deploy on the user's confirmation.

If the latest deploy of site SITE-7 has state 'error', fetch its build log, summarise the failing step, and restore the previous successful deploy.

Key Endpoints

134 endpoints — netlify is a cloud platform for deploying static sites, edge functions, and full-stack javascript applications directly from a git repository.

METHOD

PATH

DESCRIPTION

GET

/accounts

List accounts the token has access to

POST

/builds/{build_id}/start

Start a build

GET

/builds/{build_id}/log

Fetch the build log

GET

/accounts/{account_id}/env

List account-scoped environment variables

GET

/deploys/{deploy_id}

Get a deploy by id

POST

/billing/payment_methods

Manage billing payment methods

GET

/accounts

List accounts the token has access to

POST

/builds/{build_id}/start

Start a build

GET

/builds/{build_id}/log

Fetch the build log

GET

/accounts/{account_id}/env

List account-scoped environment variables

GET

/deploys/{deploy_id}

Get a deploy by id

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Netlify personal access token is stored encrypted in the Jentic vault. Agents receive scoped access — the raw token never enters the agent's prompt context or logs.

Intent-based discovery

Agents search by intent (e.g. 'trigger a Netlify deploy') and Jentic returns the matching operation with its schema, so the agent calls /sites, /builds, or /deploys without scraping docs for 134 endpoints.

Time to first call

Direct Netlify integration: 1-3 days to wire OAuth, model sites and deploys, and add error handling. Through Jentic: under 1 hour to search, load, and execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Vercel API

Vercel is the closest competitor — same Git-driven deploy model with stronger Next.js framework integration.

Choose Vercel when the project is Next.js-first; choose Netlify for richer build plugins and edge functions in non-Next.js stacks.

Alternative

Render API

Render covers static sites plus long-running services and managed databases, beyond Netlify's Jamstack focus.

Choose Render when the agent needs to deploy a long-running web service or a managed Postgres alongside the static site.

Complementary

GitHub API

GitHub hosts the source of truth that Netlify deploys from; the GitHub API drives PRs and webhooks that trigger builds.

Use GitHub to push code or open PRs and Netlify to deploy the resulting build.

Complementary

Cloudflare API

Cloudflare provides DNS, WAF, and CDN that frequently sit in front of Netlify-hosted sites.

Use Cloudflare alongside Netlify when DNS and WAF policy live outside Netlify's managed DNS.

FAQs

Specific to using Netlify API API through Jentic.

What authentication does the Netlify API use?

Netlify uses OAuth 2.0 personal access tokens. Pass the token in the Authorization header as 'Bearer {token}'. Through Jentic the token is stored encrypted and rotated centrally instead of being pasted into agent code.

Can I trigger a Netlify build through the API?

Yes. POST /builds/{build_id}/start (re)starts a specific build, and POST /sites/{site_id}/builds creates a new build for a site. The response returns a build id you can poll on /builds/{build_id} for status.

Can I roll back a deploy with the Netlify API?

Yes. List deploys via GET /sites/{site_id}/deploys, then POST /deploys/{deploy_id}/restore to restore a previous deploy as the published version. The current deploy is preserved in history.

What are the rate limits for the Netlify API?

Netlify enforces 500 requests per minute per token for most endpoints, with stricter limits on deploy creation. The X-RateLimit-Remaining response header shows current budget. Plan accordingly when scripting bulk operations.

How do I stream build logs through Jentic?

Run jentic.search('get netlify build log'), load the matching operation, then execute GET /builds/{build_id}/log with the build id. Jentic returns the log payload that the agent can summarise or feed into an alert.

Can I manage environment variables across deploy contexts with the Netlify API?

Yes. The /accounts/{account_id}/env and /api/v1/sites/{site_id}/env endpoints accept per-context values for production, deploy-preview, and branch-deploy. PATCH lets you update the value in one context without touching the others.