> ## Documentation Index > Fetch the complete documentation index at: https://docs.prisme.ai/llms.txt > Use this file to discover all available pages before exploring further. # Register the signed-in user's mobile device for push notifications > Stores the device's APNs or FCM token and its notification key (RFC 8291), sealed at rest. Registering again with the same `device_id` updates it. A former registration of the same token, whichever the account, is replaced. The app draws a `device_id` at sign-in and forgets it at sign-out; on `409` it draws a new one and retries. Org API keys are refused. ## OpenAPI ````yaml /api-reference/agent-factory/swagger.yml post /v1/push/devices openapi: 3.0.3 info: version: 1.0.0 title: Agent Factory API description: | Public REST API for the Agent Factory workspace - agents, conversations, messages, tools, artifacts, sharing, ratings, and discovery. Powered by Prisme.ai's runtime; all endpoints are exposed under each workspace's webhook namespace. contact: name: Prisme.ai url: https://prisme.ai servers: - url: https://{host}/v2/workspaces/slug:agent-factory/webhooks description: Prisme.ai workspace webhooks variables: host: default: api.studio.prisme.ai description: API host (override for self-hosted or sandbox) security: - BearerAuth: [] - OrgApiKeyAuth: [] tags: - name: Agents description: Agent CRUD, discovery, AGENTS.md import/export. - name: Access description: Agent access bindings, sharing, and access requests. - name: ApiKeys description: Agent-scoped API key management (mint, revoke, rotate). - name: Publishing description: Publish or discard draft changes on an agent. - name: Ratings description: User ratings on published agents. - name: Profiles description: >- Agent profiles/presets catalog (simple, workflow, agent_light, agent_full, orchestrator). - name: Activity description: Activity feed for agents (events, errors, lifecycle changes). - name: Analytics description: Agent usage analytics (series + summary). - name: Conversations description: Conversations on an agent (CRUD, archive, star). - name: Messages description: Send messages to an agent (synchronous send + SSE stream). - name: Tasks description: Async task lifecycle (list, fetch, cancel, resolve, subscribe). - name: Artifacts description: Generated artifacts (files, code, content) attached to a task. - name: Shares description: Conversation, message, and artifact share-link snapshots. - name: A2A description: Agent-to-agent JSON-RPC 2.0 gateway (well-known agent.json + RPC). - name: Tools description: Per-agent tool catalogue (system tools, MCP servers, function tools). - name: Retention description: Per-agent and org-wide conversation retention policies. - name: Traces description: >- Execution traces of agent turns (editor debugging, `agent-factory:traces:read`). - name: Evaluations description: Agent evaluation runs and results. - name: Push description: Mobile device registration for push notifications. - name: Admin description: | GDPR operations called by the AI Insights admin screens. They require elevated permissions: the caller must be a platform administrator (`platformRole` `superadmin` or `root`). The export route also lets a user export their own data. Each route is rate limited to 10 calls per hour per caller. paths: /v1/push/devices: post: tags: - Push summary: Register the signed-in user's mobile device for push notifications description: > Stores the device's APNs or FCM token and its notification key (RFC 8291), sealed at rest. Registering again with the same `device_id` updates it. A former registration of the same token, whichever the account, is replaced. The app draws a `device_id` at sign-in and forgets it at sign-out; on `409` it draws a new one and retries. Org API keys are refused. operationId: registerPushDevice requestBody: required: true content: application/json: schema: type: object additionalProperties: false required: - device_id - platform - token - p256dh - auth properties: device_id: type: string pattern: ^[A-Za-z0-9_-]{16,64}$ platform: type: string enum: - ios - android token: type: string description: APNs or FCM token. p256dh: type: string description: Uncompressed P-256 public key, base64url. auth: type: string description: 16-byte secret, base64url. environment: type: string enum: - production - development description: APNs environment. Required on iOS, refused on Android. topic: type: string description: APNs topic (the app bundle id). iOS only. responses: '204': description: Device registered. '400': description: >- Invalid registration. `error` names the field (`InvalidToken`, `InvalidKey`, ...). content: application/json: schema: $ref: '#/components/schemas/Error' '403': description: Not a user credential. content: application/json: schema: $ref: '#/components/schemas/Error' '409': description: >- This `device_id` belongs to another account (`error` is `DeviceIdTaken`). content: application/json: schema: $ref: '#/components/schemas/Error' '503': description: Push notifications are not configured on this instance. content: application/json: schema: $ref: '#/components/schemas/Error' security: - BearerAuth: [] components: schemas: Error: type: object required: - error - message properties: error: type: string description: >- Stable PascalCase or SNAKE_CASE error code (e.g. AgentNotFound, VALIDATION_ERROR, FORBIDDEN, METHOD_NOT_ALLOWED). message: type: string description: Human-readable error message. details: type: object description: Optional structured context for the error. additionalProperties: true securitySchemes: BearerAuth: type: http scheme: bearer bearerFormat: JWT description: | User-bound credential carrying an identity: either a session JWT or a user access token (`at:*`) generated from the user settings UI. Send as `Authorization: Bearer `. Org API keys (`iak_*`) are **not** accepted here - they carry no user identity. Use the `x-prismeai-api-key` header instead (see `OrgApiKeyAuth`). OrgApiKeyAuth: type: apiKey in: header name: x-prismeai-api-key description: | Organization API key (`iak_{orgSlug}_{uuid}`). Unlike `Authorization: Bearer`, this credential is **not** tied to a user identity - it is bound to the org and its effective access is defined by the scopes / permission rules attached to it (it can be restricted to a single project, or kept broader). For Agent Factory, these keys can be generated directly from the Agent Factory UI (in addition to the AI Governance settings). Send as `x-prismeai-api-key: iak_...`. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.