Register push token

Overview

Registers the device's push token for the authenticated session, so RAID can send push notifications to the app.

The registration is bound to the personal access token used for the call: there is one push token per access token. Calling the endpoint again with the same access token replaces the previous registration instead of adding a second one.

Controller: App\Http\Controllers\Api\V1\Profile\PushTokenController::store()
Route name: api.v1.profile.push-token.store

Authentication

Type: Bearer Token
Header: Authorization: Bearer {token}

Request

Method: PUT
Path: /api/v1/profile/push-token
Content-Type: application/json

Body

{
  "provider": "expo",
  "token": "ExponentPushToken[xxxxxxxxxxxxxxxxxxxxxx]",
  "platform": "ios",
  "app_version": "1.2.3"
}

Field	Type	Required	Validation	Description
`provider`	`string`	Yes	`required\|enum`	Push provider. Only `expo` is accepted
`token`	`string`	Yes	`required\|string\|max:255`, plus `regex` when `provider` is `expo`	Expo token, in the form `ExponentPushToken[...]` or `ExpoPushToken[...]`
`platform`	`string`	Yes	`required\|enum`	`ios` or `android`
`app_version`	`string`	No	`nullable\|string\|max:32`	Version of the app that registered the token

Validated by App\Http\Requests\Api\V1\Profile\StorePushTokenRequest.

Example request

Response `200 OK`

{
  "success": true,
  "status": "success",
  "message": "OK",
  "data": {
    "provider": "expo",
    "platform": "ios",
    "app_version": "1.2.3",
    "updated_at": "2026-10-14T09:30:00.000000Z"
  }
}

The token value itself is not echoed back. app_version is null when it was not sent.

Errors

`401 Unauthorized`

Standard shape. message is one of Unauthenticated, Invalid token, Token expired.

`403 Forbidden`

The account is suspended. Every token of the account is revoked at the same time.

{
  "success": false,
  "status": "error",
  "message": "Account suspended"
}

`422 Unprocessable Entity` - validation

{
  "success": false,
  "status": "error",
  "message": "Validation failed",
  "errors": {
    "token": ["The token field format is invalid."],
    "platform": ["The selected platform is invalid."]
  }
}

Notes

One push token per access token. A second PUT with the same access token replaces the first, including when the token value or the platform changes.

A device belongs to one account at a time. If the token value is already registered under a different access token (of any user), that other registration is removed first. A phone now used by user B therefore never notifies user A.

The registration disappears with its access token. It is deleted automatically on logout, password reset, revocation of the token, account suspension and expiry pruning. The app must register again after every login.

Use DELETE /api/v1/profile/push-token to stop notifications without logging out.

Push payload

Notifications carry a data.type that tells the app what happened. The values the app can receive:

`data.type`	Extra fields	Meaning
`certification_issued`	`log_code`	A certification was issued to the diver. `log_code` is the certification identifier used by the diver routes `certifications/{log_code}/...`

Source: docs/api/profile/PUT_push_token.md

curl --location --request PUT 'https://test.diveraid.com/api/v1/profile/push-token' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "provider": "expo", "token": "string", "platform": "ios", "app_version": "string" }'

{ "status": "success", "message": "string", "data": { "provider": "expo", "platform": "ios", "app_version": "string", "updated_at": "2019-08-24T14:15:22.123Z" } }

Register push token

Overview#

Authentication#

Request#

Body#

Example request#

Response 200 OK#

Errors#

401 Unauthorized#

403 Forbidden#

422 Unprocessable Entity - validation#

Notes#

Push payload#

Request

Responses

Overview

Authentication

Request

Body

Example request

Response `200 OK`

Errors

`401 Unauthorized`

`403 Forbidden`

`422 Unprocessable Entity` - validation

Notes

Push payload