# ENJ Management agent guide

API base: https://api.enjdigital.com
Source release: f0eee8a3239ff2e2736ec18b4017f5ee5cd062d8
Generated: 2026-11-20T08:50:18.465Z

## Start here

Connect once. Resolve the right client. Read before you act.

This reference describes the ENJ Management API. It is public documentation, not an access grant. Use your existing Management agent identity. Client records, provider credentials, messages and live authentication codes are never included in this site.


```bash
curl --fail-with-body https://api.enjdigital.com/api/auth/me \
  -H "Authorization: Bearer $ENJ_AGENT_TOKEN"
```


- Inspect the returned user and agentCapabilities before choosing a tool. Capability discovery is not an exhaustive permission grant.
- Resolve the exact Management clientId, campaignId and resource ID. A GHL location ID, team-member ID, service-user ID and Management client ID are different identifiers.
- Check GET /health and compare its commit with the source release shown on this site. If they differ, validate the current contract before relying on a write example.
- Treat a 403 as a permission boundary. Do not switch identities, use an admin session, change roles or disconnect an integration to work around it.

> Nothing on this site executes API requests. Copyable examples contain placeholders only. Mutations still require authority from the current task.

| Need | Use |
| --- | --- |
| Discover clients and campaigns | GET /api/clients?compact=true |
| Read source material and approved offers | Website context and scoped Drive-source readers |
| Read client calls | GET /api/client-context/calls |
| Build and connect native pages | Lander Studio routes and domain-setup |
| Track a blocker or revision | Tickets API with current revision checks |
| Find an exact route | Search the complete endpoint catalogue |

## Authentication & permissions

A Management token is not a provider API key.

Send Authorization: Bearer with the Management token already issued to your AI team member. Do not put tokens in query strings, URLs, tickets, screenshots, source control or this documentation. Human session-cookie sign-in and provider callbacks use different authentication paths.

| Boundary | What it means |
| --- | --- |
| Role guard | The role list is only one gate. Agency membership, client scope, assignment, feature permissions and route-specific checks can narrow access further. |
| Agent capability | Some tools additionally require an explicit service-user allowlist. An AI admin role does not bypass the domain allowlist. |
| X-Agency-Scope | Use only a scope available to the authenticated identity. Scope headers select existing access; they do not create access. |
| Server bridge | Internal runtime routes may require a separate server-held bridge secret, not the agent token. Do not request that secret. |
| Provider webhook | A callback is not an agent command. Do not simulate signed callbacks or use them to bypass supported tools. |

Saved Namecheap, Vercel, Drive, Fathom, Slack and GHL connections are resolved on the server by supported tools. A connected provider does not automatically make every provider operation available to every agent.


```bash
curl --fail-with-body https://api.enjdigital.com/api/authentication/accounts \
  -H "Authorization: Bearer $ENJ_AGENT_TOKEN"
```


> The authentication-accounts reader returns only accounts visible to your role, including current short-lived codes. Use it only for an authorized sign-in to the correct account. Never log codes or request raw TOTP seeds. Creating or changing authenticator accounts is a separate admin operation.

## Clients, campaigns & context

Keep every operation tied to its real owner.


```bash
curl --fail-with-body "https://api.enjdigital.com/api/clients?compact=true" \
  -H "Authorization: Bearer $ENJ_AGENT_TOKEN"
```


- Read the returned clients and their campaign IDs. Confirm the client, workspace and niche instead of merging records by name.
- Keep one build scope per actual campaign/page. Multiple approved niches are not a reason to abandon all generation; resolve their intended campaign scopes first.
- Do not use a different client’s GHL connection because it happens to be signed in. Client accounts may belong to separate GHL agencies.
- For website work, use the scoped context reader. It is available to Website Manager roles; direct Strategy routes have their own, narrower role list.


```bash
curl --fail-with-body "https://api.enjdigital.com/api/website-manager/context?clientId=CLIENT_ID&campaignId=CAMPAIGN_ID" \
  -H "Authorization: Bearer $ENJ_AGENT_TOKEN"
```


> GET is not a promise of zero side effects. Context readers may refresh caches or hydrate source material. Do not run refresh/synchronization actions as a substitute for ordinary cached reads without understanding their effects.

| Operational policy | Agent behavior |
| --- | --- |
| Onboarding | A completed onboarding form is sufficient; do not add a requirement for both form and call completion. |
| Strategy approval | Respect the saved campaign approval. Setup work is campaign-specific; separate campaigns keep their own GHL assets and landers. |
| Review | Save page URLs on the correct campaign and use the actual workflow stage. Do not confuse a draft, an in-review item and a launched campaign. |
| Launch | Publishing a website never authorizes publishing ads, changing budgets or turning on spend. |

## Approved offers & Google Drive

A missing structured angle is not proof that no offer was approved.

Read the exact client/campaign context and structured approval first. Then use Management’s existing scoped Drive integration to discover the linked offer buildout and source documents. Do not begin by requesting a separate Google login or declaring the offer missing.


```bash
curl --fail-with-body "https://api.enjdigital.com/api/website-manager/drive-sources?clientId=CLIENT_ID&campaignId=CAMPAIGN_ID" \
  -H "Authorization: Bearer $ENJ_AGENT_TOKEN"
```


The response includes referencedDocuments, files, listingLimitReached, campaign and available strategy context. The folder listing is capped at 500 files; a reached limit is a coverage warning, not proof of a complete search.


```bash
curl --fail-with-body "https://api.enjdigital.com/api/website-manager/drive-sources/FILE_ID?clientId=CLIENT_ID&campaignId=CAMPAIGN_ID" \
  -H "Authorization: Bearer $ENJ_AGENT_TOKEN"
```


- This reader supports native Google Docs associated with the client’s mapped folder or explicit client/campaign document links. It is not an arbitrary agency-wide file proxy.
- Inspect every relevant document.tabs entry. Blocks preserve headings, text, runs, green highlights and strikethrough. Approval highlighting may be on individual runs, not the whole paragraph.
- Match the selected wording to the correct niche/campaign. Do not promote an unrelated draft or unhighlighted copy because it appears in the same document.
- Client approval, substantiation of claims and measured ad performance are separate facts. Preserve exact approved wording and record the source tab/block when saving evidence.
- If approval conflicts with another source, record the exact conflict. Do not invent an offer or repeatedly retry a persistent 403.

> Structured Strategy routes are also indexed in the catalogue. Their role guards differ from Website Manager’s context/Drive readers; use the supported reader for your identity rather than escalating access.

## Buy & connect client domains

Use the saved integrations. One root per client, separate subdomains per page.

Discover agentCapabilities.landerDomains through /api/auth/me. The native domain tool requires an authorized AI service-user identity (or a human platform admin), an exact client/campaign/lander match, an approved current campaign and a live, published native lander. These are not the legacy Website Manager domain endpoints.


```bash
curl --fail-with-body "https://api.enjdigital.com/api/landers/LANDER_ID/domain-setup?clientId=CLIENT_ID&campaignId=CAMPAIGN_ID&roots=client-brand.site,client-brand.space" \
  -H "Authorization: Bearer $ENJ_AGENT_TOKEN"
```


- Inspect boundRoot and ownedRoots first. Reuse a client-owned root instead of buying one per niche. Candidates must satisfy the server’s client-brand checks.
- Keep the raw eligible quoteId and expiresAt. Quotes last five minutes and bind the actor, client, campaign, lander and root.
- The first one-year registration must be at most 300 USD cents including provider additional/ICANN fees. Premium/EAP domains and paid extras are excluded. Payment uses the saved account balance only.
- Read the renewal disclosure. The $3 policy is for the first registration year; do not imply renewals will also cost $3. Auto-renew must be confirmed off.


```json
{
  "clientId": "CLIENT_ID",
  "campaignId": "CAMPAIGN_ID",
  "landerId": "LANDER_ID",
  "action": "register",
  "root": "client-brand.site",
  "hostname": "homecare.client-brand.site",
  "quoteId": "FRESH_QUOTE_ID",
  "years": 1,
  "autoRenew": false,
  "maxChargeCents": 300
}
```


POST that body to /api/landers/LANDER_ID/domain-setup. Once owned, POST action="attach" using the same exact IDs, root and hostname. Then POST action="verify" until verified. Use a distinct subdomain for the other campaign.

| Status or error | What to do |
| --- | --- |
| registered / domain_owned_ready_to_attach | Ownership exists. Continue attachment; do not purchase again. |
| dns_pending / tls_pending / runtime_refresh_pending | Keep the checkpoint and retry verification with bounded backoff. Not a checkout failure. |
| verified | Independently read the branded HTTPS page, then save that URL on the correct campaign. |
| namecheap_insufficient_balance (402) | Refresh the balance/quote. Create or update one Urgent funding ticket with price, balance and shortfall. Resume after a top-up. |
| fresh quote / changed quote | Inspect again. Do not reuse an expired or consumed quote. |
| reconciliation / receipt / auto-renew review | Do not blindly register again. Retain the order evidence and escalate the precise review condition. |
| permission / provider / configuration error | A technical blocker is not proof of low balance and not a request for a browser login. |

> Namecheap XML has no atomic provider max-charge argument. Management rechecks the quote before dispatch and audits the receipt afterward. Do not invent a price-lock parameter or reintroduce the old “checkout unavailable” blocker. A dispatched or ambiguous order is durable and must be reconciled, never automatically repeated.

Attachment preserves unrelated DNS, associates the exact native lander with the shared runtime, refreshes its cache, and checks DNS, TLS and the current published page before returning a verified URL. A Vercel URL or submitted DNS record alone is not completion.

## Tickets & handoffs

One clear blocker, one owner, enough evidence to act.

- Read /api/tickets/options for valid team-member IDs, client options and campaign links. Assignee IDs are team-member IDs, not service-user IDs.
- Search existing client tickets before creating another. Keep technical revisions and blockers assigned to the responsible specialist, not automatically to the owner.
- Use a short action title. Description: what failed, exact client/campaign/page, relevant error/evidence, and the next action. Do not paste an entire chat.
- Attach useful, redacted screenshots with /api/tickets/TICKET_ID/attachments. Never include OTPs, bearer tokens or provider credentials.
- Funding blockers use Urgent priority and show fresh balance, required price and shortfall. Do not label an unavailable endpoint as insufficient funds.


```json
{
  "title": "Connect the approved campaign domain",
  "priority": "High",
  "clientScope": "clients",
  "clientIds": [
    "CLIENT_ID"
  ],
  "campaignIds": {
    "CLIENT_ID": "CAMPAIGN_ID"
  },
  "assigneeIds": [
    "TEAM_MEMBER_ID"
  ],
  "description": "Blocked: exact error and checkpoint. Evidence: relevant page/source link. Next: precise action needed.",
  "visibility": "internal"
}
```


POST /api/tickets creates a ticket. For updates, GET /api/tickets/TICKET_ID first and include its current revision as expectedRevision in PATCH /api/tickets/TICKET_ID.


```json
{
  "expectedRevision": 3,
  "status": "In Progress",
  "description": "Current blocker, evidence and next step."
}
```


> A missing expectedRevision is rejected with 428. A stale revision is rejected with 409. Re-read and reconcile; never overwrite someone else’s update blindly. Ticket editing can also depend on ownership/assignment, even when the role guard permits ticket writes.

## Client calls & transcripts

Read the entire relevant call, not just a summary or the first page.


```bash
curl --fail-with-body "https://api.enjdigital.com/api/client-context/calls?clientId=CLIENT_ID&q=strategy&offset=0&limit=100" \
  -H "Authorization: Bearer $ENJ_AGENT_TOKEN"
```


The list returns calls, total, nextOffset and strategyCallRecordingIds for matched client recordings. Follow nextOffset until null when a complete search is needed. The list limit is at most 250. Do not treat an unmatched or unavailable recording as a call that never happened.


```bash
curl --fail-with-body "https://api.enjdigital.com/api/client-context/calls/RECORDING_ID?clientId=CLIENT_ID&offset=0&limit=200" \
  -H "Authorization: Bearer $ENJ_AGENT_TOKEN"
```


- The detail response pages transcript.lines and transcript.nextOffset. Continue until nextOffset is null; the detail limit is at most 200 lines.
- Keep the clientId on every detail request. A recording ID alone does not establish client scope.
- Check transcriptHydration.available and totalLines. Missing transcript coverage is a limitation, not evidence of no discussion.
- Quote decisions with the meeting/source and timestamp when present. Separate a suggestion, client approval, a promise to verify later and an implemented change.

> A detail read may hydrate an available transcript through the saved Fathom integration. It is not a zero-side-effect cached read. Do not create plaintext copies of Fathom keys or start unrelated transcription jobs.

## Failures, safety & coverage

A missing permission is not missing data. An accepted request is not verified delivery.

| Response | Safe handling |
| --- | --- |
| 400 / 415 | Validate body, identifier types and supported document/content format. Do not guess a new endpoint. |
| 401 | Check the existing Management token and identity. Do not rotate another bot’s credentials. |
| 402 | For domain checkout, inspect the fresh balance and create/update the funding blocker. |
| 403 | Stop at the permission boundary. Report the exact route and scope, without credentials. |
| 404 | Distinguish a wrong ID/scope from an unavailable route. Check the current inventory and deployed commit. |
| 409 / 428 | Refresh the resource or quote, reconcile a conflict, and preserve uncertain external-order state. |
| 429 | Respect Retry-After when supplied; use bounded backoff, not rapid repeated polling. |
| 5xx / timeout | Preserve the checkpoint. For mutations, establish whether the action happened before retrying. |

- Never send SMS/email, place calls, enroll workflows, issue charges, publish ads or change spend just to test an integration.
- Production synchronization/refresh tools may write data or trigger notifications. Use supported reads for an audit; inspect effects before running background collection.
- Paginate every required source and keep coverage gaps visible. Partial history, missing credentials and failed pagination are not zero activity.
- A booking confirmation is not attendance. A successful conversion send is not guaranteed ad attribution. A “completed” call status is not proof of a human pickup.
- Provider bridge/webhook routes are documented for inventory completeness, not for agents to call directly.
- The private voice pilot remains disabled. Do not dial, unlock an uncertain attempt, expand its allowlist, reactivate legacy providers or route prospects through it.

> The catalogue is complete for explicit route declarations at the displayed source commit. Request schemas are partially extracted, and response schemas are not inferred. Business rules and provider-specific checks remain authoritative in the current source.

## Machine-readable reference

Start with the guide, then fetch only the inventory you need.

| File | Purpose |
| --- | --- |
| /llms.txt | Agent entry point, authority rules and links. |
| /guide.md | All operating guides in plain Markdown. |
| /manifest.json | Small area index. Fetch only the API area you need. |
| /reference/landers.json | Example of a focused area catalogue; every area has JSON and Markdown. |
| /endpoints.json | Every explicit route, inferred role guard, source link and partial request schema. |
| /endpoints.md | The same catalogue as readable Markdown. |
| /openapi.json | OpenAPI 3.1 with source-derived, partial request schemas and explicit completeness markers. |


```text
Before using ENJ Management, read https://docs.enjdigital.com/llms.txt and the relevant guide. Authenticate with your existing Management agent identity and inspect /api/auth/me. Use the exact client/campaign IDs. Documentation is not authorization to perform a mutation.
```


Freshness is pinned to a source release, not silently implied. Compare GET https://api.enjdigital.com/health with the source commit displayed here. The repository includes a reproducible route extractor and validation checks; regenerate and republish after API contract changes.