Idempotently associate an existing application to a group
PUT/public/v1/groups/:group_id/applications/:application_identifier
Associates an existing application with a group. The operation is idempotent: if the application is already associated with the group, no duplicate association is created. Distribution to devices is dispatched separately; check the dispatch_status field for the processing outcome. Pass optional version_id to select an active package version belonging to this application for this group. This creates or replaces the group-specific version (Rails test/homologation distribution), without changing the current version or other groups. A matching contingency version is cleared, as in Rails. Omitting version_id preserves any existing group-specific version. Enterprise apps do not support version selection. A new association or changed version returns 202; repeating the same selection returns 200. Acceptance does not confirm installation on devices.
Request
Responses
- 200
- 202
- 401
- 403
- 404
- 409
- 422
- 429
- 500
- 503
The association was already active; no row was duplicated. Dispatch is reconciled and deduplicated during the configured TTL, and may be re-enqueued after that period.
Application associated with the group. The distribution dispatch outcome is reported in the dispatch_status field.
Missing, expired, or invalid JWT; the response may come from Kong or from the API.
Unauthorized scope, tenant, or group.
Resource not found in the authenticated tenant.
Resource state or identity is ambiguous/conflicting.
Invalid parameter, payload, or cursor; detail also covers the native FastAPI/Pydantic error list.
Rate limit exceeded.
Data invariant violation or invalid internal configuration.
Pool, queue, or storage capacity temporarily unavailable.