Domains, DNS and accounts

Domains and accounts are the two halves of the customer-facing side of CaptainCore. A domain row can carry a DNS zone at Constellix, a registrar connection, forwarding through Forward Email and a sending subdomain at Mailgun. An account owns sites, domains and a billing relationship.

Note the two prefixes. /domains handles the collection. /domain/{id} handles one domain’s features. That split is historical and both are current.

Domains

curl -X POST -u user:app-password \
  -H "Content-Type: application/json" \
  -d '{"name":"example.com","site_id":135,"create_dns_zone":false}' \
  https://your-manager.example.com/wp-json/captaincore/v1/domains

The identifiers matter here. domain_id is the CaptainCore row, used on /domain/{id} and /dns/{id}. remote_id is the Constellix zone id, empty when the domain has no zone. provider_id is the registrar connection, empty when the domain is registered elsewhere.

DNS records

DNS is backed by Constellix. Record write routes carry their own permission closure that verifies you can reach the domain and returns 403 token_invalid otherwise.

Create takes type (A, AAAA, ANAME, CNAME, TXT, SPF, MX, SRV, HTTP), name (relative host, empty string for the apex), value and ttl in seconds, defaulting to 3600 if omitted.

curl -X POST -u user:app-password \
  -H "Content-Type: application/json" \
  -d '{"type":"TXT","name":"","value":"v=spf1 include:mailgun.org ~all","ttl":3600}' \
  https://your-manager.example.com/wp-json/captaincore/v1/dns/42/records

POST /domains/import takes zone (the BIND text) and optionally domain, which is overridden if the zone declares $ORIGIN.

Every create, update and delete on a record writes an activity log row with the record type and name.

Registrar actions

Available when the domain has a registrar provider connected, currently Hover.com or Spaceship.

Email forwarding

Forwarding runs through Forward Email. Activation writes the MX and TXT records into the zone.

recipients accepts a comma-separated string, an array of strings, or an array of {address} objects.

Sending through Mailgun

Mailgun handles outbound mail for a site, on a subdomain such as mg.example.com.

Accounts

Membership levels decide what a user sees inside an account.

Users and invites

curl -X POST -u user:app-password \
  -H "Content-Type: application/json" \
  -d '{"invite":"[email protected]","level":"sites-only"}' \
  https://your-manager.example.com/wp-json/captaincore/v1/accounts/12/invites

Two-factor and session routes sit alongside these: POST /me/tfa_activate, /me/tfa_validate, /me/tfa_deactivate, and GET / DELETE /sessions.

Billing, invoices and payment methods

Billing is backed by WooCommerce subscriptions and Stripe.

ACH bank payments have their own flow: POST /billing/ach/setup-intent creates a Stripe SetupIntent, POST /billing/ach/payment-method attaches the result, and POST /billing/ach/verify confirms micro-deposits. Administrators can review pending verifications with GET /billing/ach/pending and clear them with POST /billing/ach/admin-verify.

Site requests

Customers can ask for a site rather than create one directly.