chore: Changelog dec 15 / fix API error doc links (#691)

* Add changelog

* Fix error URL in API

* Add a call out

* move callout

apps/api/src/pkg/errors/http.ts

@@ -26,7 +26,7 @@ export function errorSchemaFactory(code: z.ZodEnum<any>) {
       }),
       docs: z.string().openapi({
         description: "A link to our documentation with more details about this error code",
-        example: `https://docs.unkey.dev/api-reference/errors/code/${code._def.values.at(0)}`,
+        example: `https://unkey.dev/docs/api-reference/errors/code/${code._def.values.at(0)}`,
       }),
       message: z
         .string()
@@ -47,7 +47,7 @@ export const ErrorSchema = z.object({
     }),
     docs: z.string().openapi({
       description: "A link to our documentation with more details about this error code",
-      example: "https://docs.unkey.dev/api-reference/errors/code/BAD_REQUEST",
+      example: "https://unkey.dev/docs/api-reference/errors/code/BAD_REQUEST",
     }),
     message: z.string().openapi({ description: "A human readable explanation of what went wrong" }),
     requestId: z.string().openapi({
@@ -110,7 +110,7 @@ export function handleZodError(
       {
         error: {
           code: "BAD_REQUEST",
-          docs: "https://docs.unkey.dev/api-reference/errors/code/BAD_REQUEST",
+          docs: "https://unkey.dev/docs/api-reference/errors/code/BAD_REQUEST",
           message: generateErrorMessage(result.error.issues, {
             maxErrors: 1,
             delimiter: {
@@ -145,7 +145,7 @@ export function handleError(err: Error, c: Context): Response {
       {
         error: {
           code: err.code,
-          docs: `https://docs.unkey.dev/api-reference/errors/code/${err.code}`,
+          docs: `https://unkey.dev/docs/api-reference/errors/code/${err.code}`,
           message: err.message,
           requestId: c.get("requestId"),
         },
@@ -159,7 +159,7 @@ export function handleError(err: Error, c: Context): Response {
     {
       error: {
         code: "INTERNAL_SERVER_ERROR",
-        docs: "https://docs.unkey.dev/api-reference/errors/code/INTERNAL_SERVER_ERROR",
+        docs: "https://unkey.dev/docs/api-reference/errors/code/INTERNAL_SERVER_ERROR",
         message: "something unexpected happened",
         requestId: c.get("requestId"),
       },
@@ -173,7 +173,7 @@ export function errorResponse(c: Context, code: z.infer<typeof ErrorCode>, messa
     {
       error: {
         code: code,
-        docs: `https://docs.unkey.dev/api-reference/errors/code/${code}`,
+        docs: `https://unkey.dev/docs/api-reference/errors/code/${code}`,
         message,
         requestId: c.get("requestId"),
       },

apps/web/content/changelog/2023-12-15.mdx

@@ -0,0 +1,66 @@
+---
+  title: Unkey is faster, we have improved analytics, and a new billing page
+  date: 2023-12-15,
+  description: We've been working on improvements to the Unkey dashboard. We also moved the Unkey API to Cloudlfare workers.
+---
+
+Welcome to the Unkey changelog for Decemeber 15th, 2023. The last two weeks have been busy with some core changes to the Unkey product.
+
+### Improved Analytics 
+
+Analytics are now more detailed and easier to understand. We added a new chart that shows the number of active keys for your API and allows you to set a timeframe. 
+
+
+![Analytics](/images/changelog/2023-12-15/verifications.png)
+
+![Active keys](/images/changelog/2023-12-15/active-keys.png)
+
+
+### We moved to Cloudflare
+
+Unkey's API has been on Fly.io since we launched in June. We've been reasonably happy with its performance, but we wanted to move to a more reliable and faster platform. We decided to move to Cloudflare Workers, a serverless platform on Cloudflare's edge network. After this change, Unkey's API runs on 300+ data centers worldwide, making it faster and more reliable. You can check out the new [API code in our repository](https://github.com/unkeyed/unkey/tree/main/apps/api) to see how we made the changes from Go to Typescript using Hono
+
+
+Below is a chart of our latency at P95. Can you tell when we moved to CF?
+
+![P95 results](/images/changelog/2023-12-15/speed.png)
+
+
+### New billing page
+
+We added a brand new billing page to the dashboard. Previously, you could change your plan and see your current usage. Now, you can see your billing history, change your payment method, and see your current billing cycle. My favorite part is that you can now see a projected forecast of your usage for the month and a projected bill.
+
+![Billing page](/images/changelog/2023-12-15/billing.png)
+
+
+### RPC methods
+
+With the move to Cloudflare workers, we decided to move to RPC methods. RPC makes it extremely easy to version our API and follow a standard. 
+
+> Note: We will continue to support the old API for the next few months. We will send out a deprecation notice before we remove the old API.
+
+
+All our RPC methods are now in the format: 
+
+```
+https://api.unkey.dev/{version}/{service}.{method}
+```
+
+Below are a couple of examples of RPC methods: one is a GET request, and the other is a POST request. 
+
+```
+curl "https://api.unkey.dev/v1/keys.getKey?keyId=key_123" \
+  -H "Authorization: Bearer <ROOT_KEY>"
+```
+----------------
+```
+curl -XPOST "https://api.unkey.dev/v1/keys.createKey" \
+  -H "Authorization: Bearer <ROOT_KEY>" \
+  -H "Content-Type: application/json" \
+  -d '{"apiId": "api_123", "name": "My Key"}'
+```
+
+
+### Content you might have missed
+
+[UX of UUIDs](https://unkey.dev/blog/uuid-ux): Andreas wrote an article on the UX of UUIDs and how some minor tweaks can make a big difference in the user experience.