Enterprise

Managing an organization requires the right administrative tools to ensure smooth and safe operations. Heylo helps Heylo Enterprise organizations balance control at the organization level with local group leaders. These controls maintain order, protect the organization, and grant oversight to local chapters and groups in the organization.

Specific Controls:

• Add or remove any admins at organization and group level
• Add, view, or remove organization bank account
• Access any group within organization
• View custom reporting

An organization can have unlimited admins. Any admin can add or remove any other organization admin by contacting Team Heylo.

Heylo Enterprise helps group leaders communicate with all members of all groups in the organization. Sharing content such as events, links, and group member benefits enables group organizations to disseminate information across all members equally and simultaneously without administrative overhead.

Note, all content types are optional at the discretion of organization admins.

Brand assets

An organization can pass organization logo and brand colors to all chapter groups and update all simultaneously. 

Content types

• Collab events
• Roles
• Links
• Benefits

Refreshing content

Content can be updated instaneously across the entire organization. New groups added to the organization will automatically receive the content. Collab events, however, require each group to add the event as a collab.

With Heylo Enterprise, an organization has the choice to allow each chapter to link their own bank account, or use one central bank account to collect payments. Payments include paid events and memberships.

Required membership dues can provide access to all groups in the organization and can be tracked and reported by the original sourcing group. Each local group leader can see their individual group reporting, but not reporting across the organization. The organization admins can see reporting across the entire organization.

Organizations can elect to centralize banking or allow groups in the organization to manage their own banking and payments.

Admins of an organization on Heylo Enterprise can receive custom reports detailing activity across all groups in the organization.

Examples of custom reports:

• Event attendant by event and group
• Top attendees by group
• Payments by group
• Member info export by group

Report frequency options

• Monthly
• Annually
• One-off

To request a new custom report, or to submit an edit request, get in touch with Team Heylo.

Heylo Enterprise pricing is unique for each organization based on the needs of the organization. It includes Heylo Pro for all groups along with all the additional features in Heylo Enterprise. Pricing is dependent on payment volume, number of groups, custom reporting requirements, and number of members.

To get a quote, please share info about the organization with Team Heylo.

Connecting with groups is our joy. You can reach us anytime in Heylo Support Chat in your Heylo private chats. Or email us at [email protected]. We are also active on Instagram as @heylo_co and you can reach us through direct messages there too. Reach out anytime with your feedback and ideas - we’d love to connect with you!

Furthermore, everyone on Heylo has access to our work to improve Heylo via “What’s New”. See “What's New” from profile settings, or check out more releases on our website.

This guide explains how to automate adding and removing members in Heylo via our REST‑only API.

TL;DR – It’s two HTTPS endpoints, both POST, authenticated with a single bearer token. You create invites or remove members with simple JSON payloads. No sessions, no WebSockets, no surprises.

1. Prerequisites

2. Authentication

Every request must include the bearer token header:

Authorization: Bearer HEYLO_API_KEY
Content‑Type: application/json

Need to rotate? Contact us or email [email protected] and we’ll issue a new one.

3. Rate limits

• Soft limit: up to 5 concurrent requests per organization.

• Best practice: Send one request at a time, wait for the 2xx response, then send the next.

• No hard per‑minute cap (yet). We’ll introduce structured 429s once the surface expands.

4. Endpoints

Coming soon: Update and fetch endpoints so you can edit member data or retrieve roster snapshots.

5. Request format

5.1 Create Invite

{
  "communityId": "abc123",             // required – Heylo group ID
  "member": {
    "userId": "user‑42",               // stable ID in *your* system
    "firstName": "Ada",
    "lastName": "Lovelace",
    "email": "[email protected]",
    "phoneNumber": "+1‑555‑867‑5309",
    "birthDate": "1815‑12‑10",
    "gender": "female",               // male | female | non-binary | decline
    "memberSinceMonth": "May",
    "memberSinceYear": "2024",
    "emergencyContactName": "Charles Babbage",
    "emergencyContactPhoneNumber": "+1‑555‑123‑4567",
    "emergencyContactRelationship": "Friend"
  },
  "replyToEmail": "[email protected]", // optional – override default reply‑to
  "suppressEmails": false,                // true = skip Heylo invite/reminder emails
  "type": "invite"                       // *always* "invite" for this endpoint
}

Example cURL

curl -X POST \
  https://us-central1-piccup-82257.cloudfunctions.net/apiv1-create \
  -H "Authorization: Bearer HEYLO_API_KEY" \
  -H "Content-Type: application/json" \
  -d @invite.json

5.2 Remove Member

{
  "communityId": "abc123",  // Heylo group ID
  "userId": "user‑42",      // same stable ID you used to create the invite
  "type": "member"          // *always* "member" for this endpoint
}

Removing a member automatically cancels any pending invites for the same [userId, communityId] pair.

Example cURL

curl -X POST \
  https://us-central1-piccup-82257.cloudfunctions.net/apiv1-remove \
  -H "Authorization: Bearer HEYLO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"communityId":"abc123","userId":"user-42","type":"member"}'

Need help? No problem! Contact the Heylo team or email us at [email protected].