PrimeBrickPrimeBrick
  • Docs
  • Contact
  • MIT License
  • Documentation
  • MCP Server
  • API Catalog
  • Services
  • Libraries
PrimeBrickPrimeBrick

© 2026 PrimeBrick. MIT License. v3.8.0

github
Information
providers
    Get providers entity metadatagetList all email providersgetGet a single email provider by UUIDgetUpdate an email provider by UUIDputDelete an email provider (soft-delete)deleteCreate a new email providerpost
config_entries
    Get config_entries entity metadatagetList all configuration entriesgetGet a single config entry by UUIDgetUpdate a config entry value by UUIDput
webhook
    Receive an inbound webhook from an email providerpost
powered by Zudoku
EmailSender Catalog
EmailSender Catalog

providers

Download schema

Email provider configuration entities


Get providers entity metadata

GET
http://localhost:3002
/api/v1/entities/providers/meta
Bearer (JWT)
or
X-API-Key (header)

Returns the field schema, supported operations, and metadata for the providers entity. Used by MCP get_entity_meta tool and FE dynamic form generation.

Get providers entity metadata › Responses

200

Entity metadata

entity
​string
module
​string
​object[]
supported_operations
​string[]
GET/api/v1/entities/providers/meta
fetch('http://localhost:3002/api/v1/entities/providers/meta', { headers: { Authorization: 'Bearer <token>' } })
Example Responses
{ "entity": "providers", "module": "emailsender", "fields": [ { "name": "name", "type": "type", "nullable": true, "description": "description" } ], "supported_operations": [ "list", "get", "create", "update", "delete" ] }
json
application/json

List all email providers

GET
http://localhost:3002
/api/v1/entities/providers/list
Bearer (JWT)
or
X-API-Key (header)

Returns a list of all non-deleted email provider configurations. Each provider includes connection details (API key, endpoint, sender settings).

List all email providers › Responses

200

List of providers

​object[]
GET/api/v1/entities/providers/list
fetch('http://localhost:3002/api/v1/entities/providers/list', { headers: { Authorization: 'Bearer <token>' } })
Example Responses
{ "providers": [ { "uuid": "00000000-0000-0000-0000-000000000000", "provider": "brevo", "api_endpoint": "api_endpoint", "from_email": "from_email", "from_name": "from_name", "reply_to": "reply_to", "version": 0 } ] }
json
application/json

Get a single email provider by UUID

GET
http://localhost:3002
/api/v1/entities/providers/{uuid}
Bearer (JWT)
or
X-API-Key (header)

Returns the full details of a single email provider configuration, including the API key.

Get a single email provider by UUID › path Parameters

uuid
​string · uuid · required

Provider UUID

Get a single email provider by UUID › Responses

Provider details

uuid
​string · uuid
provider
​string
api_key
​string
api_endpoint
​string
from_email
​string
from_name
​string
reply_to
​string
version
​integer
GET/api/v1/entities/providers/{uuid}
fetch('http://localhost:3002/api/v1/entities/providers/:uuid', { headers: { Authorization: 'Bearer <token>' } })
Example Responses
{ "uuid": "00000000-0000-0000-0000-000000000000", "provider": "provider", "api_key": "api_key", "api_endpoint": "api_endpoint", "from_email": "from_email", "from_name": "from_name", "reply_to": "reply_to", "version": 0 }
json
application/json

Update an email provider by UUID

PUT
http://localhost:3002
/api/v1/entities/providers/{uuid}
Bearer (JWT)
or
X-API-Key (header)

Updates the configuration of an existing email provider. All fields are replaced.

Update an email provider by UUID › path Parameters

uuid
​string · uuid · required

Provider UUID

Update an email provider by UUID › Request Body

provider
​string
api_key
​string
api_endpoint
​string
from_email
​string
from_name
​string
reply_to
​string

Update an email provider by UUID › Responses

Provider updated

No data returned
PUT/api/v1/entities/providers/{uuid}
fetch('http://localhost:3002/api/v1/entities/providers/:uuid', { method: 'PUT', headers: { 'Content-Type': 'application/json', Authorization: 'Bearer <token>' }, body: JSON.stringify({ provider: 'provider', api_key: 'api_key', api_endpoint: 'api_endpoint', from_email: 'from_email', from_name: 'from_name', reply_to: 'reply_to' }) })
Example Request Body
{ "provider": "provider", "api_key": "api_key", "api_endpoint": "api_endpoint", "from_email": "from_email", "from_name": "from_name", "reply_to": "reply_to" }
json
Example Responses
No example specified for this content type

Delete an email provider (soft-delete)

DELETE
http://localhost:3002
/api/v1/entities/providers/{uuid}
Bearer (JWT)
or
X-API-Key (header)

Soft-deletes an email provider configuration. The record is marked as deleted but remains in the database.

Delete an email provider (soft-delete) › path Parameters

uuid
​string · uuid · required

Provider UUID

Delete an email provider (soft-delete) › Responses

Provider deleted

No data returned
DELETE/api/v1/entities/providers/{uuid}
fetch('http://localhost:3002/api/v1/entities/providers/:uuid', { method: 'DELETE', headers: { Authorization: 'Bearer <token>' } })
Example Responses
No example specified for this content type

Create a new email provider

POST
http://localhost:3002
/api/v1/entities/providers
Bearer (JWT)
or
X-API-Key (header)

Creates a new email provider configuration with API key, endpoint, and sender settings.

Create a new email provider › Request Body

provider
​string · required
api_key
​string · required
api_endpoint
​string
from_email
​string
from_name
​string
reply_to
​string

Create a new email provider › Responses

Provider created

No data returned
POST/api/v1/entities/providers
fetch('http://localhost:3002/api/v1/entities/providers', { method: 'POST', headers: { 'Content-Type': 'application/json', Authorization: 'Bearer <token>' }, body: JSON.stringify({ provider: 'brevo', api_key: 'api_key', api_endpoint: 'api_endpoint', from_email: 'from_email', from_name: 'from_name', reply_to: 'reply_to' }) })
Example Request Body
{ "provider": "brevo", "api_key": "api_key", "api_endpoint": "api_endpoint", "from_email": "from_email", "from_name": "from_name", "reply_to": "reply_to" }
json
Example Responses
No example specified for this content type

config_entries