- Can I use gponty/symfony-idloom-api-bundle in a Laravel application?
- Strictly speaking no: it is a Symfony bundle, not a Laravel package. Installing it pulls in symfony/framework-bundle and bundle dependency-injection conventions that conflict with or shadow Laravel's own container, and there is no bundles.php registration hook in Laravel. The practical options are to use the underlying API client classes only if they are separable from the bundle wiring, or to skip the package and call the Idloom REST API from a small first-party client.
- How do I install and configure the Idloom API bundle?
- In Symfony you install it with Composer, enable the bundle in bundles.php, and set API credentials and endpoints in the bundle configuration tree. Laravel has no equivalent bundle registration or semantic config tree, so there is no supported install path there. If you only need the client, check in the source whether the transport classes can be instantiated outside the container.
- Which Laravel or Symfony versions does this package support?
- No Laravel version support is declared, because the package targets Symfony and pins Symfony component majors such as framework-bundle, http-client and serializer. Those constraints will pin dependencies that are unrelated to your business need. Laravel does carry Symfony components transitively, but not in a way that makes this bundle installable as-is.
- How does the bundle authenticate with the Idloom API, and can keys be rotated without a redeploy?
- The overview says the bundle handles authentication and exposes credentials and endpoints through configuration. It does not state whether Idloom uses a static API key, OAuth client credentials, or per-tenant keys, so verify this in the source before assuming anything. Check specifically whether credentials can be rotated without a redeploy and whether per-tenant keys are supported.
- Does the package return typed DTOs or raw arrays?
- That is not documented in the provided overview or README excerpt. If responses come back as raw arrays, most of the type-safety argument for adopting the package disappears and a thin first-party client is just as good. If they are immutable value objects, consider vendoring that DTO layer into your own namespace while keeping the MIT notice.
- Is gponty/symfony-idloom-api-bundle production-ready and actively maintained?
- Treat it as high risk: the package has 0 stars and 0 dependents, a single maintainer, and no CI or test-coverage evidence in the metadata. MIT gives you no warranty and no upstream security-response obligation, so vulnerability triage becomes your job. Its release cadence is also dictated by Idloom API changes rather than the maintainer's capacity, which is a real vendor lockstep risk.
- Should I use this bundle, vendor the client classes, or write my own Idloom client for Laravel?
- The ranked options are a thin first-party client using Laravel's Http facade or Symfony HttpClient (recommended), vendoring the client classes and DTOs into an internal namespace if the source proves well designed, or forking to replace the bundle wiring with a Laravel service provider, which is only worth it for a broad and non-trivial API surface. Installing the bundle in Laravel is not recommended. Make the build-versus-consume decision after reading the source, not the README.
- Does it handle pagination, retries with backoff, 429 rate limits and idempotency keys?
- Pagination, retry with backoff, 429 handling and idempotency keys are not described in the provided documentation. For registration and attendee writes idempotency keys matter, and without built-in backoff you will end up implementing retry logic yourself anyway. Confirm these behaviours in the source before relying on the package for any write operation.
- How do I test an Idloom API integration in Laravel?
- Wrap the integration behind a narrow contract such as an IdloomGateway interface with registerAttendee, findEvent and cancelRegistration methods, then bind an adapter and use Laravel's Http::fake() to stub responses so tests never reach Idloom. Symfony's HttpClient is also mockable, but container-wired bundle classes are harder to instantiate in isolation. This pattern keeps tests fast and lets you swap the transport later.
- Is it safe for attendee PII, and does it support webhooks?
- Attendee records are PII under GDPR and Idloom is EU-hosted, so request and response logging must be redacted and auditable; the package's logging behaviour is not documented, so verify it before enabling anything in production. Webhook support is also undocumented in the provided material, and polling may be the only ingestion path. If either concern matters to you, a first-party client gives you explicit control over redaction and ingestion.