Public API · planned · not built · no keys issued yet

A public API is on our list.

We are planning a read-only REST + JSON interface over CommunATI's public directory of organizations, programs, events and projects. It is not built yet, and no keys have been issued. If it goes ahead, it could help embed Manitoba STEM listings on a school-division portal, power a regional discovery app, support research on access patterns, or feed classroom tools. Everything on this page is a plan and may change.

Tell us you're interested See the planned endpoints

Roadmap

Planned phases, no dates yet.

If we build the API, we plan to do it in stages. None of these phases has started, and none has a date. We will update this page if that changes.

Planned · Phase 1

Read-only directory

Organizations, programs, events. JSON only. Static API key auth. 60 requests / minute / key. Beta endpoints versioned as /v1beta.

Planned · Phase 2

v1 + projects

Stable /v1 namespace, project-showcase endpoint, geosearch, age-band filters, ETags + Last-Modified, OpenAPI 3.1 schema published.

Planned · Phase 3

OAuth 2.0 + webhooks

OAuth 2.0 with org-scoped tokens. Write endpoints for member orgs to manage their own listings programmatically. Outbound webhooks for new programs and event changes.

Idea · Phase 4

Other provinces (idea only)

We may one day explore shared search with similar directories in other provinces. No agreements exist.

Endpoints (planned)

Read-only resources we plan to offer first.

Planned base URL (not yet built): https://api.communati.ca/v1beta (beta) → https://api.communati.ca/v1 (stable). As planned, every endpoint would return application/json, with application/geo+json on geo-enabled endpoints via the Accept header.

GET/organizations

List approved organizations. Filterable by region, type, indigenous_led, has_active_programs. Paginated via ?cursor. Returns name, slug, region, lat/long, logo URL, summary, and the org's program count.

Auth: any tier · Rate: 60/min beta, 600/min stable · ETag supported

GET/organizations/{slug}

Detail view for one organization. Includes the full description, contact info, registration URL, program list (summary), and the org's currently advertised events.

Auth: any tier · Rate: 60/min beta · Cache-Control: public, max-age=300

GET/programs

List programs across all orgs. Filterable by age_band (under-5, 5-7, 8-10, 11-13, 14-16, 17-plus), type (robotics, code, science, maker, AI, etc.), region, format (in-person, virtual, hybrid), distance_km + near (lat,long). Returns the program summary plus the parent org's slug.

Auth: any tier · Rate: 60/min beta · Supports ?lang=fr for translated descriptions where available

GET/programs/{slug}

Detail view for one program. Includes schedule, location, age band, instructor names (if public), registration link, and the related program count from the same org.

Auth: any tier · Rate: 60/min beta

GET/events

Upcoming public events from all orgs. Filterable by start_after, start_before, region, age_band, category. Supports format=icalendar for an .ics calendar feed instead of JSON.

Auth: any tier · Rate: 60/min beta · iCalendar format mirrors events.ics

GET/projects

Public project gallery — youth-submitted, moderator-approved projects from member orgs. Returns title, summary, hero image URL, contributing org, project tags, and submission date. No personal data about youth.

Auth: any tier · Rate: 60/min beta · later phase

GET/sponsors

Sponsor list, if a public sponsor program exists by then — with logo URL, sponsor level, and (when sponsor opts in) a public description. Excludes any sponsor that opts out of public listing.

Auth: any tier · Rate: 60/min beta · later phase

POST/organizations/{slug}/programs

Create or update a program owned by your organization. Requires an OAuth 2.0 access token with the programs:write scope, issued to a verified org admin.

Auth: OAuth 2.0 (org-scoped) · Rate: 30/min · later phase

Authentication

Planned authentication: static keys first, OAuth 2.0 later.

As planned, beta keys would be static, scoped per developer or organization, and rotated on request. Write access would use OAuth 2.0 with org-scoped access tokens, authorized by the organization's admin. No keys exist yet.

# Illustrative only, not built yet. Planned beta: static API key in Authorization header
curl https://api.communati.ca/v1beta/programs?age_band=8-10&region=winnipeg \
  -H "Authorization: Bearer cmnt_pk_live_xxxxxxxxxxxxxxxxxxxxxx" \
  -H "Accept: application/json"

# Stable: OAuth 2.0 client credentials (server-to-server)
curl https://api.communati.ca/oauth/token \
  -d grant_type=client_credentials \
  -d client_id=cmnt_ci_xxxxxxxxxxxx \
  -d client_secret=cmnt_cs_xxxxxxxxxxxx \
  -d scope=programs:read events:read

As planned, tokens would be JWTs signed with ES256, with public keys published at /.well-known/jwks.json if a production endpoint launches. Planned token lifetimes: one hour for client-credentials and twelve hours for OAuth 2.0 user-scoped tokens.

Rate limits + fair use

Planned rate limits.

We are planning for 60 requests per minute per key at beta, with bursting up to 120 RPM, and about 600 RPM at stable. A higher-volume option may follow (about 6,000 RPM); its terms and service levels are not decided.

As planned, limits would be advisory during beta — exceeding them would return HTTP 429 with a Retry-After header rather than blocking your key. Sustained abuse, scraping, or behaviour that degrades the service for other consumers could result in revocation. Terms of use are not written yet.

Schema + data model

Planned schema: JSON Schema at beta, OpenAPI 3.1 at stable.

As planned, the beta would include per-endpoint JSON Schema fragments at /v1beta/_schema/{resource}.json. Stable would ship a single openapi.yaml covering every public endpoint, plus generated client libraries for TypeScript, Python, and Swift. The schema would be versioned independently from the runtime; non-breaking field additions wouldn't bump the major version.

As planned, core resource fields would use snake_case, timestamps would be ISO 8601 in UTC, lat/long would use WGS 84 decimal degrees, currency would be CAD only, and language tags would follow BCP 47 (en-CA, fr-CA).

Use cases

What an API like this could support.

Examples only. These are illustrations of possible uses, not partners, users or commitments. No one has API access yet.

If you would use something like this, tell us at info@communati.ca. Interest helps us decide whether to build it, and what to build.

Interested?

Tell us you're interested.

There are no keys, no beta and no sandbox yet. If you would use a CommunATI public API, an email helps us decide whether to build it and what to build first. For any tool that would touch children's or family data, we also want to talk early about the privacy laws that may apply, such as federal privacy law (PIPEDA) and Manitoba law.

Email info@communati.ca with:

We will reply when we have news. We won't add you to any list without asking.

Open questions we're still resolving

Where your feedback shapes the surface.

A few API design questions we're publicly undecided on. If you have a preference, please write us at info@communati.ca — these stay open while we plan:

Hear if the API goes ahead.

If we build the API, we will publish a changelog here. Until then, write to us and we will let you know if there is news — short, infrequent, no marketing.

Ask for updates Contact us