Skip to main content
The Public Directory API exposes That’s Me events to search engines (Googlebot, Bingbot) and LLMs (Claude, GPT, Gemini) so they can discover and reason about real-world certifications, courses, and competitions when chatting with users. No authentication required. Rate limited at 30 req/min per IP.

Base URL

All endpoints below are prefixed with /event.

Privacy guarantees

The Public Directory never returns recipient data. You won’t find emails, names of certified people, birth dates, addresses, or phones here. Only:
  • Event metadata (name, description, category, dates, location, image)
  • AI-extracted skills and keywords
  • Issuer public profile (organization name, logo, KYB verification status)
Even if you have a recipient’s email outside this API, you can’t enrich it with personal data via this endpoint. That’s by design.

What’s exposed

Only events that pass all of these filters:
  1. is_private = false (issuer marked the event as public)
  2. status = ACTIVE
  3. Issuer is on a paid plan (or within 90-day grace period after cancellation)
  4. Event has a future date OR is recurring (recurrence_type != 'NONE')
  5. Not an internal auto-event (is_system = false)
Issuers on Free plan are not in the directory — paying is the gate.

Endpoints

GET /event/public-list

Paginated list of public events with AI analysis. The bread-and-butter endpoint.
Query params: Response shape:

GET /event/public-sitemap

Compact list of all public events for crawlers and SSG builds.
Response:

GET /event/canonical-tags

Browse the canonical tag taxonomy. Useful for an LLM that wants to know the vocabulary before querying.

GET /event/{id}/next-steps

Given an event, returns suggested “next steps” — learning trail continuations, preparatory events, deepening events, alternative paths, and cross-issuer similar events. Max 20 items total.
Response groups: continuation, preparatory, deepening, alternative, suggestive, similar.

Use case: LLM-driven discovery

The intent of this API is to let LLMs do the user-event matching using their own context window and tokens, not ours. Example flow:
  1. User chats with Claude/GPT/Gemini: “I want to level up my data science skills next year.”
  2. The LLM already has prior history of the user (it’s been chatting with them).
  3. The LLM hits GET /event/public-list?category=EDUCATION&q=data+science to fetch candidate events.
  4. The LLM reads the ai_analysis.skills and ai_analysis.keywords of each event and ranks them against the user’s profile — all client-side, using the LLM’s own inference.
  5. The LLM recommends the top match with the platform_url, which deep-links the user to the event on That’s Me.
This pattern means the LLM provider pays for the match, not us. The value comes from being the canonical, verifiable, AI-readable source of real-world certifications.
Want your events to surface here? Upgrade to Starter or above and keep is_private: false on your events. Higher recommendation rate comes from filling out the AI-analysis fields well (clear description, accurate dates, image, location).

Rate limit and abuse

  • 30 requests per minute per IP.
  • Exceeded? 429 Too Many Requests with Retry-After header.
  • Heavy abuse (scraping the full directory in tight loops) may result in IP blocks. If you’re an LLM provider or search engine and need higher limits, email suporte@thatsme.com.br.

What’s NOT here

Things that require authentication and are outside the public directory:
  • Lists of recipients (use /v1.0/recipients with your API key)
  • Webhook subscriptions (use /v1.0/webhooks)
  • Certificate issuance (use POST /v1.0/invitations)
  • Dashboard analytics (use /dashboard/* with your API key)
  • Anything containing personal data of certified people
See /api/v1/overview for the authenticated API.