# Using Access Control URL for Membership purchase Steps: - **Step: 1** Step 1: Configure Membership Access - Navigate to the Membership section. - Under the Access Control settings, select the option labeled "Private". - **Step : 2** Configure API Endpoint for Validation - Paste your full API Url with endpoint in the designated field for validation. - ![Screenshot 2024-06-26 at 7.18.26 PM](https://hackmd.io/_uploads/HywVhct8C.png) - **note: The validation call will be constructed as: `/api-endpoint/?account=<CONNECTED-ACCOUNT-ADDRESS>`** - **Step : 3** Add a Failure Description - Add a description that will be displayed if the validation fails. This description should provide clear guidance to the user on what went wrong and how to proceed. - ![Screenshot 2024-06-26 at 7.19.00 PM](https://hackmd.io/_uploads/Syu8hqY80.png) - The failure message will appear during the checkout process if the validation is unsuccessful(as shown below) - ![Screenshot 2024-06-26 at 6.27.49 PM](https://hackmd.io/_uploads/B1o8l5FLR.png) - (**Note: The description supports Markdown text for formatting.**) ## API Required Specifications for Kyoto University ![image](https://hackmd.io/_uploads/B1Fhq5t8C.png) **1. API Response Requirements:** - The API GET call must return a boolean value (1 or 0) with a status code of 200. **2. API Endpoint Construction:** - The API GET call URL will be constructed with an account address parameter, formatted as: `/api-endpoint/?account=<0x...>`. **3. Validation Logic:** - Maintain a mapping of student data to validate if the connected wallet address belongs to a student. - If the wallet address is correct (i.e., it matches a student in your mapping), the API should return `1`. - In all other cases, the API should return `0`. **4. Server Management:** - You can independently create and maintain your server for this API to handle student ID validation against the connected address.