Developer Portal

Public API documentation for East End Business Services. This is a small, single-purpose API — one endpoint, no accounts, no rate-limit tiers — documented in full below.

Authentication

None required. The API is public and unauthenticated. There is no API key to request or manage.

Versioning & deprecation policy

Endpoints are versioned by URL path: the current version is v1, under /api/v1/. Unversioned /api/* paths are deprecated aliases kept working for backward compatibility.

A deprecated response carries an RFC 8594 Deprecation: true header and a Link header with rel="successor-version" pointing to its replacement. A Sunset header with a removal date is added once one is scheduled — none is scheduled today.

Endpoints

Full request/response schemas: /openapi.json (OpenAPI 3.0.3).

Quickstart

List the current API surface:

curl https://eebs.us/api/v1

Submit a contact inquiry (safe to run as-is — it delivers to a real inbox, so use recognizable test data):

curl -X POST https://eebs.us/api/v1/contact \
  -H "Content-Type: application/json" \
  -d '{
    "Nombre": "Test Agent",
    "Correo": "[email protected]",
    "Mensaje": "API quickstart test — please disregard."
  }'

A successful submission returns 200 with {"success": true, "message": "..."}. Every error path — malformed JSON, a missing required field, an unreachable upstream — returns a structured JSON body:

{
  "error": {
    "code": "VALIDATION_ERROR",
    "message": "Missing required field(s): Correo.",
    "resolution": "Include Nombre and Correo in the request body."
  }
}

Sandbox

There is no separate sandbox environment. The single endpoint above is low-risk (a contact-form relay with server-side validation) and safe to exercise directly against production with clearly-labeled test data, as shown in the quickstart.

Machine-readable resources