# NOWATCH API The NOWATCH API Version: 0.9.0 ## Servers ``` /nowatch ``` ## Security ### bearer Type: http Scheme: bearer Bearer Format: JWT ## Download OpenAPI description [NOWATCH API](https://docs.api.nowatch.tech/_bundle/apis/@0.9.0/index.yaml) ## auth User authentication ### Register - [POST /v1/auth/register](https://docs.api.nowatch.tech/apis/auth/authcontroller_registerv1.md) ### Login - [POST /v2/auth/login](https://docs.api.nowatch.tech/apis/auth/authcontroller_loginv2.md) ### Admin login - [POST /v2/auth/login/admin](https://docs.api.nowatch.tech/apis/auth/authcontroller_loginadminv1.md) ### Create refresh token - [POST /v1/auth/refresh](https://docs.api.nowatch.tech/apis/auth/authcontroller_refreshtokenv1.md) ### Reset password - [POST /v1/auth/forgot_password](https://docs.api.nowatch.tech/apis/auth/authcontroller_forgotpasswordv1.md): Initiates users forgot password flow, user will receive a code from AWS in their email ### Change password - [POST /v1/auth/confirm_new_password](https://docs.api.nowatch.tech/apis/auth/authcontroller_confirmnewpasswordv1.md): Changes users password with verification code and new password ### Sign out - [POST /v1/auth/sign-out](https://docs.api.nowatch.tech/apis/auth/authcontroller_signoutv1.md): Revokes all tokens ### Login (deprecated) - [POST /v1/auth/login](https://docs.api.nowatch.tech/apis/auth/authcontroller_loginv1.md) ## user User data routes ### Fetch profile - [GET /v1/user](https://docs.api.nowatch.tech/apis/user/usercontroller_findonev1.md) ### Update profile - [PUT /v1/user](https://docs.api.nowatch.tech/apis/user/usercontroller_updatev1.md) ### Delete account - [DELETE /v1/user](https://docs.api.nowatch.tech/apis/user/usercontroller_deletev1.md) ### Request beta access - [POST /v1/user/beta_access](https://docs.api.nowatch.tech/apis/user/usercontroller_requestbetaaccessv1.md): The process is the following. 1) First the user requests beta 2) A email gets sent to legal@nowatch.com and the request is added to the database 3) A NOWATCH admin will login to the admin dashboard (test admin dashboard or production admin dashboard) and approve / deny the request ### Update password - [POST /v1/user/change_password](https://docs.api.nowatch.tech/apis/user/usercontroller_changepasswordv1.md) ### Fetch settings - [GET /v1/user/settings](https://docs.api.nowatch.tech/apis/user/usercontroller_fetchsettings.md): For extra context visit: User Settings Context ### Update settings - [PUT /v1/user/settings](https://docs.api.nowatch.tech/apis/user/usercontroller_updatesettings.md): For extra context visit: User Settings Context ### Export data - [GET /v1/user/export](https://docs.api.nowatch.tech/apis/user/usercontroller_export.md) ### Create data export - [POST /v1/user/export/create](https://docs.api.nowatch.tech/apis/user/usercontroller_createexport.md) ### List data exports - [GET /v1/user/export/list](https://docs.api.nowatch.tech/apis/user/usercontroller_listexports.md) ### Get export status - [GET /v1/user/export/{id}/status](https://docs.api.nowatch.tech/apis/user/usercontroller_getexportstatus.md) ### Get export result (download file) - [GET /v1/user/export/{id}/result](https://docs.api.nowatch.tech/apis/user/usercontroller_getexportresult.md) ### (Admin) Get all users - [GET /v1/user/admin/all](https://docs.api.nowatch.tech/apis/user/usercontroller_getallv1.md) ### (Admin) Get all beta requests - [GET /v1/user/admin/beta/all](https://docs.api.nowatch.tech/apis/user/usercontroller_findbetarequestsv1.md) ### (Admin) Set beta request status - [POST /v1/user/admin/beta/set](https://docs.api.nowatch.tech/apis/user/usercontroller_setbetav1.md) ### (Admin) Update any users profile - [PUT /v1/user/admin](https://docs.api.nowatch.tech/apis/user/usercontroller_updateadminv1.md) ### (Admin) Fetch any user profile by email - [GET /v1/user/admin](https://docs.api.nowatch.tech/apis/user/usercontroller_finduserbyemailv1.md) ### (Admin) Fetch list of users who have measurements since date - [GET /v1/user/admin/measurementsSince/{date}](https://docs.api.nowatch.tech/apis/user/usercontroller_userswithmeasurementsv1.md) ### (Admin) Fetch any user profile - [GET /v1/user/admin/{id}](https://docs.api.nowatch.tech/apis/user/usercontroller_findoneuserv1.md) ## firmware Firmware updates and downloads ### Fetch latest firmware - [GET /v3/firmware/latest](https://docs.api.nowatch.tech/apis/firmware/firmwarecontroller_latestv3.md): ### Fetch Latest Firmware (V3) This endpoint retrieves the latest compatible firmware version for the requesting client. The compatibility is determined by several factors: 1. User Early Access Status: If the authenticated user has isEarlyAccess set to true, the system will first attempt to find an early access firmware. If a compatible early access firmware is found, it will be returned. Otherwise, the system will proceed to look for a general release firmware. 2. Client Application Version (app-version header): The app-version header, provided by the client application (e.g., "1.2.3"), is crucial for determining firmware compatibility. Only firmwares with a min_app_version less than or equal to the client's app-version will be considered. 3. Platform (platform query parameter): Specifies the target platform for the firmware (e.g., IOS , ANDROID ). 4. Device (device query parameter): Specifies the target device model for the firmware (e.g., X , B ). Process to find the latest firmware: * Step 1: Fetch Candidate Firmwares: The system queries the database for all firmware records that match the provided platform and device . * Step 2: Prioritize Early Access (if applicable): If the user is an early access user, the system filters the candidate firmwares to include only those marked as earlyAccess: true . If no compatible early access firmware is found, it then considers general release firmwares. * Step 3: Filter by Application Version Compatibility: From the remaining candidate firmwares, only those where the client's app-version is greater than or equal to the firmware's min_app_version are kept. This ensures that the firmware is compatible with the client's current application. * Example: If the client's app-version is 1.5.0 : * A firmware with min_app_version: 1.4.0 is compatible ( 1.5.0 >= 1.4.0 ). * A firmware with min_app_version: 1.6.0 is incompatible ( 1.5.0 < 1.6.0 ). * Step 4: Sort by Version: The compatible firmwares are then sorted in descending order based on their version number (e.g., "1.0.1" is newer than "1.0.0"). * Step 5: Return Latest: The firmware at the top of the sorted list (i.e., the latest compatible version) is returned. Error Handling: * If the app-version header is missing or in an invalid format (expected x.y.z ), a 400 Bad Request error is returned. * If no compatible firmware is found after applying all filters, a 404 Not Found error is returned. ### Download specified version for device - [GET /v2/firmware/download](https://docs.api.nowatch.tech/apis/firmware/firmwarecontroller_downloadv2.md) ### Fetch latest firmware (deprecated) - [GET /v1/firmware/latest](https://docs.api.nowatch.tech/apis/firmware/firmwarecontroller_latestv1.md) ### Fetch latest firmware (deprecated) - [GET /v2/firmware/latest](https://docs.api.nowatch.tech/apis/firmware/firmwarecontroller_latestv2.md) ### Download latest firmware (deprecated) - [GET /v1/firmware/download_latest](https://docs.api.nowatch.tech/apis/firmware/firmwarecontroller_downloadlatestv1.md) ### Download specified version (deprecated) - [GET /v1/firmware/download](https://docs.api.nowatch.tech/apis/firmware/firmwarecontroller_downloadv1.md) ## admin-firmware Admin firmware management ### List all firmware versions - [GET /admin/firmware](https://docs.api.nowatch.tech/apis/admin-firmware/firmwareadmincontroller_listfirmware.md) ### Create new firmware version - [POST /admin/firmware](https://docs.api.nowatch.tech/apis/admin-firmware/firmwareadmincontroller_createfirmware.md) ### Set active firmware version - [PUT /admin/firmware/active](https://docs.api.nowatch.tech/apis/admin-firmware/firmwareadmincontroller_setactivefirmware.md) ### Delete firmware version - [DELETE /admin/firmware/{id}](https://docs.api.nowatch.tech/apis/admin-firmware/firmwareadmincontroller_deletefirmware.md) ## measurement Time series health data (heart rate, temperature, activity, etc.) ### Fetch users measurements - [GET /v1/measurement](https://docs.api.nowatch.tech/apis/measurement/measurementcontroller_fetchrawmeasurementsv1.md) ### Delete users measurements - [DELETE /v1/measurement](https://docs.api.nowatch.tech/apis/measurement/measurementcontroller_deleterawmeasurementsv1.md) ### Upload users measurements in a compressed ZIP file - [POST /v1/measurement/upload](https://docs.api.nowatch.tech/apis/measurement/measurementcontroller_uploadv1.md): This endpoint is used to upload time series data to the backend. The request is a multipart/form-data request with two parts: 1. file: The zipped CSV file containing the time-series data. 2. type: The name of the table the data belongs to. For extra context visit: Measurements Context ### Shows the latest measurements dates for a user per type - [GET /v1/measurement/oldest](https://docs.api.nowatch.tech/apis/measurement/measurementcontroller_fetcholdestmeasurementsv1.md) ## insight User insights, feedback, and reflections ### Upload users insight feedback - [POST /v2/insight/feedback](https://docs.api.nowatch.tech/apis/insight/insightcontroller_createfeedbackv2.md) ### Create a reflection for the day or week - [POST /v2/insight](https://docs.api.nowatch.tech/apis/insight/insightcontroller_createv2.md) ### Fetch reflection with instance id - [GET /v1/insight/{id}](https://docs.api.nowatch.tech/apis/insight/insightcontroller_fetchreflectionv1.md) ### Upload users insight feedback (deprecated) - [POST /v1/insight/feedback](https://docs.api.nowatch.tech/apis/insight/insightcontroller_createfeedbackv1.md) ### Create a reflection for the day or week (deprecated) - [POST /v1/insight](https://docs.api.nowatch.tech/apis/insight/insightcontroller_createv1.md) ## session Activity session tracking ### Creates new sessions - [POST /v1/session](https://docs.api.nowatch.tech/apis/session/sessioncontroller_createv1.md): For extra context visit: Sessions Context ### Fetch all user sessions based on start and end date - [GET /v1/session](https://docs.api.nowatch.tech/apis/session/sessioncontroller_findallv1.md): For extra context visit: Sessions Context ### Fetch session - [GET /v1/session/{id}](https://docs.api.nowatch.tech/apis/session/sessioncontroller_findonev1.md): For extra context visit: Sessions Context ### Update session - [PUT /v1/session/{id}](https://docs.api.nowatch.tech/apis/session/sessioncontroller_updatev1.md): For extra context visit: Sessions Context ### Delete session - [DELETE /v1/session/{id}](https://docs.api.nowatch.tech/apis/session/sessioncontroller_removev1.md): For extra context visit: Sessions Context ## checkin User check-ins and wellness tracking ### Creates new check-ins ('How do you feel?') - [POST /v1/checkin](https://docs.api.nowatch.tech/apis/checkin/checkincontroller_createv1.md): The Check-in feature (”How do you feel?” question) is designed to support users with greater awareness of their internal state by encouraging regular moments of self-reflection throughout the day. This question can appear randomly or after N minutes of prolonged stress. These settings are chosen by the user. They can choose the following options: * 0, 3, 6, or 9 daily random vibrations; * Prolonged stress vibrations (when in more than 5, 10, 15, or 20 minutes consecutively under stress); * Both random and prolonged stress vibrations. From each a Check-In, the following information can be obtained: * Origin of the check-in: user initiative, random vibration, or prolonged stress vibration. * How does the user feel: * Reactivity: very calm, calm, neutral, stressed, very stressed; * Valence: very negative, negative, neutrals, positive, very positive; * Related feelings: happy, sad, etc. * What was the user doing; * Who was the user with. ### Fetch all user checkins based on date range - [GET /v1/checkin](https://docs.api.nowatch.tech/apis/checkin/checkincontroller_findallv1.md) ### Fetch checkin - [GET /v1/checkin/{id}](https://docs.api.nowatch.tech/apis/checkin/checkincontroller_findonev1.md) ### Update checkin - [PUT /v1/checkin/{id}](https://docs.api.nowatch.tech/apis/checkin/checkincontroller_updatev1.md) ### Delete checkin - [DELETE /v1/checkin/{id}](https://docs.api.nowatch.tech/apis/checkin/checkincontroller_removev1.md) ## alarm User alarm management ### Creates new alarms - [POST /v1/alarm](https://docs.api.nowatch.tech/apis/alarm/alarmcontroller_createv1.md) ### Fetch all user alarms based on offset, limit - [GET /v1/alarm](https://docs.api.nowatch.tech/apis/alarm/alarmcontroller_findallv1.md) ### Fetch alarm - [GET /v1/alarm/{id}](https://docs.api.nowatch.tech/apis/alarm/alarmcontroller_findonev1.md) ### Update session - [PUT /v1/alarm/{id}](https://docs.api.nowatch.tech/apis/alarm/alarmcontroller_updatev1.md) ### Delete session - [DELETE /v1/alarm/{id}](https://docs.api.nowatch.tech/apis/alarm/alarmcontroller_removev1.md) ## day-feedback Daily feedback and mood tracking ### Creates new day feedback ('How was your day/sleep?') - [POST /v1/day-feedback](https://docs.api.nowatch.tech/apis/day-feedback/dayfeedbackcontroller_createv1.md): Each day, the user receives two questions in the app, under the Now tab. ### "How was your day?" question This question appears once each day, when you open the app after the theoretical end of the workday (between 5 p.m. and midnight). * Possible values: very bad, bad, okay, good, very good. ### "How was your sleep?" question This question appears once each day, when you open the app after the theoretical end of the night of sleep (between 4 a.m. and midday). * Possible values: very bad, bad, okay, good, very good. ### Fetch all user day feedbacks based on type, start, end date - [GET /v1/day-feedback](https://docs.api.nowatch.tech/apis/day-feedback/dayfeedbackcontroller_findallv1.md) ### Fetch day-feedback - [GET /v1/day-feedback/{id}](https://docs.api.nowatch.tech/apis/day-feedback/dayfeedbackcontroller_findonev1.md) ### Update day-feedback - [PUT /v1/day-feedback/{id}](https://docs.api.nowatch.tech/apis/day-feedback/dayfeedbackcontroller_updatev1.md) ### Delete day-feedback - [DELETE /v1/day-feedback/{id}](https://docs.api.nowatch.tech/apis/day-feedback/dayfeedbackcontroller_removev1.md) ## sleep Sleep logs and sleep data ### Fetches a single sleep log for a user - [GET /v1/sleep/log/{id}](https://docs.api.nowatch.tech/apis/sleep/sleepcontroller_findsleeplogv1.md) ### Update a sleep log for a user - [PUT /v1/sleep/log/{id}](https://docs.api.nowatch.tech/apis/sleep/sleepcontroller_updatesleeplogv1.md) ### Delete a sleep log for a user - [DELETE /v1/sleep/log/{id}](https://docs.api.nowatch.tech/apis/sleep/sleepcontroller_deletesleeplogv1.md) ### Fetches all sleep logs for a user - [GET /v1/sleep/log](https://docs.api.nowatch.tech/apis/sleep/sleepcontroller_findallsleeplogsv1.md) ### Create a sleep log for a user - [POST /v1/sleep/log](https://docs.api.nowatch.tech/apis/sleep/sleepcontroller_createsleeplogv1.md) ### Fetches all processed sleep records for a user - [GET /v2/sleep/processed](https://docs.api.nowatch.tech/apis/sleep/sleepcontroller_findprocessedsleepv2.md) ### Fetches a single sleep record for a user - [GET /v2/sleep/{id}](https://docs.api.nowatch.tech/apis/sleep/sleepcontroller_findsleepv2.md) ### Update or create a sleep record for a user - [PUT /v2/sleep/{id}](https://docs.api.nowatch.tech/apis/sleep/sleepcontroller_updatesleepv2.md) ### Delete sleep record for user - [DELETE /v2/sleep/{id}](https://docs.api.nowatch.tech/apis/sleep/sleepcontroller_deletesleepv2.md) ### Fetches all sleep records for a user - [GET /v2/sleep](https://docs.api.nowatch.tech/apis/sleep/sleepcontroller_findallsleepv2.md) ### Create sleep record for a user - [POST /v2/sleep](https://docs.api.nowatch.tech/apis/sleep/sleepcontroller_createsleepv2.md) ### Update or create multiple sleep records for a user - [PUT /v2/sleep/batch](https://docs.api.nowatch.tech/apis/sleep/sleepcontroller_batchsleepupdatev2.md) ## activity Sessions wrapper for activities ### Creates a new activity - [POST /v1/activity](https://docs.api.nowatch.tech/apis/activity/activitycontroller_create.md): For extra context visit: Sessions Context ### Fetch all activites for date range - [GET /v1/activity](https://docs.api.nowatch.tech/apis/activity/activitycontroller_findactivities.md): For extra context visit: Sessions Context ### Fetch activity by id - [GET /v1/activity/{id}](https://docs.api.nowatch.tech/apis/activity/activitycontroller_findactivity.md): For extra context visit: Sessions Context ### Update activity - [PUT /v1/activity/{id}](https://docs.api.nowatch.tech/apis/activity/activitycontroller_update.md): For extra context visit: Sessions Context ### Delete a activity - [DELETE /v1/activity/{id}](https://docs.api.nowatch.tech/apis/activity/activitycontroller_remove.md): For extra context visit: Sessions Context ## intention Sessions wrapper for intentions ### Creates a new intention - [POST /v1/intention](https://docs.api.nowatch.tech/apis/intention/intentioncontroller_create.md): For extra context visit: Sessions Context ### Fetch all intentions for date range - [GET /v1/intention](https://docs.api.nowatch.tech/apis/intention/intentioncontroller_find.md): For extra context visit: Sessions Context ### Fetch intention by id - [GET /v1/intention/{id}](https://docs.api.nowatch.tech/apis/intention/intentioncontroller_findone.md): For extra context visit: Sessions Context ### Update intention - [PUT /v1/intention/{id}](https://docs.api.nowatch.tech/apis/intention/intentioncontroller_update.md): For extra context visit: Sessions Context ### Delete a intention - [DELETE /v1/intention/{id}](https://docs.api.nowatch.tech/apis/intention/intentioncontroller_remove.md): For extra context visit: Sessions Context ## statistics Aggregated health statistics ### Get multiple statistics - [GET /v1/statistics](https://docs.api.nowatch.tech/apis/statistics/statisticscontroller_getmanystatistics.md): For more information visit Statistics Context ### Create multiple statistics - [POST /v1/statistics](https://docs.api.nowatch.tech/apis/statistics/statisticscontroller_createstatistics.md): For more information visit Statistics Context ### Create or update multiple statistics - [PUT /v1/statistics/batch](https://docs.api.nowatch.tech/apis/statistics/statisticscontroller_createmanystatistics.md): For more information visit Statistics Context ### Create or update a single statistic - [PUT /v1/statistics/{date}/{type}](https://docs.api.nowatch.tech/apis/statistics/statisticscontroller_createorupdatestatistics.md): For more information visit Statistics Context ### Delete a single statistic - [DELETE /v1/statistics/{date}/{type}](https://docs.api.nowatch.tech/apis/statistics/statisticscontroller_deleteonestatistics.md): For more information visit Statistics Context ## sharing Manage sharing your data with other people ### Share your dashboard data with a user - [POST /v1/sharing/invite](https://docs.api.nowatch.tech/apis/sharing/sharingcontroller_createinvite.md): Creates an invitation to share your dashboard with another user. The recipient will receive an email notification and can accept or reject the invitation. You can specify from which date the data should be shared. For extra context visit: Sharing Context ### Delete a sent sharing invite - [DELETE /v1/sharing/invite](https://docs.api.nowatch.tech/apis/sharing/sharingcontroller_deleteinvite.md): Cancels a pending invitation that was sent to another user. This can only be done before the invitation has been accepted. For extra context visit: Sharing Context ### Resend a sharing invite - [PUT /v1/sharing/invite/resend](https://docs.api.nowatch.tech/apis/sharing/sharingcontroller_resendinvite.md): Resends an invitation email to a user who hasn't yet responded to a previous invitation. This is useful when the original email was missed or expired. For extra context visit: Sharing Context ### Accept a sharing invite - [POST /v1/sharing/invite/accept](https://docs.api.nowatch.tech/apis/sharing/sharingcontroller_acceptinvite.md): Accepts an invitation to view another user's dashboard. Once accepted, the dashboard will appear in your shared dashboards list and you can access their data from the specified date onwards. For extra context visit: Sharing Context ### Reject a sharing invite - [POST /v1/sharing/invite/reject](https://docs.api.nowatch.tech/apis/sharing/sharingcontroller_rejectinvite.md): Declines an invitation to view another user's dashboard. The sender will not be notified of the rejection. For extra context visit: Sharing Context ### Get all dashboards user is sharing - [GET /v1/sharing](https://docs.api.nowatch.tech/apis/sharing/sharingcontroller_getshared.md): Retrieves a list of all users with whom the authenticated user is currently sharing their dashboard. For extra context visit: Sharing Context ### Stop sharing a dashboard - [DELETE /v1/sharing](https://docs.api.nowatch.tech/apis/sharing/sharingcontroller_stopsharing.md): Revokes another user's access to your dashboard. The recipient will no longer be able to view your dashboard data. For extra context visit: Sharing Context ### Update shared since for a dashboard user is sharing - [POST /v1/sharing/shared-since](https://docs.api.nowatch.tech/apis/sharing/sharingcontroller_updatesharedsince.md): Modifies the start date from which data is shared with a specific user. This allows you to extend or restrict the date range of shared data. For extra context visit: Sharing Context ### Get all invites sent by the user - [GET /v1/sharing/invites/sent](https://docs.api.nowatch.tech/apis/sharing/sharingcontroller_getsentinvites.md): Retrieves a list of all sharing invitations that the authenticated user has sent to others, including their current status (pending, accepted, or rejected). For extra context visit: Sharing Context ### Get all invites received by the user - [GET /v1/sharing/invites/received](https://docs.api.nowatch.tech/apis/sharing/sharingcontroller_getreceivedinvites.md): Retrieves a list of all sharing invitations that the authenticated user has received from others, including their current status. For extra context visit: Sharing Context ### Get all sharing requests sent by the user - [GET /v1/sharing/requests/sent](https://docs.api.nowatch.tech/apis/sharing/sharingcontroller_getsentrequests.md): Retrieves all requests that the authenticated user has sent to others asking for access to their dashboards. For extra context visit: Sharing Context ### Get all sharing requests received by the user - [GET /v1/sharing/requests/received](https://docs.api.nowatch.tech/apis/sharing/sharingcontroller_getreceivedrequests.md): Retrieves all requests from other users asking to view the authenticated user's dashboard. For extra context visit: Sharing Context ### Request access to a user's dashboard - [POST /v1/sharing/request](https://docs.api.nowatch.tech/apis/sharing/sharingcontroller_createrequest.md): Sends a request to another user asking for access to view their dashboard. The recipient can choose to accept or reject the request. For extra context visit: Sharing Context ### Delete a sent sharing request - [DELETE /v1/sharing/request](https://docs.api.nowatch.tech/apis/sharing/sharingcontroller_deleterequest.md): Cancels a pending request that was sent to another user asking for dashboard access. For extra context visit: Sharing Context ### Accept a sharing request - [POST /v1/sharing/request/accept](https://docs.api.nowatch.tech/apis/sharing/sharingcontroller_acceptrequest.md): Accepts a request from another user to view your dashboard. Once accepted, the requester will gain access to your dashboard data from the specified date. For extra context visit: Sharing Context ### Reject a sharing request - [POST /v1/sharing/request/reject](https://docs.api.nowatch.tech/apis/sharing/sharingcontroller_rejectrequest.md): Declines a request from another user to view your dashboard. The requester will not be notified of the rejection. For extra context visit: Sharing Context ### Resend a sharing request - [PUT /v1/sharing/request/resend](https://docs.api.nowatch.tech/apis/sharing/sharingcontroller_resendrequest.md): Resends a request email to a user who hasn't yet responded to a previous dashboard access request. For extra context visit: Sharing Context ## shared Manage other people's data shared with you ### Get all dashboards shared with the user - [GET /v1/shared](https://docs.api.nowatch.tech/apis/shared/sharedcontroller_getsharedwithme.md): Retrieves all dashboards that other users have shared with the authenticated user. For extra context visit: Sharing Context ### Delete a shared dashboard - [DELETE /v1/shared](https://docs.api.nowatch.tech/apis/shared/sharedcontroller_deleteshared.md): Removes a shared dashboard from the authenticated user's list. This effectively stops viewing access to the shared dashboard without notifying the owner. For extra context visit: Sharing Context ### Get all groups owned by the user - [GET /v1/shared/groups](https://docs.api.nowatch.tech/apis/shared/sharedcontroller_getgroupsownedbyuser.md): Retrieves all groups created by the authenticated user, including the members of each group. Groups allow users to organize their shared dashboards. For extra context visit: Sharing Context ### Create a new group - [POST /v1/shared/groups](https://docs.api.nowatch.tech/apis/shared/sharedcontroller_creategroup.md): Creates a new group for organizing shared dashboards. Groups allow users to categorize and manage multiple shared users more efficiently. For extra context visit: Sharing Context ### Rename a group - [PATCH /v1/shared/groups/{groupId}](https://docs.api.nowatch.tech/apis/shared/sharedcontroller_renamegroup.md): Updates the name of an existing group. The user must own the group to rename it. For extra context visit: Sharing Context ### Delete a group - [DELETE /v1/shared/groups/{groupId}](https://docs.api.nowatch.tech/apis/shared/sharedcontroller_deletegroup.md): Deletes a group. The user must own the group to delete it. Deleting a group does not affect the shared dashboards themselves, only the grouping. For extra context visit: Sharing Context ### Update custom name and icon color for a shared dashboard - [POST /v1/shared/custom](https://docs.api.nowatch.tech/apis/shared/sharedcontroller_updatecustom.md): Allows users to personalize how a shared dashboard appears to them by setting a custom name and icon color. This only affects the viewing user's experience and does not change the dashboard for others. For extra context visit: Sharing Context ### Upload custom profile picture for a shared dashboard - [POST /v1/shared/custom/profile-picture](https://docs.api.nowatch.tech/apis/shared/sharedcontroller_uploadcustomprofilepicture.md): Uploads a custom profile picture for a shared dashboard. The user must have access to the shared dashboard. Max file size is 5MB. Allowed formats: jpg, png, webp. For extra context visit: Sharing Context ### Delete custom profile picture for a shared dashboard - [DELETE /v1/shared/custom/profile-picture](https://docs.api.nowatch.tech/apis/shared/sharedcontroller_deletecustomprofilepicture.md): Deletes the custom profile picture for a shared dashboard. The user must have access to the shared dashboard. For extra context visit: Sharing Context ### Add a user to a group - [POST /v1/shared/groups/{groupId}/members](https://docs.api.nowatch.tech/apis/shared/sharedcontroller_addusertogroup.md): Adds a shared user to an existing group. The user to be added must already be sharing their dashboard with the authenticated user. For extra context visit: Sharing Context ### Remove a user from a group - [DELETE /v1/shared/groups/{groupId}/members](https://docs.api.nowatch.tech/apis/shared/sharedcontroller_removeuserfromgroup.md): Removes a shared user from a group. This does not stop the dashboard sharing relationship, it only removes them from the group. For extra context visit: Sharing Context ## telemetry Application telemetry data (spans, metrics, logs) ### Send spans - [POST /v1/telemetry/spans](https://docs.api.nowatch.tech/apis/telemetry/telemetrycontroller_receivespans.md) ### Send metrics - [POST /v1/telemetry/metrics](https://docs.api.nowatch.tech/apis/telemetry/telemetrycontroller_receivemetrics.md) ### Send logs - [POST /v1/telemetry/logs](https://docs.api.nowatch.tech/apis/telemetry/telemetrycontroller_receivelogs.md)