nBlocks API
✓ Official Vendor SpecIdentity AuthAuthenticationapiKey50 EndpointsREST
For Agents
Configure SaaS app settings, manage tenants, roles, feature flags, and payment plans, and customise authentication branding and email templates for an nBlocks-powered application.
Use for: I need to create a new role with specific permissions in nBlocks, Update the password reset email template for my SaaS app, List all roles defined for my nBlocks application, Retrieve the current app profile and credential state
Not supported: Does not handle end-user sign-in flows, MFA challenges, or session token issuance — use for app, tenant, role, and branding configuration only.
The nBlocks API provides a multi-tenant SaaS platform backend for app management, user authentication, tenant management, role-based access control, feature flags, and payment plan handling. Developers integrate it to bootstrap a SaaS product without building auth, billing, or tenant isolation from scratch. The API exposes 50 endpoints covering app profile configuration, branding (custom CSS and translations), email templates, role definitions, and credential rotation through an x-api-key header.
Install Jentic One Beta
Connect the nBlocks API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the nBlocks API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with nBlocks API.
Update app branding by uploading custom CSS and translation files for the login UI
Define and assign roles with granular permission sets for multi-tenant access control
Manage email templates used for verification, password reset, and tenant invitations
Rotate app credentials and inspect credential state without redeploying the app
Configure feature flags and payment plans that gate access to product tiers
Provision and manage tenants under a single nBlocks app profile
Use Cases
Patterns agents use nBlocks API for, with concrete tasks.
★ SaaS Tenant Onboarding Bootstrap
Use nBlocks to launch a multi-tenant SaaS product without building authentication, tenant isolation, role management, or billing plumbing. The API lets a backend service create the app profile, define roles, configure email templates, and wire up payment plans in a single integration. Time-to-launch drops from weeks of auth and billing work to a few days of configuration.
Create an admin role with permission to manage users and assign it to the first tenant via PUT /role/{roleId}
Custom Branding for Login and Emails
White-label the nBlocks-hosted login experience by uploading custom CSS, translations, and per-template email content. Agencies and product teams use this to deliver a branded auth flow per customer, with branding changes applied at runtime without redeploying. The flow uses POST /brand/css, POST /brand/translations, and PUT /email/template/{templateName}.
Upload a custom CSS file via POST /brand/css and update the welcome email template via PUT /email/template/welcome
Role and Permission Management
Define application-wide roles with permission sets, assign them to tenants, and update permissions over time as the product evolves. The role endpoints (GET /role, POST /role, PUT /role/{roleId}) give programmatic control over RBAC without touching the auth UI. Suitable for products with admin, member, and viewer tiers across hundreds of tenants.
List existing roles via GET /role and create a new viewer role with read-only permissions via POST /role
Agent-Driven SaaS Configuration
AI agents use nBlocks through Jentic to provision new tenants, rotate credentials, and update branding on behalf of an administrator. Jentic stores the x-api-key in an isolated vault so the agent never sees the raw secret, and the agent searches by intent to find the right endpoint. Useful for ops automation, support bots, and internal admin agents.
Search Jentic for 'rotate nBlocks app credentials' and execute PUT /app/credentials with a new key
Key Endpoints
50 endpoints — the nblocks api provides a multi-tenant saas platform backend for app management, user authentication, tenant management, role-based access control, feature flags, and payment plan handling.
METHOD
PATH
DESCRIPTION
GET
/app
Get app profile
PUT
/app/credentials
Update app credentials
POST
/role
Create a new role
PUT
/email/template/{templateName}
Update an email template
POST
/brand/css
Upload custom CSS
POST
/brand/translations
Set custom translations
GET
/app
Get app profile
PUT
/app/credentials
Update app credentials
POST
/role
Create a new role
PUT
/email/template/{templateName}
Update an email template
POST
/brand/css
Upload custom CSS
POST
/brand/translations
Set custom translations
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
The nBlocks `x-api-key` is stored encrypted in the Jentic vault. Agents receive scoped execution tokens — the raw header value never enters the agent's context or logs.
Intent-based discovery
Agents search by intent (e.g., 'create a tenant role in nBlocks') and Jentic returns the matching endpoint with its schema, so the agent can call POST /role without browsing nBlocks docs.
Time to first call
Direct nBlocks integration: 1-2 days to wire up auth, branding, and roles. Through Jentic: under 30 minutes — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using nBlocks API through Jentic.
What authentication does the nBlocks API use?
The nBlocks API uses an API key passed in the `x-api-key` header (security scheme `apiKeyAuth`). Through Jentic, this key is stored in the encrypted vault and never enters the agent's context — agents call the API via scoped execution tokens.
Can I manage roles and permissions with the nBlocks API?
Yes. The /role endpoints support listing all roles (GET /role), creating new roles (POST /role), and updating role permissions (PUT /role/{roleId}). Roles can be assigned to tenants to enforce RBAC across the SaaS application.
What are the rate limits for the nBlocks API?
Public rate limits are not declared in the OpenAPI spec. Refer to the nBlocks documentation at nebulr-group.github.io/nblocks-api-docs for current quotas. Jentic surfaces 429 responses back to the agent so retries can be handled with exponential backoff.
How do I customise the login page branding through Jentic?
Search Jentic for 'upload custom CSS to nBlocks' to find the POST /brand/css operation, load its schema, then execute with the CSS payload. Use POST /brand/translations for localisation strings on the same login UI.
Can I rotate nBlocks app credentials programmatically?
Yes. PUT /app/credentials updates the credentials and GET /app/credentialsState returns the current rotation status. Jentic agents can call these directly without exposing the raw API key.
GET STARTED