Scopes a tech director can sign off on
A district admin registers a partner app, picks its read scopes — posts, events, documents, athletics — and hands over a token shown exactly once. The partner endpoints reuse the same handlers and serializers as Bloomz's own web surface, so a partner can never see more than the public web view does. There are no write scopes in the product, rotation is one click and immediate, and every registration, rotation, and disable lands in the audit log.
Webhooks that behave like the best in the industry
Five catalog events — content shared to the public web, athletics scores, dismissal transitions, visitor check-ins — deliver as signed payloads your partner verifies the same way they'd verify Stripe's. Failures retry on a bounded backoff schedule, dead-letter after five attempts, and every attempt is inspectable in the delivery log. Integrations stop being a nightly CSV job someone maintains and start being a push that arrives in seconds.
SIS, SSO, and rostering connect on day one, green means data is flowing. Toggle a provider.
How this reinforces the Bloomz pillars
Connected across Bloomz
20 minutes with Bloomz
answers more than 20 pages ever could.
Bring your hardest scenario, a multilingual community, a PBIS rollout, a vendor consolidation, and we'll walk through the actual product.