Integrations
The admissions system integrates with several external services to provide file storage, email delivery, notifications, AI-powered features, and payment processing. This article provides an overview of available integrations and their purpose.
Active Integrations
Amazon S3 (File Storage)
All uploaded files -- applicant documents, form attachments, school logos, and generated contracts -- are stored in Amazon S3.
- Region: Typically
eu-central-1. - Private files (applicant documents): Stored in a per-school isolated location and only accessible through short-lived signed URLs (15-minute expiry). One school can never reach another school's files.
- Public files (school logos, form headers): Stored in a per-school public location and served directly — appropriate for non-sensitive brand assets.
Amazon SES (Email Delivery)
Email delivery for notifications, templates, and contract communications uses Amazon SES SMTP:
- Protocol: SMTP over TLS (port 587).
- From address: Configured at the Kinderpedia level (default:
[email protected]). - Delivery: Near-instant delivery for transactional emails.
OpenAI (AI Text Generation)
The system uses OpenAI's API for AI-powered text improvements in email template editing:
- Model: A modern instruction-tuned model is selected by the Kinderpedia admin.
- Usage: Text tone adjustment, grammar correction, and content suggestions in the WYSIWYG editor.
Kinderpedia Notification Server
Push notifications are delivered through the Kinderpedia notification infrastructure:
- Protocol: Messages are queued and delivered asynchronously by a background worker.
- Delivery: The notification service consumes the queue and pushes to users.
- Channels: In-app notifications and push notifications.
Kinderpedia Users SDK
User authentication and management is handled via the Users SDK:
- Authentication: JWT-based with cookies.
- User resolution: User profiles, names, and roles resolved from the central user service.
- Caching: User data cached for 5 minutes to reduce external API calls.
CDN (Content Delivery)
Images and assets use a CDN for fast delivery:
- Avatar images: User and school avatars resolved through CDN URL patterns.
- URL pattern: Handles
cdn::prefix resolution for avatar paths.
Integration Health
Most integrations are configured at the infrastructure level and do not require manual setup in the application UI. If you experience issues with any integration:
- Email not sending -- Check SES configuration and sender verification.
- Files not uploading -- Verify S3 credentials and bucket permissions.
- AI features not working -- Confirm OpenAI API key is valid and has sufficient quota.
- Notifications not arriving -- Check the notification queue and notification server status.
WARNING
Integration credentials are managed at the infrastructure level by Kinderpedia administrators. Schools don't need to configure these — if something stops working, contact your Kinderpedia admin.
Payment Integration
For payment processing (Stripe), see the dedicated Payment Integration article.