ENJManagement API reference
Source f0eee8a

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.
NeedUse
Discover clients and campaignsGET /api/clients?compact=true
Read source material and approved offersWebsite context and scoped Drive-source readers
Read client callsGET /api/client-context/calls
Build and connect native pagesLander Studio routes and domain-setup
Track a blocker or revisionTickets API with current revision checks
Find an exact routeSearch the complete endpoint catalogue