Users API
The LiquidCommerce User API provides functionality for managing user accounts within the LiquidCommerce ecosystem.
Users API Overview
This API handles all aspects of user data management, from account creation and authentication to profile management and secure data storage.
Key Features
User creation
User management (update user information)
User Addresses
User Saved Payment Methods
Secure handling of Personally Identifiable Information (PII)
PCI DSS compliant data storage and transmission
Data Security and Compliance
LiquidCommerce takes the security and privacy of user data very seriously. Our User API is designed with the following security measures:
PCI DSS Compliance: Our systems are fully compliant with the Payment Card Industry Data Security Standard (PCI DSS), ensuring that all sensitive payment information is handled securely.
Secure PII Handling: All Personally Identifiable Information (PII) is encrypted both in transit and at rest using industry-standard encryption protocols.
Data Minimization: We collect and store only the minimum amount of PII necessary for the operation of our services.
Access Control: Strict access controls and authentication mechanisms are in place to ensure that only authorized personnel can access user data.
Regular Audits: We conduct regular security audits and assessments to maintain the highest levels of data protection.
Data Retention: User data is retained only for as long as necessary and in compliance with applicable laws and regulations.
Data Purging: User data is permanently and securely erased using industry-standard deletion methods when no longer needed or upon request, ensuring complete removal from all systems including backups and archives.
Authentication
Before using the API, you need to obtain an access token from the Authentication API. Include this token in the Authorization header of all API requests:
Authorization: Bearer <YOUR_ACCESS_TOKEN>Error Handling
The API uses standard HTTP response codes to indicate the success or failure of requests. In case of an error, the response body will contain a JSON object with more details about the error.
Rate Limiting
The API is subject to rate limiting to ensure fair usage and maintain performance. If you exceed the rate limit, you'll receive a 429 (Too Many Requests) response.
Last updated