diff --git a/readme.md b/readme.md
index fc9506d7..9dbc97d7 100644
--- a/readme.md
+++ b/readme.md
@@ -1 +1,110 @@
-test notes go here :)
+# Project API Documentation
+
+## API Endpoint Error Handling
+
+### Overview
+This section provides detailed information about potential API errors, their meanings, and recommended handling strategies.
+
+### HTTP Status Codes
+
+#### Client Error Responses (4xx)
+| Status Code | Description | Typical Cause | Recommended Action |
+|------------|-------------|--------------|-------------------|
+| 400 Bad Request | Invalid request syntax | Malformed request parameters | Validate input, check request format |
+| 401 Unauthorized | Authentication required | Missing or invalid authentication credentials | Verify authentication token, re-authenticate |
+| 403 Forbidden | Insufficient permissions | User lacks required access rights | Check user permissions, request appropriate access |
+| 404 Not Found | Resource does not exist | Incorrect endpoint or resource ID | Verify endpoint URL, check resource identifier |
+| 429 Too Many Requests | Rate limit exceeded | Excessive API calls | Implement exponential backoff, respect rate limits |
+
+#### Server Error Responses (5xx)
+| Status Code | Description | Typical Cause | Recommended Action |
+|------------|-------------|--------------|-------------------|
+| 500 Internal Server Error | Unexpected server condition | Server-side processing error | Retry request, report to support if persistent |
+| 503 Service Unavailable | Temporary server overload | High traffic or maintenance | Implement retry mechanism with exponential backoff |
+
+### Error Response Structure
+Typical error responses follow this JSON structure:
+```json
+{
+  "error": {
+    "code": "ERROR_CODE",
+    "message": "Descriptive error message",
+    "details": "Additional error context"
+  }
+}
+```
+
+### Error Handling Best Practices
+1. Always check HTTP status code before processing response
+2. Implement comprehensive error logging
+3. Provide user-friendly error messages
+4. Use exponential backoff for retry mechanisms
+5. Handle network and timeout errors gracefully
+
+### Example Error Handling (Pseudo-code)
+```javascript
+async function apiRequest(endpoint) {
+  try {
+    const response = await fetch(endpoint);
+    
+    if (!response.ok) {
+      const errorBody = await response.json();
+      
+      switch (response.status) {
+        case 400:
+          throw new ValidationError(errorBody.error.message);
+        case 401:
+          handleUnauthorizedError();
+          break;
+        case 500:
+          logServerError(errorBody);
+          break;
+        default:
+          handleGenericError(errorBody);
+      }
+    }
+    
+    return response.json();
+  } catch (error) {
+    // Implement comprehensive error handling
+    console.error('API Request Failed:', error);
+    throw error;
+  }
+}
+```
+
+### Retry Strategy Example
+```javascript
+async function retryRequest(fn, maxRetries = 3) {
+  let retries = 0;
+  
+  while (retries < maxRetries) {
+    try {
+      return await fn();
+    } catch (error) {
+      if (error.status >= 500 || error.status === 429) {
+        const delay = Math.pow(2, retries) * 1000;
+        await new Promise(resolve => setTimeout(resolve, delay));
+        retries++;
+      } else {
+        throw error;
+      }
+    }
+  }
+  
+  throw new Error('Max retries exceeded');
+}
+```
+
+### Monitoring and Logging
+- Implement comprehensive error logging
+- Use structured logging with error codes
+- Monitor API error rates and patterns
+- Set up alerts for recurring error conditions
+
+### Contact and Support
+For persistent issues or unusual error patterns, contact support at support@example.com with:
+- Exact error message
+- HTTP status code
+- Request details
+- Reproduction steps
\ No newline at end of file