Developers

Written to be read.

A REST API over every public model method, real SDKs for modules and gateways, an event system for everything else — and a codebase that ships as PHP you can actually open.

Read the dev docs Download 6.0.0

api — bash 200 OK · 61 ms

$ curl -H "BLESTA-API-USER: api" \

-H "BLESTA-API-KEY: ****************" \

"https://acme.example/api/clients/get.json?client_id=842"

{

"response": {

"id": 842,

"id_code": "ACM-842",

"first_name": "Dana",

"last_name": "Reyes",

"company": "Northwind Labs",

"email": "dana@northwind.example",

"status": "active"

}

$ curl -H "BLESTA-API-USER: api" \

-H "BLESTA-API-KEY: ****************" \

-d "vars[client_id]=842" \

https://acme.example/api/invoices/add.json

{ "response": 4193 }

# Invoices.add event fired — plugins notified

a real session — every public model method is an endpoint

Blesta AI Billing & Payments Automation Orders Domains Support Clients & Admin Developers

The API

If the app can do it, the API can do it.

The REST API exposes every public model method for first party apps — clients, invoices, services, transactions, all of it — in JSON, XML, or serialized PHP with simple key auth. Plugin models are addressable too, as Plugin.Model. No "enterprise tier" endpoints.

Every public model method, not a curated subset JSON, XML & PHP response formats The staff chatbot writes API calls for you in v6

api — bash

$ curl -H "BLESTA-API-USER: api" \

-H "BLESTA-API-KEY: ****************" \

https://app.yourhost.example/api/clients/getList.json

{ "response": [ { "id": 1, "id_code": "1001", … } ] }

key auth · every model method · plugin models via Plugin.Model

my_module.php

class MyModule extends Module {
  public function addService($pkg, $vars) {
    return $this->api()->createAccount($vars);
  }
}
 
// or listen instead of extend
Events::register('Invoices.add', [$this, 'onInvoice']);

module · registrar · gateway · plugin — pick your surface

Extend everything

Three friction levels of extensibility.

Full SDKs for modules (including a registrar base class), merchant and non-merchant gateways, and plugins with database-registerable events and observers. Don't want to write code? The Universal Module needs none. Somewhere between? The Extension Generator scaffolds a working extension from inside the admin.

Events & observers across the core Universal Module — integrate with zero code Extension Generator + AI skills + Marketplace Example Objects Library for realistic fixtures New in 6.0

Source you can audit

Six encoded files. Everything else is yours to read.

Models, controllers, plugins, modules, gateways — the codebase ships as readable, namespaced PHP 8.2+. Exactly six files are encoded: three for license enforcement, three for the Blesta AI integration. That's the whole list. Audit it, step through it, patch your fork of a view — it's your server and the code is waiting for you.

Commercially licensed — source-available, not FOSS Passes security audits because auditors can actually read it Even the AI ticket logic is plaintext in the Support Manager

blesta/ — what ships encoded vs readable

app/models/invoices.php ................ readable
app/models/clients.php ................. readable
plugins/support_manager/ ............... readable
components/gateways/ ................... readable
components/modules/ .................... readable
license enforcement (3 files) .......... encoded
blesta ai integration (3 files) ........ encoded

6 encoded files, total · everything else is plain php

Import Manager

WHMCS 8.0-9.x database connected

Clients · services · invoices · tickets · more ✓ 4,112 records

Live on Blesta ✓ same weekend

whmcs 5.2-7.x & 8.0-9.x · clientexec 5.5+ · blesta 2.5 · generic csv

Switching

Migration is a weekend, not a quarter.

The Import Manager moves clients, services, invoices, transactions, tickets, and more from WHMCS 5.2-7.x or 8.0-9.x, ClientExec 5.5+ — or anything at all via CSV.

WHMCS, ClientExec & CSV importers in-box Run it on a staging copy first, as many times as you like White-glove migration service available

See migration pricing

Extension Dev Kit

Your AI already knows Blesta.

The Extension Dev Kit is a free reference kit on GitHub, distilled from the v6 base classes, that turns any AI coding tool into a Blesta extension developer. It covers building modules, gateways, and plugins from scratch — and porting what you already have, whether that's a 5.x extension or a WHMCS one.

Build modules, gateways & plugins against the real v6 contracts Convert 5.x extensions to 6.0 — or WHMCS extensions to Blesta Ships as a Claude Code skill; plain markdown works in any AI tool

Get the kit on GitHub

github.com/blesta/extension-dev-kit

SKILL.md ....................... Claude Code skill
reference/modules/ ............. create · 5.x→6 · WHMCS→6
reference/gateways/ ............ create · 5.x→6 · WHMCS→6
reference/plugins/ ............. create · 5.x→6 · WHMCS→6
reference/common/ .............. Paradigm UI · WHMCS mapping

drop it into claude code, cursor, copilot — the context does the teaching

And the plumbing

Incoming webhooks trigger actions inside Blesta from your other systems Outgoing webhooks with delivery logs and automatic retry Developer docs cover the API, events, and every extension type Official extensions developed in the open on GitHub The v6 chatbot's Developer Help mode answers plugin questions in-app A community of extension developers in the forums & Discord

Readable source · Real SDKs · Your server

Read the source.
Then build on it.

Install the trial, open app/models/, and see for yourself. Thirty days, full product, no credit card.

Download 6.0.0 Developer docs

Written to be read.

If the app can do it, the API can do it.

Three friction levels of extensibility.

Six encoded files. Everything else is yours to read.

Migration is a weekend, not a quarter.

Your AI already knows Blesta.

Read the source.Then build on it.

Read the source.
Then build on it.