Build on InsideHOA

Simple API key authentication

Each integration receives a scoped API key associated with a specific HOA.

API keys should only be stored and used in secure server-side code. They should never be exposed in public browser JavaScript.

Designed for secure integrations

• HTTPS-only access
• HOA-specific API keys
• Scoped permissions
• Versioned API endpoints
• Revocable credentials
• Optional expiration dates

$curl = curl_init();

curl_setopt_array($curl, [
    CURLOPT_URL =>
        'https://services.insidehoa.com' .
        '/api/public/v1/ping',

    CURLOPT_RETURNTRANSFER => true,

    CURLOPT_HTTPHEADER => [
        'X-IHOA-API-Key: YOUR_API_KEY'
    ]
]);

$response = curl_exec($curl);

curl_close($curl);

{
  "name": "Community Website",
  "scopes": [
    "public.notifications.read"
  ]
}

$curl = curl_init();

curl_setopt_array($curl, [
    CURLOPT_URL =>
        'https://services.insidehoa.com' .
        '/api/public/v1/notifications?limit=20&type=Event',

    CURLOPT_RETURNTRANSFER => true,

    CURLOPT_HTTPHEADER => [
        'X-IHOA-API-Key: YOUR_API_KEY'
    ]
]);

$response = curl_exec($curl);

curl_close($curl);

{
  "items": [
    {
      "notificationPk":
        "cd9f775f7ce3468297ad7b6e59751215",

      "notificationId":
        "8877fb91a1b143dcad87ca4c5df28829",

      "notificationType":
        "Event",

      "title":
        "Board Meeting",

      "author":
        "Community News",

      "contentText":
        "The board will meet Thursday evening.",

      "event": {
        "details": {
          "eventType":
            "BoardMeeting",

          "occurrences": [
            {
              "startDateTime":
                "2026-10-01T23:30:00Z",

              "endDateTime":
                "2026-10-02T01:30:00Z",

              "location":
                "Remote"
            }
          ]
        }
      }
    }
  ],

  "nextCursor":
    null,

  "hasMore":
    false,

  "hoaTimeZone":
    "Mountain Standard Time"
}

WordPress-friendly

InsideHOA can be integrated into an existing WordPress website using the native WordPress HTTP API.

A lightweight custom plugin can retrieve notifications, support both structured and legacy event records, convert UTC timestamps using the returned HOA time zone, render the content within the website, and record engagement without exposing the InsideHOA API key to visitors.

WordPress request example

$response = wp_remote_get(
    'https://services.insidehoa.com' .
    '/api/public/v1/notifications?limit=20&type=Event',
    [
        'headers' => [
            'X-IHOA-API-Key' =>
                INSIDEHOA_API_KEY
        ],

        'timeout' => 10
    ]
);

if (!is_wp_error($response)) {
    $notifications = json_decode(
        wp_remote_retrieve_body($response),
        true
    );
}

Convert a UTC timestamp for display

$utc = new DateTime(
    $start_date_time,
    new DateTimeZone('UTC')
);

$utc->setTimezone(
    new DateTimeZone(
        $windows_to_iana[
            $notifications['hoaTimeZone']
        ]
    )
);

PHP uses IANA time-zone identifiers. If the API returns a Windows identifier such as Mountain Standard Time, the integration must map it to the corresponding IANA identifier, such as America/Denver.

Handle structured and legacy events

$event =
    $notification['event'] ?? null;

if (!empty($event['details'])) {
    $occurrences =
        $event['details']['occurrences'] ?? [];
} elseif ($event !== null) {
    $occurrences = [[
        'startDateTime' =>
            $event['startDateTime'] ?? null,

        'endDateTime' =>
            $event['endDateTime'] ?? null,

        'isAllDay' =>
            $event['isAllDay'] ?? false
    ]];
}