HydraCore
API by router

Domains

Get Domain Records

Get the DNS records required for custom domain setup.

Reads the custom_domain from tenant_branding and returns the CNAME/A records needed for verification.

"There's no place like home." — Dorothy, Wizard of Oz (there's no place like your custom domain)

GET
/v1/domain/records
AuthorizationBearer <token>

In: header

Header Parameters

X-Api-Key?X-Api-Key

Response Body

curl -X GET "https://loading/v1/domain/records" \  -H "X-Api-Key: string"
{
  "domain": "string",
  "records": [],
  "verified": false
}
{
  "detail": [
    {
      "loc": [
        "string"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

Retry Ssl

Retry SSL provisioning for a domain stuck in error state.

Deletes the old CF hostname (if any), resets state to 'none', and the user can re-trigger via POST /domain/verify. Only works if a custom domain is configured and ssl_status is an error state.

"Never tell me the odds." — Han Solo (about retrying failed SSL provisioning)

POST
/v1/domain/retry-ssl
AuthorizationBearer <token>

In: header

Header Parameters

X-Api-Key?X-Api-Key

Response Body

curl -X POST "https://loading/v1/domain/retry-ssl" \  -H "X-Api-Key: string"
{}
{
  "detail": [
    {
      "loc": [
        "string"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

Get Ssl Status

Get current SSL automation status and recent log entries.

"Badges? We don't need no stinking badges!" — Gold Hat, Treasure of the Sierra Madre (about SSL badges on the dashboard)

GET
/v1/domain/ssl-status
AuthorizationBearer <token>

In: header

Header Parameters

X-Api-Key?X-Api-Key

Response Body

curl -X GET "https://loading/v1/domain/ssl-status" \  -H "X-Api-Key: string"
{
  "log": [],
  "status": {
    "domain": "string",
    "domain_verified": false,
    "last_check_at": "string",
    "ssl_error": "string",
    "ssl_expires_at": "string",
    "ssl_provisioned_at": "string",
    "ssl_status": "none",
    "verification_attempts": 0
  }
}
{
  "detail": [
    {
      "loc": [
        "string"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

Verify Domain

Create CF custom hostname and start validation, or check existing status.

Phase 1.10: Replaces the old DNS TXT/CNAME verification with CF API.

  • First call: creates CF custom hostname → cf_pending_validation
  • Subsequent calls: polls CF API for status update
  • CF validates via HTTP DCV when CNAME is pointed to proxy.hydracore.dev

"Trust, but verify." — Ronald Reagan (about Cloudflare hostname validation)

POST
/v1/domain/verify
AuthorizationBearer <token>

In: header

Header Parameters

X-Api-Key?X-Api-Key

Response Body

curl -X POST "https://loading/v1/domain/verify" \  -H "X-Api-Key: string"
{
  "domain": "string",
  "records": [],
  "verified": false
}
{
  "detail": [
    {
      "loc": [
        "string"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}