Nasze API

User Identifier Conventions

• Path parameter = email: Every user_id in the API routes (for example, /api/v1/users/{user_id}/files) must be the user's email address. It is case-insensitive on the backend, but clients should send it in lowercase to avoid clashes. Remember to URL-encode the @ symbol, e.g. john.doe%40example.com.

• Blob container derivation: When a user is created, we derive their Azure Blob container name from the email by lowercasing it, replacing @ with -at-, replacing . with -, and converting any remaining characters that are not letters, digits, or hyphens into hyphens. Repeated hyphens are collapsed and the name is trimmed to meet Azure's length rules (3–63 characters, starting and ending with an alphanumeric character).

• Collision awareness: Because of the sanitization above, different emails that normalize to the same value (for example, characters that only differ by case, punctuation, or symbols) will share the same storage container. Make sure real user emails remain unique after these transformations to avoid conflicts.

• Metadata rules: Additional metadata stored with user files, such as source_url, must contain printable ASCII characters only. Clients should strip leading/trailing whitespace and avoid characters outside the standard URL set before submitting.