diff --git a/api-reference/endpoints/points/get-all-points-triggers.mdx b/api-reference/endpoints/points/get-all-points-triggers.mdx
new file mode 100644
index 0000000..6673a6b
--- /dev/null
+++ b/api-reference/endpoints/points/get-all-points-triggers.mdx
@@ -0,0 +1,3 @@
+---
+openapi: get /points/triggers
+---
diff --git a/api-reference/endpoints/points/get-points-summary.mdx b/api-reference/endpoints/points/get-points-summary.mdx
new file mode 100644
index 0000000..7ac2423
--- /dev/null
+++ b/api-reference/endpoints/points/get-points-summary.mdx
@@ -0,0 +1,3 @@
+---
+openapi: get /points/summary
+---
diff --git a/api-reference/endpoints/users/get-a-users-points-summary.mdx b/api-reference/endpoints/users/get-a-users-points-summary.mdx
new file mode 100644
index 0000000..baaa426
--- /dev/null
+++ b/api-reference/endpoints/users/get-a-users-points-summary.mdx
@@ -0,0 +1,3 @@
+---
+openapi: get /users/{id}/points/event-summary
+---
diff --git a/api-reference/endpoints/users/get-a-users-points.mdx b/api-reference/endpoints/users/get-a-users-points.mdx
new file mode 100644
index 0000000..578d3b9
--- /dev/null
+++ b/api-reference/endpoints/users/get-a-users-points.mdx
@@ -0,0 +1,3 @@
+---
+openapi: get /users/{id}/points
+---
diff --git a/api-reference/openapi.yml b/api-reference/openapi.yml
index d87d17f..49f8f77 100644
--- a/api-reference/openapi.yml
+++ b/api-reference/openapi.yml
@@ -1,7 +1,7 @@
 openapi: 3.1.0
 info:
   title: Trophy
-  version: '1.0.4'
+  version: "1.0.4"
 paths:
   /achievements:
     get:
@@ -10,14 +10,14 @@ paths:
       tags:
         - Achievements
       responses:
-        '200':
+        "200":
           description: Successful operation
           content:
             application/json:
               schema:
                 type: array
                 items:
-                  $ref: '#/components/schemas/AchievementWithStatsResponse'
+                  $ref: "#/components/schemas/AchievementWithStatsResponse"
               examples:
                 Successful operation:
                   value:
@@ -47,24 +47,24 @@ paths:
                       streakLength: 10
                       completions: 2
                       completedPercentage: 20
-        '401':
-          description: 'Unauthorized'
+        "401":
+          description: "Unauthorized"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
-        '404':
-          description: 'Achievements not found'
+                $ref: "#/components/schemas/ErrorBody"
+        "404":
+          description: "Achievements not found"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
-        '422':
-          description: 'Unprocessible Entity'
+                $ref: "#/components/schemas/ErrorBody"
+        "422":
+          description: "Unprocessible Entity"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
+                $ref: "#/components/schemas/ErrorBody"
       summary: Get all achievements and their completion stats
       security:
         - ApiKeyAuth: []
@@ -83,12 +83,12 @@ paths:
             type: string
           example: finish-onboarding
       responses:
-        '201':
+        "201":
           description: Successful operation
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/AchievementCompletionResponse'
+                $ref: "#/components/schemas/AchievementCompletionResponse"
               examples:
                 Successful operation:
                   value:
@@ -100,25 +100,25 @@ paths:
                       description: Complete the onboarding process.
                       badgeUrl: https://example.com/badge.png
                       key: finish-onboarding
-                      achievedAt: '2021-01-01T00:00:00Z'
-        '401':
-          description: 'Unauthorized'
+                      achievedAt: "2021-01-01T00:00:00Z"
+        "401":
+          description: "Unauthorized"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
-        '404':
-          description: 'Achievement Not Found'
+                $ref: "#/components/schemas/ErrorBody"
+        "404":
+          description: "Achievement Not Found"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
-        '422':
-          description: 'Unprocessible Entity'
+                $ref: "#/components/schemas/ErrorBody"
+        "422":
+          description: "Unprocessible Entity"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
+                $ref: "#/components/schemas/ErrorBody"
       summary: Mark an achievement as completed
       security:
         - ApiKeyAuth: []
@@ -130,7 +130,7 @@ paths:
               type: object
               properties:
                 user:
-                  $ref: '#/components/schemas/UpdatedUser'
+                  $ref: "#/components/schemas/UpdatedUser"
                   description: The user that completed the achievement.
               required:
                 - user
@@ -157,12 +157,12 @@ paths:
             type: string
           example: words-written
       responses:
-        '201':
+        "201":
           description: Created event
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/EventResponse'
+                $ref: "#/components/schemas/EventResponse"
               examples:
                 Successful operation:
                   value:
@@ -177,32 +177,32 @@ paths:
                         metricValue: 500
                         name: 500 words written
                         description: Write 500 words in the app.
-                        achievedAt: '2020-01-01T00:00:00Z'
+                        achievedAt: "2020-01-01T00:00:00Z"
                     currentStreak:
                       length: 1
                       frequency: daily
-                      started: '2025-04-02'
-                      periodStart: '2025-03-31'
-                      periodEnd: '2025-04-05'
-                      expires: '2025-04-12'
-        '400':
-          description: 'Bad Request'
+                      started: "2025-04-02"
+                      periodStart: "2025-03-31"
+                      periodEnd: "2025-04-05"
+                      expires: "2025-04-12"
+        "400":
+          description: "Bad Request"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
-        '401':
-          description: 'Unauthorized'
+                $ref: "#/components/schemas/ErrorBody"
+        "401":
+          description: "Unauthorized"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
-        '422':
-          description: 'Unprocessible Entity'
+                $ref: "#/components/schemas/ErrorBody"
+        "422":
+          description: "Unprocessible Entity"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
+                $ref: "#/components/schemas/ErrorBody"
       summary: Send a metric change event
       security:
         - ApiKeyAuth: []
@@ -214,7 +214,7 @@ paths:
               type: object
               properties:
                 user:
-                  $ref: '#/components/schemas/UpsertedUser'
+                  $ref: "#/components/schemas/UpsertedUser"
                   description: The user that triggered the event.
                 value:
                   type: number
@@ -232,7 +232,7 @@ paths:
                   user:
                     email: user@example.com
                     tz: Europe/London
-                    id: '18'
+                    id: "18"
                   value: 750
   /users:
     post:
@@ -249,15 +249,15 @@ paths:
           application/json:
             schema:
               type: object
-              $ref: '#/components/schemas/UpsertedUser'
+              $ref: "#/components/schemas/UpsertedUser"
               description: The user object.
       responses:
-        '201':
+        "201":
           description: Identified user
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/User'
+                $ref: "#/components/schemas/User"
                 examples:
                   Successful operation:
                     value:
@@ -265,26 +265,26 @@ paths:
                       email: user@example.com
                       tz: Europe/London
                       subscribedToEmails: true
-                      created: '2021-01-01T00:00:00Z'
-                      updated: '2021-01-01T00:00:00Z'
-        '400':
-          description: 'Bad Request'
+                      created: "2021-01-01T00:00:00Z"
+                      updated: "2021-01-01T00:00:00Z"
+        "400":
+          description: "Bad Request"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
-        '422':
-          description: 'Unprocessible Entity'
+                $ref: "#/components/schemas/ErrorBody"
+        "422":
+          description: "Unprocessible Entity"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
-        '401':
-          description: 'Unauthorized'
+                $ref: "#/components/schemas/ErrorBody"
+        "401":
+          description: "Unauthorized"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
+                $ref: "#/components/schemas/ErrorBody"
   /users/{id}:
     get:
       description: Get a single user.
@@ -303,12 +303,12 @@ paths:
       security:
         - ApiKeyAuth: []
       responses:
-        '200':
+        "200":
           description: Found user
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/User'
+                $ref: "#/components/schemas/User"
                 examples:
                   Successful operation:
                     value:
@@ -316,26 +316,26 @@ paths:
                       email: user@example.com
                       tz: Europe/London
                       subscribedToEmails: true
-                      created: '2021-01-01T00:00:00Z'
-                      updated: '2021-01-01T00:00:00Z'
-        '400':
-          description: 'Bad Request'
+                      created: "2021-01-01T00:00:00Z"
+                      updated: "2021-01-01T00:00:00Z"
+        "400":
+          description: "Bad Request"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
-        '422':
-          description: 'Unprocessible Entity'
+                $ref: "#/components/schemas/ErrorBody"
+        "422":
+          description: "Unprocessible Entity"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
-        '401':
-          description: 'Unauthorized'
+                $ref: "#/components/schemas/ErrorBody"
+        "401":
+          description: "Unauthorized"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
+                $ref: "#/components/schemas/ErrorBody"
     patch:
       description: Update a user.
       operationId: users_update
@@ -357,19 +357,19 @@ paths:
         content:
           application/json:
             schema:
-              $ref: '#/components/schemas/UpdatedUser'
+              $ref: "#/components/schemas/UpdatedUser"
               description: The user object.
             example:
               id: user-id
               email: user@example.com
               tz: Europe/London
       responses:
-        '200':
+        "200":
           description: Updated user
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/User'
+                $ref: "#/components/schemas/User"
                 examples:
                   Successful operation:
                     value:
@@ -377,26 +377,26 @@ paths:
                       email: user@example.com
                       tz: Europe/London
                       subscribedToEmails: true
-                      created: '2021-01-01T00:00:00Z'
-                      updated: '2021-01-01T00:00:00Z'
-        '400':
-          description: 'Bad Request'
+                      created: "2021-01-01T00:00:00Z"
+                      updated: "2021-01-01T00:00:00Z"
+        "400":
+          description: "Bad Request"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
-        '422':
-          description: 'Unprocessible Entity'
+                $ref: "#/components/schemas/ErrorBody"
+        "422":
+          description: "Unprocessible Entity"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
-        '401':
-          description: 'Unauthorized'
+                $ref: "#/components/schemas/ErrorBody"
+        "401":
+          description: "Unauthorized"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
+                $ref: "#/components/schemas/ErrorBody"
   /users/{id}/metrics:
     get:
       description: Get a single user's progress against all active metrics.
@@ -412,14 +412,14 @@ paths:
             type: string
           example: userId
       responses:
-        '200':
+        "200":
           description: Successful operation
           content:
             application/json:
               schema:
                 type: array
                 items:
-                  $ref: '#/components/schemas/MetricResponse'
+                  $ref: "#/components/schemas/MetricResponse"
               examples:
                 Successful operation:
                   value:
@@ -434,14 +434,14 @@ paths:
                           name: Novice Writer
                           metricId: d01dcbcb-d51e-4c12-b054-dc811dcdc623
                           metricValue: 500
-                          achievedAt: '2021-01-01T00:00:00Z'
+                          achievedAt: "2021-01-01T00:00:00Z"
                           badgeUrl: https://example.com/badge1.png
                         - id: 8a07f2d0-9c72-4de1-bf92-9530ae82b4b6
                           trigger: metric
                           name: Intermediate Writer
                           metricId: d01dcbcb-d51e-4c12-b054-dc811dcdc623
                           metricValue: 1000
-                          achievedAt: '2021-01-02T00:00:00Z'
+                          achievedAt: "2021-01-02T00:00:00Z"
                           badgeUrl: https://example.com/badge2.png
                         - id: 2090d038-aa04-4048-ab2e-e2b7bf2d3b9f
                           trigger: metric
@@ -449,24 +449,24 @@ paths:
                           metricId: d01dcbcb-d51e-4c12-b054-dc811dcdc623
                           metricValue: 2000
                           achievedAt: null
-        '401':
-          description: 'Unauthorized'
+        "401":
+          description: "Unauthorized"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
-        '404':
-          description: 'User Not Found'
+                $ref: "#/components/schemas/ErrorBody"
+        "404":
+          description: "User Not Found"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
-        '422':
-          description: 'Unprocessible Entity'
+                $ref: "#/components/schemas/ErrorBody"
+        "422":
+          description: "Unprocessible Entity"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
+                $ref: "#/components/schemas/ErrorBody"
       summary: Get all metrics for a user
       security:
         - ApiKeyAuth: []
@@ -492,12 +492,12 @@ paths:
             type: string
           example: key
       responses:
-        '200':
+        "200":
           description: Successful operation
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/MetricResponse'
+                $ref: "#/components/schemas/MetricResponse"
               examples:
                 Successful operation:
                   value:
@@ -512,13 +512,13 @@ paths:
                         name: Novice Writer
                         metricId: d01dcbcb-d51e-4c12-b054-dc811dcdc623
                         metricValue: 500
-                        achievedAt: '2021-01-01T00:00:00Z'
+                        achievedAt: "2021-01-01T00:00:00Z"
                       - id: 8a07f2d0-9c72-4de1-bf92-9530ae82b4b6
                         trigger: metric
                         name: Intermediate Writer
                         metricId: d01dcbcb-d51e-4c12-b054-dc811dcdc623
                         metricValue: 1000
-                        achievedAt: '2021-01-02T00:00:00Z'
+                        achievedAt: "2021-01-02T00:00:00Z"
                       - id: 2090d038-aa04-4048-ab2e-e2b7bf2d3b9f
                         trigger: metric
                         name: Expert Writer
@@ -526,24 +526,24 @@ paths:
                         metricValue: 2000
                         achievedAt: null
                         badgeUrl: https://example.com/badge.png
-        '401':
-          description: 'Unauthorized'
+        "401":
+          description: "Unauthorized"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
-        '404':
-          description: 'Not Found'
+                $ref: "#/components/schemas/ErrorBody"
+        "404":
+          description: "Not Found"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
-        '422':
-          description: 'Unprocessible Entity'
+                $ref: "#/components/schemas/ErrorBody"
+        "422":
+          description: "Unprocessible Entity"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
+                $ref: "#/components/schemas/ErrorBody"
       summary: Get a single metric for a user
       security:
         - ApiKeyAuth: []
@@ -586,7 +586,7 @@ paths:
           schema:
             type: string
             format: date
-          example: '2024-01-01'
+          example: "2024-01-01"
         - name: endDate
           in: query
           description: The end date for the data range in YYYY-MM-DD format. The endDate must be after the startDate, and the date range must not exceed 400 days.
@@ -594,9 +594,9 @@ paths:
           schema:
             type: string
             format: date
-          example: '2024-01-31'
+          example: "2024-01-31"
       responses:
-        '200':
+        "200":
           description: Successful operation
           content:
             application/json:
@@ -609,7 +609,7 @@ paths:
                       type: string
                       format: date
                       description: The date of the data point. For weekly or monthly aggregations, this is the first date of the period.
-                      example: '2024-01-01'
+                      example: "2024-01-01"
                     total:
                       type: number
                       format: double
@@ -627,33 +627,33 @@ paths:
               examples:
                 Successful operation:
                   value:
-                    - date: '2024-01-01'
+                    - date: "2024-01-01"
                       total: 100
                       change: 100
-                    - date: '2024-01-02'
+                    - date: "2024-01-02"
                       total: 300
                       change: 200
-                    - date: '2024-01-03'
+                    - date: "2024-01-03"
                       total: 600
                       change: 300
-        '401':
-          description: 'Unauthorized'
+        "401":
+          description: "Unauthorized"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
-        '404':
-          description: 'Not Found'
+                $ref: "#/components/schemas/ErrorBody"
+        "404":
+          description: "Not Found"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
-        '422':
-          description: 'Unprocessible Entity'
+                $ref: "#/components/schemas/ErrorBody"
+        "422":
+          description: "Unprocessible Entity"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
+                $ref: "#/components/schemas/ErrorBody"
       summary: Get a summary of metric events over time
       security:
         - ApiKeyAuth: []
@@ -672,14 +672,14 @@ paths:
             type: string
           example: userId
       responses:
-        '200':
+        "200":
           description: Successful operation
           content:
             application/json:
               schema:
                 type: array
                 items:
-                  $ref: '#/components/schemas/CompletedAchievementResponse'
+                  $ref: "#/components/schemas/CompletedAchievementResponse"
               examples:
                 Successful operation:
                   value:
@@ -687,7 +687,7 @@ paths:
                       trigger: api
                       key: completed-onboarding
                       name: Completed Onboarding
-                      achievedAt: '2021-01-01T00:00:00Z'
+                      achievedAt: "2021-01-01T00:00:00Z"
                       badgeUrl: https://example.com/badge2.png
                     - id: d01dcbcb-d51e-4c12-b054-dc811dcdc623
                       trigger: metric
@@ -696,33 +696,33 @@ paths:
                       metricValue: 500
                       metricName: words written
                       name: Novice Writer
-                      achievedAt: '2021-02-01T00:00:00Z'
+                      achievedAt: "2021-02-01T00:00:00Z"
                       badgeUrl: https://example.com/badge1.png
                     - id: d01dcbcb-d51e-4c12-b054-dc811dcdc624
                       trigger: streak
                       key: 3-day-streak
                       streakLength: 3
                       name: 3-Day Streak
-                      achievedAt: '2021-03-01T00:00:00Z'
+                      achievedAt: "2021-03-01T00:00:00Z"
                       badgeUrl: https://example.com/badge2.png
-        '401':
-          description: 'Unauthorized'
+        "401":
+          description: "Unauthorized"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
-        '404':
-          description: 'Not Found'
+                $ref: "#/components/schemas/ErrorBody"
+        "404":
+          description: "Not Found"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
-        '422':
-          description: 'Unprocessible Entity'
+                $ref: "#/components/schemas/ErrorBody"
+        "422":
+          description: "Unprocessible Entity"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
+                $ref: "#/components/schemas/ErrorBody"
       summary: Get a user's completed achievements
       security:
         - ApiKeyAuth: []
@@ -749,62 +749,62 @@ paths:
             The number of past streak periods to include in the streakHistory field of the 
             response.
       responses:
-        '200':
+        "200":
           description: Successful operation
           content:
             application/json:
               schema:
                 type: object
-                $ref: '#/components/schemas/StreakResponse'
+                $ref: "#/components/schemas/StreakResponse"
               examples:
                 Successful operation:
                   value:
                     length: 1
                     frequency: weekly
-                    started: '2025-04-02'
-                    periodStart: '2025-03-31'
-                    periodEnd: '2025-04-05'
-                    expires: '2025-04-12'
+                    started: "2025-04-02"
+                    periodStart: "2025-03-31"
+                    periodEnd: "2025-04-05"
+                    expires: "2025-04-12"
                     streakHistory:
-                      - periodStart: '2025-03-30'
-                        periodEnd: '2025-04-05'
+                      - periodStart: "2025-03-30"
+                        periodEnd: "2025-04-05"
                         length: 1
-                      - periodStart: '2025-04-06'
-                        periodEnd: '2025-04-12'
+                      - periodStart: "2025-04-06"
+                        periodEnd: "2025-04-12"
                         length: 2
-                      - periodStart: '2025-04-13'
-                        periodEnd: '2025-04-19'
+                      - periodStart: "2025-04-13"
+                        periodEnd: "2025-04-19"
                         length: 3
-                      - periodStart: '2025-04-20'
-                        periodEnd: '2025-04-26'
+                      - periodStart: "2025-04-20"
+                        periodEnd: "2025-04-26"
                         length: 0
-                      - periodStart: '2025-04-27'
-                        periodEnd: '2025-05-03'
+                      - periodStart: "2025-04-27"
+                        periodEnd: "2025-05-03"
                         length: 1
-                      - periodStart: '2025-05-04'
-                        periodEnd: '2025-05-10'
+                      - periodStart: "2025-05-04"
+                        periodEnd: "2025-05-10"
                         length: 2
-                      - periodStart: '2025-05-11'
-                        periodEnd: '2025-05-17'
+                      - periodStart: "2025-05-11"
+                        periodEnd: "2025-05-17"
                         length: 3
-        '401':
-          description: 'Unauthorized'
+        "401":
+          description: "Unauthorized"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
-        '404':
-          description: 'Not Found'
+                $ref: "#/components/schemas/ErrorBody"
+        "404":
+          description: "Not Found"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
-        '422':
-          description: 'Unprocessible Entity'
+                $ref: "#/components/schemas/ErrorBody"
+        "422":
+          description: "Unprocessible Entity"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
+                $ref: "#/components/schemas/ErrorBody"
       summary: Get a user's streak status
       security:
         - ApiKeyAuth: []
@@ -831,12 +831,12 @@ paths:
             maximum: 100
           description: The number of recent point awards to return.
       responses:
-        '200':
+        "200":
           description: Successful operation
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/GetUserPointsResponse'
+                $ref: "#/components/schemas/GetUserPointsResponse"
               examples:
                 Successful operation:
                   value:
@@ -850,24 +850,24 @@ paths:
                           points: 10
                           metricName: words written
                           metricThreshold: 1000
-        '401':
-          description: 'Unauthorized'
+        "401":
+          description: "Unauthorized"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
-        '404':
-          description: 'Not Found'
+                $ref: "#/components/schemas/ErrorBody"
+        "404":
+          description: "Not Found"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
-        '422':
-          description: 'Unprocessible Entity'
+                $ref: "#/components/schemas/ErrorBody"
+        "422":
+          description: "Unprocessible Entity"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
+                $ref: "#/components/schemas/ErrorBody"
       summary: Get a user's points data
       security:
         - ApiKeyAuth: []
@@ -903,7 +903,7 @@ paths:
           schema:
             type: string
             format: date
-          example: '2024-01-01'
+          example: "2024-01-01"
         - name: endDate
           in: query
           description: The end date for the data range in YYYY-MM-DD format. The endDate must be after the startDate, and the date range must not exceed 400 days.
@@ -911,9 +911,9 @@ paths:
           schema:
             type: string
             format: date
-          example: '2024-01-31'
+          example: "2024-01-31"
       responses:
-        '200':
+        "200":
           description: Successful operation
           content:
             application/json:
@@ -926,7 +926,7 @@ paths:
                       type: string
                       format: date
                       description: The date of the data point. For weekly or monthly aggregations, this is the first date of the period.
-                      example: '2024-01-01'
+                      example: "2024-01-01"
                     total:
                       type: number
                       format: double
@@ -944,33 +944,33 @@ paths:
               examples:
                 Successful operation:
                   value:
-                    - date: '2024-01-01'
+                    - date: "2024-01-01"
                       total: 100
                       change: 100
-                    - date: '2024-01-02'
+                    - date: "2024-01-02"
                       total: 300
                       change: 200
-                    - date: '2024-01-03'
+                    - date: "2024-01-03"
                       total: 600
                       change: 300
-        '401':
-          description: 'Unauthorized'
+        "401":
+          description: "Unauthorized"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
-        '404':
-          description: 'Not Found'
+                $ref: "#/components/schemas/ErrorBody"
+        "404":
+          description: "Not Found"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
-        '422':
-          description: 'Unprocessible Entity'
+                $ref: "#/components/schemas/ErrorBody"
+        "422":
+          description: "Unprocessible Entity"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
+                $ref: "#/components/schemas/ErrorBody"
       summary: Get a summary of points events over time
       security:
         - ApiKeyAuth: []
@@ -981,12 +981,12 @@ paths:
       tags:
         - Points
       responses:
-        '200':
+        "200":
           description: Successful operation
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/PointsSummaryResponse'
+                $ref: "#/components/schemas/PointsSummaryResponse"
               examples:
                 Successful operation:
                   value:
@@ -1023,18 +1023,18 @@ paths:
                     - from: 901
                       to: 1000
                       users: 0
-        '401':
-          description: 'Unauthorized'
+        "401":
+          description: "Unauthorized"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
-        '404':
-          description: 'Not Found'
+                $ref: "#/components/schemas/ErrorBody"
+        "404":
+          description: "Not Found"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
+                $ref: "#/components/schemas/ErrorBody"
       summary: Get a breakdown of users by points
       security:
         - ApiKeyAuth: []
@@ -1045,14 +1045,14 @@ paths:
       tags:
         - Points
       responses:
-        '200':
+        "200":
           description: Successful operation
           content:
             application/json:
               schema:
                 type: array
                 items:
-                  $ref: '#/components/schemas/PointsTriggerResponse'
+                  $ref: "#/components/schemas/PointsTriggerResponse"
               examples:
                 Successful operation:
                   value:
@@ -1063,29 +1063,29 @@ paths:
                       metricId: 0040fe51-6bce-4b44-b0ad-bddc4e123534
                       metricName: words written
                       metricThreshold: 1000
-                      created: '2021-01-01T00:00:00Z'
-                      updated: '2021-01-01T00:00:00Z'
+                      created: "2021-01-01T00:00:00Z"
+                      updated: "2021-01-01T00:00:00Z"
                     - id: 0040fe51-6bce-4b44-b0ad-bddc4e123536
                       type: streak
                       points: 10
                       status: active
                       streakLengthThreshold: 7
-                      created: '2021-01-01T00:00:00Z'
-                      updated: '2021-01-01T00:00:00Z'
+                      created: "2021-01-01T00:00:00Z"
+                      updated: "2021-01-01T00:00:00Z"
                     - id: 0040fe51-6bce-4b44-b0ad-bddc4e123535
                       type: achievement
                       points: 50
                       status: active
                       achievementId: 0040fe51-6bce-4b44-b0ad-bddc4e123535
                       achievementName: finish onboarding
-                      created: '2021-01-01T00:00:00Z'
-                      updated: '2021-01-01T00:00:00Z'
-        '401':
-          description: 'Unauthorized'
+                      created: "2021-01-01T00:00:00Z"
+                      updated: "2021-01-01T00:00:00Z"
+        "401":
+          description: "Unauthorized"
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ErrorBody'
+                $ref: "#/components/schemas/ErrorBody"
       summary: Get all points triggers
       security:
         - ApiKeyAuth: []
@@ -1114,7 +1114,7 @@ components:
           type: integer
           description: The length of the user's current streak.
         frequency:
-          $ref: '#/components/schemas/StreakFrequency'
+          $ref: "#/components/schemas/StreakFrequency"
           description: The frequency of the streak.
         started:
           type: string
@@ -1140,7 +1140,7 @@ components:
       type: object
       description: An object representing the user's streak after sending a metric event.
       allOf:
-        - $ref: '#/components/schemas/BaseStreakResponse'
+        - $ref: "#/components/schemas/BaseStreakResponse"
         - type: object
           properties:
             extended:
@@ -1151,7 +1151,7 @@ components:
       type: object
       description: An object representing the user's streak.
       allOf:
-        - $ref: '#/components/schemas/BaseStreakResponse'
+        - $ref: "#/components/schemas/BaseStreakResponse"
         - type: object
           properties:
             streakHistory:
@@ -1168,12 +1168,12 @@ components:
                     type: string
                     format: date
                     description: The date this streak period started.
-                    example: '2025-03-31'
+                    example: "2025-03-31"
                   periodEnd:
                     type: string
                     format: date
                     description: The date this streak period ended.
-                    example: '2025-04-05'
+                    example: "2025-04-05"
                   length:
                     type: integer
                     description: The length of the user's streak during this period.
@@ -1192,7 +1192,7 @@ components:
         type:
           type: string
           description: The type of trigger
-          enum: ['metric', 'achievement', 'streak']
+          enum: ["metric", "achievement", "streak"]
         points:
           type: number
           description: The points awarded by this trigger.
@@ -1219,7 +1219,7 @@ components:
           type: number
           description: The points awarded by this trigger
         trigger:
-          $ref: '#/components/schemas/PointsTrigger'
+          $ref: "#/components/schemas/PointsTrigger"
     GetUserPointsResponse:
       title: GetUserPointsResponse
       type: object
@@ -1231,12 +1231,12 @@ components:
           type: array
           description: Array of trigger awards that added points.
           items:
-            $ref: '#/components/schemas/PointsAward'
+            $ref: "#/components/schemas/PointsAward"
     MetricEventPointsResponse:
       title: MetricEventPointsResponse
       type: object
       allOf:
-        - $ref: '#/components/schemas/GetUserPointsResponse'
+        - $ref: "#/components/schemas/GetUserPointsResponse"
         - type: object
           properties:
             added:
@@ -1255,7 +1255,7 @@ components:
           description: The name of this achievement.
         trigger:
           type: string
-          enum: ['metric', 'streak', 'api']
+          enum: ["metric", "streak", "api"]
           description: The trigger of the achievement.
         description:
           type: string
@@ -1283,7 +1283,7 @@ components:
           type: string
           description: The name of the metric associated with this achievement (only applicable if trigger = 'metric')
         currentStreak:
-          $ref: '#/components/schemas/MetricEventStreakResponse'
+          $ref: "#/components/schemas/MetricEventStreakResponse"
           description: >-
             The user's current streak for the metric, if the metric has streaks
             enabled.
@@ -1295,7 +1295,7 @@ components:
       title: CompletedAchievementResponse
       type: object
       allOf:
-        - $ref: '#/components/schemas/AchievementResponse'
+        - $ref: "#/components/schemas/AchievementResponse"
         - type: object
           properties:
             achievedAt:
@@ -1306,7 +1306,7 @@ components:
       title: AchievementWithStatsResponse
       type: object
       allOf:
-        - $ref: '#/components/schemas/AchievementResponse'
+        - $ref: "#/components/schemas/AchievementResponse"
         - type: object
           properties:
             completions:
@@ -1333,7 +1333,7 @@ components:
           description: The name of the metric.
           example: Words written
         status:
-          $ref: '#/components/schemas/MetricStatus'
+          $ref: "#/components/schemas/MetricStatus"
           description: The status of the metric.
         current:
           type: number
@@ -1343,7 +1343,7 @@ components:
         achievements:
           type: array
           items:
-            $ref: '#/components/schemas/CompletedAchievementResponse'
+            $ref: "#/components/schemas/CompletedAchievementResponse"
           description: >-
             A list of the metric's achievements and the user's progress towards
             each.
@@ -1381,7 +1381,7 @@ components:
       type: object
       description: An object with editable user fields.
       allOf:
-        - $ref: '#/components/schemas/UpdatedUser'
+        - $ref: "#/components/schemas/UpdatedUser"
         - type: object
           properties:
             id:
@@ -1395,7 +1395,7 @@ components:
       type: object
       description: A user of your application.
       allOf:
-        - $ref: '#/components/schemas/UpsertedUser'
+        - $ref: "#/components/schemas/UpsertedUser"
         - type: object
           properties:
             control:
@@ -1406,12 +1406,12 @@ components:
               type: string
               format: date-time
               description: The date and time the user was created, in ISO 8601 format.
-              example: '2021-01-01T00:00:00Z'
+              example: "2021-01-01T00:00:00Z"
             updated:
               type: string
               format: date-time
               description: The date and time the user was last updated, in ISO 8601 format.
-              example: '2021-01-01T00:00:00Z'
+              example: "2021-01-01T00:00:00Z"
     ErrorBody:
       title: ErrorBody
       type: object
@@ -1429,7 +1429,7 @@ components:
           description: The unique ID of the completion.
           example: 0040fe51-6bce-4b44-b0ad-bddc4e123534
         achievement:
-          $ref: '#/components/schemas/CompletedAchievementResponse'
+          $ref: "#/components/schemas/CompletedAchievementResponse"
       required:
         - completionId
         - achievement
@@ -1453,15 +1453,15 @@ components:
         achievements:
           type: array
           items:
-            $ref: '#/components/schemas/CompletedAchievementResponse'
+            $ref: "#/components/schemas/CompletedAchievementResponse"
           description: Achievements completed as a result of this event.
         currentStreak:
-          $ref: '#/components/schemas/MetricEventStreakResponse'
+          $ref: "#/components/schemas/MetricEventStreakResponse"
           description: >-
             The user's current streak for the metric, if the metric has streaks
             enabled.
         points:
-          $ref: '#/components/schemas/PointsAward'
+          $ref: "#/components/schemas/PointsAward"
           description: >-
             The points added by this event, and a breakdown of the points
             awards that added points.
@@ -1491,7 +1491,7 @@ components:
         to the greatest number of points a user has, rounded up to the nearest
         power of 10.
       items:
-        $ref: '#/components/schemas/PointsRange'
+        $ref: "#/components/schemas/PointsRange"
     PointsTriggerResponse:
       title: PointsTriggerResponse
       type: object
@@ -1501,14 +1501,14 @@ components:
           description: The unique ID of the trigger.
         type:
           type: string
-          enum: ['metric', 'achievement', 'streak']
+          enum: ["metric", "achievement", "streak"]
           description: The type of trigger.
         points:
           type: number
           description: The points awarded by this trigger.
         status:
           type: string
-          enum: ['active', 'archived']
+          enum: ["active", "archived"]
           description: The status of the trigger.
         achievementId:
           type: string
diff --git a/assets/og.png b/assets/og.png
index 70e42a4..d728382 100644
Binary files a/assets/og.png and b/assets/og.png differ
diff --git a/assets/platform/achievements/displaying_trophy_cabinet.mp4 b/assets/platform/achievements/displaying_trophy_cabinet.mp4
new file mode 100644
index 0000000..8806265
Binary files /dev/null and b/assets/platform/achievements/displaying_trophy_cabinet.mp4 differ
diff --git a/assets/platform/achievements/user_achievements.png b/assets/platform/achievements/user_achievements.png
new file mode 100644
index 0000000..e17609c
Binary files /dev/null and b/assets/platform/achievements/user_achievements.png differ
diff --git a/assets/platform/points/create_trigger.mp4 b/assets/platform/points/create_trigger.mp4
new file mode 100644
index 0000000..9385ff9
Binary files /dev/null and b/assets/platform/points/create_trigger.mp4 differ
diff --git a/assets/platform/points/points_analytics.png b/assets/platform/points/points_analytics.png
new file mode 100644
index 0000000..c53d021
Binary files /dev/null and b/assets/platform/points/points_analytics.png differ
diff --git a/assets/platform/points/points_preview.mp4 b/assets/platform/points/points_preview.mp4
new file mode 100644
index 0000000..9082eaa
Binary files /dev/null and b/assets/platform/points/points_preview.mp4 differ
diff --git a/assets/platform/streaks/displaying_streaks.png b/assets/platform/streaks/displaying_streaks.png
new file mode 100644
index 0000000..49cd5ec
Binary files /dev/null and b/assets/platform/streaks/displaying_streaks.png differ
diff --git a/docs.json b/docs.json
index 1ae8802..7575d68 100644
--- a/docs.json
+++ b/docs.json
@@ -25,7 +25,7 @@
   },
   "seo": {
     "metatags": {
-      "og:description": "Trophy is a developer-friendly platform for building gamified product experiences in any mobile or web app. Add features like achievements and streaks in hours, not months.",
+      "og:description": "Trophy is a developer-friendly platform for building gamified product experiences that retain users in any mobile or web app. Add features like achievements, streaks and points systems and deliver personalized progress report and reactivation emails with no code.",
       "og:image": "/assets/og.png"
     }
   },
@@ -50,6 +50,7 @@
               "platform/users",
               "platform/achievements",
               "platform/streaks",
+              "platform/points",
               "platform/emails"
             ]
           },
@@ -123,6 +124,13 @@
               "api-reference/endpoints/metrics/send-a-metric-change-event"
             ]
           },
+          {
+            "group": "Points",
+            "pages": [
+              "api-reference/endpoints/points/get-points-summary",
+              "api-reference/endpoints/points/get-all-points-triggers"
+            ]
+          },
           {
             "group": "Users",
             "pages": [
@@ -133,7 +141,9 @@
               "api-reference/endpoints/users/get-a-single-metric-for-a-user",
               "api-reference/endpoints/users/get-a-single-metric-event-summary-for-a-user",
               "api-reference/endpoints/users/get-a-users-completed-achievements",
-              "api-reference/endpoints/users/get-a-users-streak"
+              "api-reference/endpoints/users/get-a-users-streak",
+              "api-reference/endpoints/users/get-a-users-points",
+              "api-reference/endpoints/users/get-a-users-points-summary"
             ]
           }
         ]
diff --git a/getting-started/introduction.mdx b/getting-started/introduction.mdx
index d050799..de7e3f7 100644
--- a/getting-started/introduction.mdx
+++ b/getting-started/introduction.mdx
@@ -3,9 +3,9 @@ title: Welcome to Trophy
 description: Trophy documentation for gamification APIs, quickstart guides and tutorials.
 ---
 
-Trophy is a developer-friendly platform and toolkit for building gamified product experiences in any mobile or web app.
+Trophy is a developer-friendly toolkit for building gamified product experiences in any mobile or web app.
 
-It makes adding features like [Achievements](/platform/achievements) and [Streaks](/platform/streaks) simple with just a few lines of code, and can send gamified [Emails](/platform/emails) to increase your retention and engagement.
+It makes building features like [Achievements](/platform/achievements), [Streaks](/platform/streaks) and [Points](/platform/points) simple with just a few lines of code, and can send gamified [Emails](/platform/emails) to increase your retention and engagement.
 
 <CardGroup>
   <Card
@@ -38,7 +38,7 @@ It's been proven by the likes of Duolingo and others to predictably boost retent
 
 But building gamification at scale can be tricky. You have a global userbase, all in different timezones, all with different usage patterns that need to be measured and optimized in realtime. Plus, you want to run experiments to test different approaches and see how they impact retention, but this requires constant code changes, which holds up work on your core product.
 
-Trophy takes away the legwork involved in building features like achievements and streaks and provides reliable, scalable APIs for shipping gamification experiences faster than building in-house. Plus, it provides a web platform to easily configure, measure and experiment with the product experience without constant code changes.
+Trophy takes away the legwork involved in building features like achievements, streaks and points systems and provides reliable, scalable APIs for shipping gamification experiences faster than building in-house. Plus, it provides a web platform to easily configure, measure and experiment with the product experience without constant code changes.
 
 ## Get Support
 
diff --git a/getting-started/quickstart.mdx b/getting-started/quickstart.mdx
index 2f081a9..5d27ad0 100644
--- a/getting-started/quickstart.mdx
+++ b/getting-started/quickstart.mdx
@@ -35,9 +35,9 @@ Here you'll integrate your backend web application with Trophy and start buildin
 
   </Step>
   <Step title="Create your first metric">
-    All gamification features, like [Achievements](/platform/achievements), [Streaks](/platform/streaks) and [Emails](/platform/emails), are driven by user interactions. In Trophy, you use [Metrics](/platform/metrics) to define those interactions and [Events](/platform/events) to track them. 
+    All gamification features are driven by user interactions. In Trophy, you use [Metrics](/platform/metrics) to define and model those interactions and [Events](/platform/events) to track them.
     
-    Here you'll create your first metric to get started. In thr Trophy dashboard, head into the [metrics page](https://app.trophy.so/metrics) and hit the _New Metric_ button:
+    Here you'll create your first metric to get started. In the Trophy dashboard, head into the [metrics page](https://app.trophy.so/metrics) and hit the _New Metric_ button:
 
     <Frame>
       <video
@@ -71,7 +71,7 @@ Here you'll integrate your backend web application with Trophy and start buildin
 
     <MetricChangeRequestBlock />
 
-    By making this call, you're telling Trophy that a specific user made an interaction with your product. As a result, Trophy will process any gamification features that you've configured against the metric automatically.
+    By making this call, you're telling Trophy that a specific user made an interaction with your product. As a result, Trophy will process any gamification features like achievements or streaks that you've configured against the metric automatically.
 
   </Step>
   <Step title="Continue building your gamification experience">
@@ -84,14 +84,17 @@ Here you'll integrate your backend web application with Trophy and start buildin
         Reward users for continued progress or taking specific actions.
       </Card>
       <Card title="Streaks" icon="flame" href="/platform/streaks">
-        Motivate users to continue using your platform over time.
+        Motivate users to build regular usage habits.
+      </Card>
+      <Card title="Points" icon="sparkle" href="/platform/points">
+        Build sophisticated points systems to reward and retain users.
       </Card>
       <Card title="Emails" icon="mail" href="/platform/emails">
-        Encourage and congratulate users to keep them coming back.
+        Deliver personalized lifecyle emails to users at the perfect moment.
       </Card>
     </CardGroup>
 
-    Or, explore our [ready-made APIs](/api-reference/introduction) that support building any in-app gamification UI you want.
+    Or, explore our [purpose-built APIs](/api-reference/introduction) that support building any in-app gamification UI you want.
 
   </Step>
 </Steps>
diff --git a/guides/example-apps/example-study-platform.mdx b/guides/example-apps/example-study-platform.mdx
index 887f1a3..666fa78 100644
--- a/guides/example-apps/example-study-platform.mdx
+++ b/guides/example-apps/example-study-platform.mdx
@@ -43,9 +43,9 @@ The tech stack for this example study platform is as follows:
 
 The example app uses Trophy to demonstrate how easy it is to build gamification experiences. Here's a breakdown of the gamification features used:
 
-### Multi-stage Acheivements
+### Achievements
 
-The example app features multi-stage [achievements(/platform/achievements)] with the following milestones:
+The example app features [achievements(/platform/achievements)] with the following milestones:
 
 - 10 flashcards viewed
 - 50 flashcards viewed
diff --git a/guides/tutorials/how-to-build-a-gamified-study-platform.mdx b/guides/tutorials/how-to-build-a-gamified-study-platform.mdx
index 7d0c99e..90583db 100644
--- a/guides/tutorials/how-to-build-a-gamified-study-platform.mdx
+++ b/guides/tutorials/how-to-build-a-gamified-study-platform.mdx
@@ -993,7 +993,7 @@ import Image from "next/image";
 interface ToastProps {
   id: string | number;
   title: string;
-  description: string;
+  description?: string;
   image?: {
     src: string;
     alt: string;
@@ -1040,7 +1040,9 @@ export function Toast(props: ToastProps) {
       <div className="flex flex-1 items-center">
         <div className="w-full">
           <p className="text-sm font-medium text-gray-900">{title}</p>
-          <p className="mt-1 text-sm text-gray-500">{description}</p>
+          {description && (
+            <p className="mt-1 text-sm text-gray-500">{description}</p>
+          )}
         </div>
       </div>
     </div>
@@ -1086,7 +1088,7 @@ export default nextConfig;
 
 And finally, we update our `<Flashcards />` component to read the response from Trophy and display toasts for any unlocked achievements:
 
-```tsx src/app/flashcards.tsx [expandable] {15,33,38-61}
+```tsx src/app/flashcards.tsx [expandable] {15,33,38-56}
 "use client";
 
 import {
@@ -1130,23 +1132,17 @@ export default function Flashcards({ flashcards }: Props) {
         return;
       }
 
-      // Show toast if the user has unlocked any new achievements
-      if (response.achievements?.length) {
-        response.achievements.forEach((metricAchievements) => {
-          if (metricAchievements.completed?.length) {
-            metricAchievements.completed.forEach((achievement) => {
-              toast({
-                title: achievement.name as string,
-                description: `Congratulations! You've viewed ${achievement.metricValue} flashcards!`,
-                image: {
-                  src: achievement.badgeUrl as string,
-                  alt: achievement.name as string,
-                },
-              });
-            });
-          }
+      // Show toasts if the user has unlocked any new achievements
+      response.achievements.forEach((achievement) => {
+        toast({
+          title: achievement.name as string,
+          description: achievement.description,
+          image: {
+            src: achievement.badgeUrl as string,
+            alt: achievement.name as string,
+          },
         });
-      }
+      });
     });
   }, [api]);
 
@@ -1193,7 +1189,7 @@ We'll use the same methods to show similar toasts when a user extendeds their st
 
 All we need to do is read the `currentStreak.extended` property from Trophy and handle showing another toast with a new `if` statement:
 
-```tsx src/app/flashcards.tsx [expandable] {62-69}
+```tsx src/app/flashcards.tsx [expandable] {56-63}
 "use client";
 
 import {
@@ -1237,23 +1233,17 @@ export default function Flashcards({ flashcards }: Props) {
         return;
       }
 
-      // Show toast if the user has unlocked any new achievements
-      if (response.achievements?.length) {
-        response.achievements.forEach((metricAchievements) => {
-          if (metricAchievements.completed?.length) {
-            metricAchievements.completed.forEach((achievement) => {
-              toast({
-                title: achievement.name as string,
-                description: `Congratulations! You've viewed ${achievement.metricValue} flashcards!`,
-                image: {
-                  src: achievement.badgeUrl as string,
-                  alt: achievement.name as string,
-                },
-              });
-            });
-          }
+      // Show toasts if the user has unlocked any new achievements
+      response.achievements.forEach((achievement) => {
+        toast({
+          title: achievement.name as string,
+          description: achievement.description,
+          image: {
+            src: achievement.badgeUrl as string,
+            alt: achievement.name as string,
+          },
         });
-      }
+      });
 
       // Show toast if user has extended their streak
       if (response.currentStreak?.extended) {
@@ -1310,7 +1300,7 @@ For this we'll make use of the [HTML5 Audio API](https://developer.mozilla.org/e
 
 To load the sound files into our application, we'll create a ref for each one, then we simply call the `play()` method on each when we want to actually play the sound:
 
-```tsx src/app/flashcards.tsx [expandable] {25-31,53-57,77-81}
+```tsx src/app/flashcards.tsx [expandable] {25-31,53-57,73-77}
 "use client";
 
 import {
@@ -1370,19 +1360,15 @@ export default function Flashcards({ flashcards }: Props) {
         }
 
         // Show toasts if the user has unlocked any new achievements
-        response.achievements.forEach((metricAchievements) => {
-          if (metricAchievements.completed?.length) {
-            metricAchievements.completed.forEach((achievement) => {
-              toast({
-                title: achievement.name as string,
-                description: `Congratulations! You've viewed ${achievement.metricValue} flashcards!`,
-                image: {
-                  src: achievement.badgeUrl as string,
-                  alt: achievement.name as string,
-                },
-              });
-            });
-          }
+        response.achievements.forEach((achievement) => {
+          toast({
+            title: achievement.name as string,
+            description: achievement.description,
+            image: {
+              src: achievement.badgeUrl as string,
+              alt: achievement.name as string,
+            },
+          });
         });
       }
 
diff --git a/platform/achievements.mdx b/platform/achievements.mdx
index 3b5b6fc..503ea97 100644
--- a/platform/achievements.mdx
+++ b/platform/achievements.mdx
@@ -1,17 +1,25 @@
 ---
 title: Achievements
 description: Learn how to use Achievements in a gamified product experience with Trophy.
-"og:description": Use multi-stage, one-off and streak achievements to rewards users for continued progress and to encourage them to discover new parts of your app.
+"og:description": Use metric, standalone and streak achievements to rewards users for continued progress and to encourage them to discover new parts of your app.
 icon: trophy
 ---
 
 import MetricChangeResponseBlock from "/snippets/metric-change-response-block.mdx";
+import AllAchievementsResponseBlock from "/snippets/all-achievements-response-block.mdx";
 
 ## What Are Achievements?
 
 Achievements are rewards that users can unlock as they use your platform. They can be used to reward users for making continued progress along core user journeys, or to motivate users to explore more nascent features.
 
-No matter the type of achievement, they work best when designed to incentivize users to take actions that are likely to lead to increased retention. So before jumping in, have a think about what those actions might be in your context.
+Achievements work best when designed to incentivize users to take actions that
+are likely to lead to increased retention.
+
+<Tip>
+  Use Trophy's [metric analytics](/platform/metrics#metric-analytics) to compare
+  the retention of each user interaction, then configure achievements around
+  these interactions to maximize retention impact.
+</Tip>
 
 Here we'll have a look of the types of achievements you can build with Trophy, the different ways to use them, and how to integrate them into your platform.
 
@@ -144,7 +152,9 @@ This will return back a response that contains details of the achievement that w
   "completionId": "0040fe51-6bce-4b44-b0ad-bddc4e123534",
   "achievement": {
     "id": "5100fe51-6bce-6j44-b0hs-bddc4e123682",
+    "trigger": "api",
     "name": "Finish onboarding",
+    "description": "Complete the onboarding process.",
     "badgeUrl": "https://example.com/badge.png",
     "key": "finish-onboarding",
     "achievedAt": "2021-01-01T00:00:00Z"
@@ -167,12 +177,14 @@ This will return back a response that contains details of the achievement that w
 
 A badge can be uploaded and assigned to any achievement in Trophy. Trophy will host the image for you and return the URL back to you in relevant API responses to be used as the `src` property in `<img>` tags.
 
-```json Response {6}
+```json Response {8}
 {
   "completionId": "0040fe51-6bce-4b44-b0ad-bddc4e123534",
   "achievement": {
     "id": "5100fe51-6bce-6j44-b0hs-bddc4e123682",
+    "trigger": "api",
     "name": "Finish onboarding",
+    "description": "Complete the onboarding process.",
     "badgeUrl": "https://example.com/badge.png",
     "key": "finish-onboarding",
     "achievedAt": "2021-01-01T00:00:00Z"
@@ -180,14 +192,56 @@ A badge can be uploaded and assigned to any achievement in Trophy. Trophy will h
 }
 ```
 
-## Achievement Analytics
+## Displaying Achievements
+
+Trophy has a number of APIs that support displaying achievements within your applications. Here we'll look at the different ways to use them and the types of UI's you can build.
+
+<Tip>
+  Take a look at our [examples center](https://examples.trophy.so) for live
+  demos of APIs in practice.
+</Tip>
+
+### All Achievements
+
+To display a high-level overview of all achievements users can complete, use the [all achievements endpoint](/api-reference/endpoints/achievements/all-achievements). Use this data to build UI that gives users an idea of the progression pathways within your application.
+
+<Frame>
+  <video
+    autoPlay
+    muted
+    loop
+    playsInline
+    className="w-full aspect-video"
+    src="../assets/platform/achievements/displaying_trophy_cabinet.mp4"
+  ></video>
+</Frame>
+
+The all achievements endpoint returns a list of all achievements within your Trophy account along with details of 'rarity' (the percentage of users who have completed each achievement) as follows:
+
+<AllAchievementsResponseBlock />
+
+### User Achievements
 
-If you have multi-stage acheivements set up for any of your [Metrics](/platform/metrics), then the metric analytics page displays a chart that shows you the current progress of all Users as follows:
+If instead you're building user-specific UI elements, then use the [user achievements endpoint](/api-reference/endpoints/users/get-a-users-completed-achievements) to get only the achievements a specific user has completed.
+
+Use this data to display achievements against a user's profile for example.
 
 <Frame>
   <img
     height="200"
     noZoom
+    src="../assets/platform/achievements/user_achievements.png"
+  />
+</Frame>
+
+## Achievement Analytics
+
+If you have achievements set up for any of your [Metrics](/platform/metrics), then the metric analytics page displays a chart that shows you the current progress of all Users as follows:
+
+<Frame>
+  <img
+    width="50%"
+    noZoom
     src="../assets/platform/metrics/achievement_completions.png"
   />
 </Frame>
@@ -207,8 +261,9 @@ If you have multi-stage acheivements set up for any of your [Metrics](/platform/
     <Accordion title="What achievements should I create?">
     Achievements, like all gamification, offer the best retention when tightly aligned to the user's core reason for using your platform.
 
-    Only you'll know what's best here.
-    </Accordion>
+    Use Trophy's [metric analytics](/platform/metrics#metric-analytics) to compare the retention of each user interaction, then configure achievements around these interactions to maximize retention impact.
+
+</Accordion>
 
 </AccordionGroup>
 
diff --git a/platform/events.mdx b/platform/events.mdx
index 75746c6..cb3cf0d 100644
--- a/platform/events.mdx
+++ b/platform/events.mdx
@@ -1,7 +1,7 @@
 ---
 title: Events
-description: Events are data objects that record continual user interactions against metrics in Trophy.
-"og:description": Events are data objects that record continual user interactions against metrics in Trophy.
+description: Events are data objects that represent individual user interactions against metrics in Trophy.
+"og:description": Events are data objects that represent individual user interactions against metrics in Trophy.
 icon: radio
 ---
 
@@ -10,7 +10,7 @@ import MetricChangeResponseBlock from "/snippets/metric-change-response-block.md
 
 ## What are Events?
 
-Events store information about individual user interactions that are tracked against [Metrics](/platform/metrics) in Trophy. One event corresponds to a single interaction made by a single user.
+Events represent individual user interactions against [Metrics](/platform/metrics) in Trophy. One event corresponds to a single interaction made by a single user.
 
 When you [integrate metrics](#tracking-metric-events) into your platform, you're setting up your platform to continuously stream events to your Trophy metrics for each user interaction. These interactions then drive all the gamification features you set up around these metrics.
 
@@ -18,7 +18,7 @@ When you [integrate metrics](#tracking-metric-events) into your platform, you're
 
 ### Metric-backed
 
-Each event increases or decreases a specific metric that you've configured in Trophy for a specific user.
+Each event increases or decreases the total value of a specific metric that you've configured in Trophy for a specific user.
 
 ### Value
 
@@ -34,17 +34,25 @@ Here's an example where a fictional book-writing platform is using a metric to t
 
 <MetricChangeRequestBlock />
 
-Any [Achievements](/platform/achievements), [Streaks](/platform/streaks) or other gamification features that have been set up against this metric will be automatically processed, and the response will contain any updates to the users progress that are a direct result of the event occurring:
+Any [Achievements](/platform/achievements), [Streaks](/platform/streaks) or [Points](/platform/points) that have been set up against this metric will be automatically processed, and the response will contain any updates to the users progress that are a direct result of the event occurring:
 
 <MetricChangeResponseBlock />
 
-With custom code, this response data can then be used to drive any in-app experience you wish including:
+In this example the response includes the following:
+
+- Newly unlocked achievements as a result of the event
+- The users latest streak as result of the event
+- Any points awards as a result of the event
+
+With a little bit of custom code, this response data can be used to drive any in-app experience you wish including:
 
 - Triggering in-app notifications
 - Sound effects
 - Animations
 
-Watch Charlie integrate metric tracking into a simple NextJS application using the NodeJS SDK:
+Additionally, any [Emails](/platform/emails) configured to track the metric will be scheduled automatically by Trophy.
+
+Watch Charlie integrate metric tracking into a simple NextJS application using the Trophy [NodeJS SDK](/api-reference/client-libraries):
 
 <Frame>
   <iframe
diff --git a/platform/metrics.mdx b/platform/metrics.mdx
index 7544b44..cf429c9 100644
--- a/platform/metrics.mdx
+++ b/platform/metrics.mdx
@@ -7,18 +7,20 @@ icon: box
 
 ## What are Metrics?
 
-All gamification features are centered around user interactions. At Trophy, we use the term **Metrics** to refer to the data objects that reflect those interactions within the platform.
+All gamification features are centered around user interactions. At Trophy, we use the term **Metrics** to refer to the data objects that model those interactions within your web or mobile app.
 
 Metrics are un-opinionated, meaning they can be used to model absolutely any user interaction you can think of. Examples could include:
 
-- Followers on social media platforms
+- Followers, likes or posts
 - Tasks completed
 - Miles ran
 - Lessons completed
+- Words written
+- ...
 
 Metrics are the building blocks of the infrastructure that powers Trophy's gamification features. Each user interaction that relates to a metric is stored as an [Event](/platform/events).
 
-Events are stored and processed in chronological order. At any particular point in time, the combined state of all of a user's events reflects their overall progress on your platform.
+Events are stored and processed in chronological order. At any particular point in time, the combined state of a user's event history reflects their overall progress on your platform.
 
 ## Key Attributes
 
@@ -50,14 +52,14 @@ To create a Metric, head over to the [Metrics](https://app.trophy.so/metrics) pa
   <Step title="Enter a name">
     Choose a name for the metric.
   </Step>
-
-  <Step title="Choose an emoji">
-    Choose an emoji that will be made available for display in emails and will represent the metric in other areas of Trophy.
-  </Step>
   
   <Step title="Hit save">
     Save the new metric.
   </Step>
+
+   <Step title="Configure settings">
+    Configure additional settigns like metric units or currency if applicable on the metric configure page.
+  </Step>
 </Steps>
 
 ## Metric Analytics
@@ -68,7 +70,6 @@ Trophy has a built-in analytics dashboard for each metric you create. It shows y
 - The number of users actively making progress against the metric
 - The metric's [Trophy Retention Impact Score](#trophy-retention-impact-score)
 - The metric's [Achievment Completion Chart](#achievment-completion-chart)
-- The metric's [Streak Progress Analytics](#streak-progress-analytics)
 
 <Frame>
   <img
@@ -114,24 +115,6 @@ The achievement completion chart shows the current state of the userbase in term
   />
 </Frame>
 
-### Streak Progress Analytics
-
-The Streak analytics charts show important information about streaks if they are enabled for this metric, including:
-
-- The average length of streaks
-- The number of active streaks
-- The streak retention impact (reflects the increase in retention of users who are on a streak compared to those who aren't)
-
-[Learn more about streaks](/platform/streaks).
-
-<Frame>
-  <img
-    height="200"
-    noZoom
-    src="../assets/platform/metrics/streak_analytics.png"
-  />
-</Frame>
-
 ## Frequently Asked Questions
 
 <AccordionGroup>
diff --git a/platform/overview.mdx b/platform/overview.mdx
index f3724f8..a3ff434 100644
--- a/platform/overview.mdx
+++ b/platform/overview.mdx
@@ -20,10 +20,13 @@ Trophy is built around a set of key concepts that all gamification experiences h
     Reward users for continued progress or taking specific actions.
   </Card>
   <Card title="Streaks" icon="flame" href="/platform/streaks">
-    Motivate users to continue using your platform over time.
+    Motivate users to build regular usage habits.
+  </Card>
+  <Card title="Points" icon="sparkle" href="/platform/points">
+    Build sophisticated points systems to reward and retain users.
   </Card>
   <Card title="Emails" icon="mail" href="/platform/emails">
-    Encourage and congratulate users to keep them coming back.
+    Deliver personalized lifecyle emails to users at the perfect moment.
   </Card>
 </CardGroup>
 
diff --git a/platform/points.mdx b/platform/points.mdx
new file mode 100644
index 0000000..0ec8ddf
--- /dev/null
+++ b/platform/points.mdx
@@ -0,0 +1,124 @@
+---
+title: Points
+description: Learn how to build points-based systems using Trophy
+"og:description": Use points systems to reward users for in-app actions.
+icon: sparkle
+---
+
+import MetricChangeResponseBlock from "/snippets/metric-change-response-block.mdx";
+
+## What is a Points system?
+
+Points systems are used to reward users for taking actions in your product. When rewards are closely aligned with user incentives, they can be a powerful retention feature.
+
+<Tip>
+  Use Trophy's [metric analytics](/platform/metrics#metric-analytics) to compare
+  the retention of each user interaction, then configure points around these
+  interactions to maximize retention impact.
+</Tip>
+
+Use Trophy to create sophisticated points systems driven by real user interactions with no custom code.
+
+## Creating Triggers
+
+Points can be awarded as a result of user interactions tracked by Trophy including:
+
+- Awarding points as users increment [Metrics](/platform/metrics) e.g. "earn 10 points for every mile ran".
+- Awarding points for reaching [Streak](/platform/streaks) milestones e.g. reaching 7-day, 14-day and 30-day streaks.
+- Awarding points for unlocking [Achievements](/platform/achievements).
+
+<Frame>
+  <video
+    autoPlay
+    muted
+    loop
+    playsInline
+    className="w-full aspect-video"
+    src="../assets/platform/points/create_trigger.mp4"
+  ></video>
+</Frame>
+
+To create a new points trigger, head to the [points](https://app.trophy.so/points/configure/new) page in the Trophy dashboard and follow the steps below:
+
+<Tip>
+  All new points triggers are created as 'Inactive' to allow testing and
+  balancing before deployment to production.
+</Tip>
+
+<Steps>
+<Step title="Choose a trigger type">
+  Choose how you want points to be awarded.
+  
+- Choosing **Metric** will mean points will be automatically awarded to users incrementally as they increase their metric total for a particular metric.
+
+- Choosing **Streak** will mean points will be automatically awarded to users eaech time their streak is increased by a specific length.
+
+- Choosing **Achievement** will mean points will be automatically awarded to users when they complete a specific achievement.
+
+</Step>
+
+<Step title="Set up trigger">
+  Once you've chosen the points trigger type, you need to set up the trigger settings.
+
+- If you chose the **Metric** trigger, you'll need to choose the metric, the threshold amount at which to award points, and number of points to award each time the user's total metric value increases by the threshold amount.
+
+- If you chose the **Streak** trigger, you'll need to set the streak length that should award points and the number of points to award to user's each time their streak is increased by this length.
+
+- If you chose the **Achievement** trigger, you'll need to choose the achievement that should award points when completed and the number of points to award.
+
+</Step>
+
+<Step title="Hit save">
+  Save the new points trigger.
+</Step>
+</Steps>
+
+## Balancing Points
+
+Running an effective points system requires finding the optimal pace at which users earn points. Too fast, and users will get points fatigue, rendering them useless. Too slow, and users may get bored and churn.
+
+Trophy's preview tool can model different scenarios to help you determine how frequently users should earn points.
+
+<Frame>
+  <video
+    autoPlay
+    muted
+    loop
+    playsInline
+    className="w-full aspect-video"
+    src="../assets/platform/points/points_preview.mp4"
+  ></video>
+</Frame>
+
+## Displaying Points
+
+There are a few ways to use Trophy to fetch and display points in your app.
+
+Firstly, any points awarded to users are returned in the response when sending metric change events using the (metric change event API](/api-reference/endpoints/metrics/send-a-metric-change-event).
+
+The response includes the user's total points, how many points were awarded as a result of the event, and the details of the specific triggers that fired.
+
+<MetricChangeResponseBlock />
+
+Additionally there are a number of APIs that can be used to fetch and display points data in the API. Check the full [API reference](/api-reference/introduction) for details.
+
+## Points Analytics
+
+Trophy has built-in analytics to track points awards across your users in real time including:
+
+- Total points earned by all users over time
+- Most points earned by a single user
+- Average points earned in the first 14 days (useful for understanding new user retention patterns and the impact of points)
+- A breakdown on the most commonly awarded points triggers
+
+<Frame>
+  <img
+    height="200"
+    noZoom
+    src="../assets/platform/points/points_analytics.png"
+  />
+</Frame>
+
+## Get Support
+
+Want to get in touch with the Trophy team? Reach out to us via [email](mailto:support@trophy.so). We're here to help!
diff --git a/platform/streaks.mdx b/platform/streaks.mdx
index c8467e9..eed3b86 100644
--- a/platform/streaks.mdx
+++ b/platform/streaks.mdx
@@ -11,7 +11,13 @@ import MetricChangeResponseBlock from "/snippets/metric-change-response-block.md
 
 A streak is a period of consecutive days, weeks or months that a user has performed a key action on your platform. Streaks have been shown to meaningfully increase retention, particularly when the user action being tracked aligns with the core value of your product.
 
-Streaks are **global** to your platform, meaning that each user has a single streak that can be updated by incrementing [Metrics](/platform/metrics). You can decide which metrics should update a user's streak when incremented.
+<Tip>
+  Use Trophy's [metric analytics](/platform/metrics#metric-analytics) to compare
+  the retention of each user interaction, then configure streaks around these
+  interactions to maximize retention impact.
+</Tip>
+
+Streaks are **global** to your platform, meaning that each user has a single streak across all interactions. You can decide which [Metrics](/platform/metrics) should contribute a user's streak on the [streaks configure](https://staging-app.trophy.so/streaks/configure) page.
 
 ## Key Attributes
 
@@ -19,13 +25,13 @@ Streaks are **global** to your platform, meaning that each user has a single str
 
 Streaks can be configured to be daily, weekly or monthly. This means that a user must increment a metric at least once every calendar day, week or month to maintain their streak.
 
-Trophy will automatically compute streak data for all streak frequencies, which means you can change the frequency at any time while maintaining users' streaks. Just note that changing the frequency may be confusing for users, and may lead to lost streaks (e.g. if you change from weekly to daily).
+Trophy will automatically compute streak data for all streak frequencies, which means you can change the frequency at any time while maintaining users' streaks. Just note that changing the frequency may be confusing for users, so best to communicate any changes ahead of time.
 
 ### Streak Metrics
 
-You can choose which metrics should update a user's streak when incremented.
+You can choose which metrics should contribute to a user's streak
 
-For example, if your platform is a language learning app, you might want to track a user's streak based on the number of lessons completed, while also tracking a metric for the number of words learned that doesn't affect the streak. In this case, you would set the lessons completed metric to update the user's streak.
+For example, if your platform is a language learning app, you might want to track a user's streak based on the number of lessons completed, while also tracking a metric for the number of words learned that doesn't affect streaks. In this case, you would configure the lessons completed metric to contribute to streak's but not the words learned metric.
 
 <Callout intent="info">
   Regardless of whether streaks are enabled or disabled, Trophy will still
@@ -45,9 +51,12 @@ Trophy automatically calculates streaks for all users when users
 
 ## Displaying Streaks
 
-If you have [Emails](/platform/emails) configured, Trophy will automatically include streak information in the emails sent to users, as a means of encouraging users to keep using your product.
+Trophy exposes streak data in two ways, which can be used to build UI elements within your applications and display streaks to users.
 
-However, Trophy also returns streak data back to you to display in your app however you like. Trophy exposes streak data in two ways:
+<Tip>
+  Take a look at our [examples center](https://examples.trophy.so) for live
+  demos of APIs in practice.
+</Tip>
 
 ### Metric Event Response
 
@@ -56,6 +65,11 @@ streak (if streaks are enabled).
 
 <MetricChangeResponseBlock />
 
+This can be used to transactionally trigger UI/UX elements including:
+
+- Showing in-app pop-ups
+- Playing sound effects
+
 ### User Streaks API
 
 At any time, you can query the [User Streaks API](/api-reference/endpoints/users/get-a-users-streak).
@@ -110,6 +124,16 @@ This will return the current streak for a single user, along with their recent s
 }
 ```
 
+Use this data to display a user's streak history within your application.
+
+<Frame>
+  <img
+    height="200"
+    noZoom
+    src="../assets/platform/streaks/displaying_streaks.png"
+  />
+</Frame>
+
 ## Get Support
 
 Want to get in touch with the Trophy team? Reach out to us via [email](mailto:support@trophy.so). We're here to help!
diff --git a/platform/users.mdx b/platform/users.mdx
index a715348..4735a38 100644
--- a/platform/users.mdx
+++ b/platform/users.mdx
@@ -1,6 +1,6 @@
 ---
 title: Users
-description: Learn how to track interactions across your whole userbase using Trophy. Track any user interaction and trigger automated gamification flows in just a few lines of code.
+description: Learn how to track interactions across your userbase using Trophy.
 "og:description": Users are the people that use your platform. Learn how to tell Trophy about them.
 icon: users
 ---
@@ -16,7 +16,10 @@ Users in Trophy have a number of attributes, some are required while others are
 
 Every user you tell Trophy about must have an `id`, this is what identifies them as a unique person.
 
-To make things simple, Trophy lets you use your own id that you already have in your database instead of needing to manage another one just for Trophy.
+<Tip>
+  To make things simple, Trophy lets you use your own `id` that you already have
+  in your database instead of needing to manage another one just for Trophy.
+</Tip>
 
 <ParamField path="id" type="string" required={true}>
   This is the ID of the user in **your** database.
@@ -117,8 +120,10 @@ In this case, you can tell Trophy about new users using the [User Identification
 <IdentifyUserRequestBlock />
 
 <Tip>
-  Even if you use explicit identification, the metrics API will always create
-  new and update existing users to ensure your whole userbase is always tracked.
+  Even if you use explicit identification, the [metric tracking
+  API](/api-reference/endpoints/metrics/send-a-metric-change-event) will always
+  create new and update existing users to ensure your user data is always in
+  sync.
 </Tip>
 
 ## Keeping Users Up To Date
@@ -133,7 +138,7 @@ To fetch the details of a user that you've already identified with Trophy, use t
 
 This will return the full details of the user along with the `control` attribute that you can use to conditionally enroll users in any gamification features. Learn more about [Experimentation](/experimentation/overview).
 
-```json Response
+```json Response {3}
 {
   "id": "user-id",
   "control": false,
diff --git a/snippets/all-achievements-response-block.mdx b/snippets/all-achievements-response-block.mdx
new file mode 100644
index 0000000..bdb69fd
--- /dev/null
+++ b/snippets/all-achievements-response-block.mdx
@@ -0,0 +1,36 @@
+```json Response [expandable]
+[
+  {
+    "id": "5100fe51-6bce-6j44-b0hs-bddc4e123682",
+    "trigger": "api",
+    "name": "Finish onboarding",
+    "description": "Complete the onboarding process.",
+    "badgeUrl": "https://example.com/badge.png",
+    "key": "finish-onboarding",
+    "completions": 8,
+    "completedPercentage": 80
+  },
+  {
+    "id": "5100fe51-6bce-6j44-b0hs-bddc4e123683",
+    "trigger": "metric",
+    "name": "500 words written",
+    "description": "Write 500 words in the app.",
+    "badgeUrl": "https://example.com/badge.png",
+    "metricId": "5100fe51-6bce-6j44-b0hs-bddc4e123683",
+    "metricName": "words written",
+    "metricValue": 500,
+    "completions": 6,
+    "completedPercentage": 60
+  },
+  {
+    "id": "5100fe51-6bce-6j44-b0hs-bddc4e123684",
+    "trigger": "streak",
+    "name": "10 days of exercise",
+    "description": "Exercise at least once a day for 10 days in a row.",
+    "badgeUrl": "https://example.com/badge.png",
+    "streakLength": 10,
+    "completions": 2,
+    "completedPercentage": 20
+  }
+]
+```
diff --git a/snippets/metric-change-response-block.mdx b/snippets/metric-change-response-block.mdx
index 219f945..757eaa0 100644
--- a/snippets/metric-change-response-block.mdx
+++ b/snippets/metric-change-response-block.mdx
@@ -8,10 +8,11 @@
       "id": "5100fe51-6bce-6j44-b0hs-bddc4e123682",
       "trigger": "metric",
       "metricId": "5100fe51-6bce-6j44-b0hs-bddc4e123682",
-      "metricName": "words written",
+      "metricName": "Words Written",
       "metricValue": 500,
       "name": "500 words written",
-      "achievedAt": "2020-01-01T00:00:00Z"
+      "description": "Write 500 words in the app.",
+      "achievedAt": "2025-04-02T00:00:00Z"
     }
   ],
   "currentStreak": {
@@ -21,6 +22,23 @@
     "periodStart": "2025-03-31",
     "periodEnd": "2025-04-05",
     "expires": "2025-04-12"
+  },
+  "points": {
+    "total": 5,
+    "added": 5,
+    "awards": [
+      {
+        "id": "2414266f-9d02-4820-866b-47b03e87b702",
+        "awarded": 5,
+        "trigger": {
+          "id": "8126234a-2d8c-498d-b919-2459378accad",
+          "type": "metric",
+          "metricName": "Words Written",
+          "metricThreshold": 10,
+          "points": 5
+        }
+      }
+    ]
   }
 }
 ```