Technical FAQ
Explore our Technical FAQ for quick answers to common questions about Social Plus products. Get troubleshooting tips, best practices, and insights to optimize your technical experience.
Last updated
Was this helpful?
Explore our Technical FAQ for quick answers to common questions about Social Plus products. Get troubleshooting tips, best practices, and insights to optimize your technical experience.
Last updated
Was this helpful?
To create a large number of users, it's advised to use the following endpoint: Register a session.
To obtain your admin token, please follow these steps on the Social Plus console:
Navigate to "Settings" > "Admin Users"
Click on the cogwheel icon.
This will provide you with the necessary 'Bearer' token to use for authorization when performing admin actions.
To retrieve the next page of data from an API, you should use the "next" page token provided at the end of the initial page's results. This token should be appended to the endpoint to fetch the values for the next page.
Here's an example:
{
"paging": {
"next": "eyJza2lwIjoyMCwibGltaXQiOjEwfQ=="
},
}To get the next page of data, append the "next" token to the endpoint like this:
Next Page API Request:
curl --location --globoff 'https://api.sg.amity.co/api/v3/communities?filter=all&sortBy=lastCreated&options[token]=eyJza2lwIjoxMCwibGltaXQiOjEwfQ%3D%3D' \
--header 'accept: application/json' \
--header 'Authorization: Bearer xxx'You can upload a bulk list of blocklisted words using an example like this:
curl --location 'https://api.sg.amity.co/api/v3/blacklist/records' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer xxx' \
--data '{
"regexs": [
"word1",
"word2",
"word3"
],
"isMatchExactWord": true
}'In this example, replace "word1," "word2," and "word3" with the blocklisted words you want to upload in bulk. The request includes the necessary headers and data to add the specified words to the blocklist.
Setting isMatchExactWord to true makes the blocklisting more strict and will only block exact matches, while setting it to false makes the blocklisting more permissive and will block any occurrence of the blocklisted word or expression within a larger text.
API: https://api-docs.amity.co/#/Moderation/post_api_v3_blocklists
You can adjust your follow/unfollow settings by making an API call to the following endpoint: https://api-docs.amity.co/#/Network%20Setting/put_api_v3_network_settings_social. Please refer to the example below to understand the structure:
curl --location --request PUT 'https://api.sg.amity.co/api/v3/network-settings/social' \
--header 'accept: application/json' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer xxx' \
--data '{
"isFollowWithRequestEnabled": false
}'For higher-quality images, you can enhance the resolution by simply adding ?size=full to the end of the URL.
Example: https://api.amity.co/api/v3/files/{fileId}/download?size=full.
Additionally, you have the flexibility to specify the size as "small," "medium," "large," or "full" based on your preferences.
A refreshToken is primarily employed by SDKs to validate the accessToken's validity. When using the API, obtaining a new token can be achieved by making a "register session" API call, eliminating the need to directly manage or use a refreshToken.
The authentication token has a duration of 10 minutes, and it must be used within that specific time frame. For further information on secure mode and authentication tokens, please refer to this section: https://docs.amity.co/analytics-and-moderation/console/settings/security#secure-mode
To list the communities you've joined, use this API: https://api-docs.amity.co/#/Community/get_api_v3_communities.
Set the filter to 'member' to retrieve the communities you are a part of.
curl --location 'https://apix.sg.amity.co/api/v3/communities?filter=member&sortBy=lastCreated&options%5Blimit%5D=100' \
--header 'accept: application/json' \
--header 'Authorization: Bearer xxx'You will have to get a new authentication token after the expiration of the current one, you can call the following API endpoint: https://api-docs.amity.co/#/Authentication/get_api_v3_authentication_token.
curl --location 'https://api.sg.amity.co/api/v3/authentication/token?userId=Amity'
--header 'accept: application/json'
--header 'x-server-key: xxx'After receiving the new authentication token, you can use it to call the register session API to obtain a new access token.
API: https://api-docs.amity.co/#/Session/post_api_v4_sessions
curl --location 'https://apix.sg.amity.co/api/v4/sessions' \
--header 'accept: application/json' \
--header 'x-api-key: xxx' \
--header 'Content-Type: application/json' \
--data '{
"userId": "Amity",
"deviceId": "test",
"authToken": "xxx"
}'You can utilise the following API to obtain an authentication token: https://api-docs.amity.co/#/Authentication/get_api_v3_authentication_token.
For more information about obtaining an authentication token, please visit - Security.
curl --location 'https://api.sg.amity.co/api/v3/authentication/token?userId=Amity'
--header 'accept: application/json'
--header 'x-server-key: xxx'While there isn't a specialized API exclusively for tracking your reactions to posts, you can utilize the "get list of reactions" API. This API, accessible at https://api-docs.amity.co/#/Reaction/get_api_v3_reactions, enables users to see a list of reactions along with the users who reacted. To determine if you've reacted to a specific post, you'll need to query this API and check if you are listed among the reactors.
Absolutely. To update a user's metadata, simply include 'metadata' in the body of your request, and it will be updated as specified. Below are sample cURL commands for reference:
curl --location --request PUT ‘https://api.eu.amity.co/api/v2/users’
–header ‘Content-Type: application/json’
–header ‘Authorization: Bearer xxx’
–data ‘{
“userId”: “Test”,
“metadata”: {
“testmeta”: “usermetaUpdate”
}
}’To delete all posts in your system, first retrieve the posts from community or user feeds using the API found at https://api-docs.amity.co/#/Post/get_api_v3_posts.
After obtaining the posts, utilize the delete post API to remove them, which is available at https://api-docs.amity.co/#/Post%20v4/delete_api_v4_posts__postId_.
Please note, you may need to implement a script to automate the deletion of all posts.
To upload audio files, it is advisable to use the upload API available at https://api-docs.amity.co/#/File/post_api_v4_files.
Yes, you can use this API to filter and find users within a community based on their role, such as 'moderator': https://api-docs.amity.co/#/Community/get_api_v3_communities__communityId__users.
curl --location --globoff 'https://apix.sg.amity.co/api/v3/communities/65e18cd9e66dfc75f3cd8f7d/users?memberships[]=member&roles[]=moderator&options%5Blimit%5D=10' \
--header 'accept: application/json' \
--header 'Authorization: Bearer xxx'Unfortunately, our API is designed to support uploads of files from local storage only, not from URLs.
If you're using the same device ID when register session, it will cause the previously issued access token to become invalid.
The targetType and targetId parameters are essential in query options for fetching posts from a specific feed.
targetType specifies the type of feed, which can be either ‘user’ or ‘community’.
targetId is the identifier for the specific feed, such as a userId for a user feed or a communityId for a community feed.
For a comprehensive explanation of these parameters and their usage, you can refer to the Social Plus SDK documentation on querying posts: https://docs.amity.co/amity-sdk/social/posts/query-post
Currently, posts within a community can’t be sorted by engagement like the global feed. The available sorting options for community posts are ‘lastCreated’ and ‘firstCreated’.
For more information on how to implement these sorting options, you can refer to the Social Plus SDK documentation on querying posts: https://docs.amity.co/amity-sdk/social/posts/query-post
To exclude deleted communities from your query results, you can use different methods depending on whether you’re using the API or SDK:
Using the API: When querying communities through the API at: Query communities API, include the parameter isDeleted: false in your request. This will filter out any deleted communities from the results.
curl --location 'https://api.sg.amity.co/api/v3/communities?filter=all&isDeleted=false'
--header 'accept: application/json'
--header 'Authorization: Bearer xxx'Using the SDK: If you’re utilizing the SDK, you can set the includeDelete: false parameter. This option allows you to control whether deleted communities are included in the query results. For more information on how to use this, visit Social Plus SDK - Query Communities https://docs.amity.co/amity-sdk/social/communities/query-communities and adjust the includeDelete parameter as needed.
Due to privacy and design considerations, it’s not possible to query communities joined by other users, even if you are an admin. However, the current user can query the communities they have joined themselves. This can be done through the API, as detailed at: Query communities API, by filtering for membership.
curl --location 'https://api.sg.amity.co/api/v3/communities?filter=member' \
--header 'accept: application/json' \
--header 'Authorization: Bearer xxx'Alternatively, you can use the SDK, as explained in Social Plus SDK - Query Communities https://docs.amity.co/amity-sdk/social/communities/query-communities.
This behavior is due to pagination implemented in our API endpoints and functions, which default to returning 20 items per page. To access more items, you need to use the next page token (Please refer to the API section above) or the nextPage() function, depending on the SDK you’re utilizing.
For detailed information on how pagination works for different SDKs, please refer to the Live Objects/Collections section in our documentation here: https://docs.amity.co/amity-sdk/core-concepts/live-objects-collections
To update a user’s role in a community, you have two options:
Using API: Add roles to community users API with the following cURL command:
curl --location 'https://api.sg.amity.co/api/v4/communities/657306a3189cef362ea99923/users/roles' \
--header 'accept: application/json' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer xxx' \
--data '{
"roles": [
"community-moderator"
],
"userIds": [
"test"
]
}'For Admin Users Using the Console: You can modify a user's role directly within the console. Follow these steps:
Go to the specific community you wish to manage.
Navigate to the 'Members' tab.
Locate the user whose role you want to change.
Click on the three dots button on the right-hand side.
Select 'Change user role' from the options.
Members can be removed either through the SDK, as detailed here: https://docs.amity.co/amity-sdk/social/communities/community-moderation#remove-members, or by using the API, found at: Delete community users API.
You can delete a community using the API provided here: Delete Community API Alternatively, for admin users, you can also close a community directly from the Social Plus console.
Here's how:
Navigate to the Community tab in the console.
Select "Communities."
Click on the name of the community you want to close.
Go to "Settings" page.
Scroll to the bottom where you will find the "Close Community" option.
You can implement an auto-join function, which can be called after a new user is created. To achieve this, use the join community API, which you can find here: Join community API. By doing this, existing posts in those particular communities will be displayed as the initial content in the global feed for new users.
Metadata consists of additional properties designed for custom fields. It serves to store supplementary data related to specific objects, like a user object, but isn't suitable for large amounts of data or information.
The global feed aggregates posts from communities you have joined and from users you are following. If you haven’t joined any communities or followed any users, there will be no posts for the global feed to display.
The supported image formats for upload are JPG and PNG. Each image must not exceed 1GB in size. A post can contain up to ten images.
Additionally, on iOS & Android UIKit v4, any uploaded images or videos in unsupported formats, like HEIC, will be automatically converted to a suitable format before uploading.
The supported video formats include 3gp, avi, f4v, flv, m4v, mov, mp4, ogv, 3g2, wmv, vob, webm, and mkv. Videos must not exceed 1 GB in size and should have a maximum duration of 2 hours. Each post can contain up to ten videos.
Additionally, on iOS & Android UIKit v4, any uploaded videos (with HEVC encoding or HDR capabilities) will be automatically converted to a suitable video format before uploading.
When using the SDK, you only need the auth token, which should be provided when a user logs in or creates an account. The SDK will manage the process thereafter. For more information, you can refer to the Social Plus SDK documentation on user creation: https://docs.amity.co/amity-sdk/core-concepts/user/create-user
Our global feed offers multiple sorting options, including sorting by factors such as Engagement Rate, Time of Posting, and Updates. Your feed may be currently sorted by other factors, if you wish to update or adjust the feed configuration, please reach out to our support team at support.asc@amity.co
For more detailed information on custom post ranking, you can also refer to our documentation at Custom post ranking.
To list the communities you've joined, you can use the queryCommunities function with the filter set to membership. For more information, refer to the documentation at https://docs.amity.co/amity-sdk/social/communities/query-communities.
To enable file downloading, incorporate the file ID into the download button's path. Use the following URL pattern, replacing "fileID" with the actual file ID:
Path: https://api.region.amity.co/api/v3/files/fileID
Additionally, leverage the SDK to retrieve the file ID. This approach allows for a seamless integration of the download functionality into your application.
Please ensure that your message or post is of the file type.
To customize the UIKIT and make the first channel automatically open when a user logs in, you’ll need to make some changes to the code in the
Amity-Social-Cloud-UIKit-Web-OpenSource/src/chat/components/RecentChat/index.js file.
Here are the steps to do that:
First, you’ll need to add an import statement for useState at the beginning of the file. Add this line to the top of the file along with other import statements:
import React, { useEffect, useState } from 'react';Next, you’ll need to add some code inside the RecentChat component. Here’s the code you need to add:
const RecentChat = ({ onChannelSelect, onAddNewChannelClick, selectedChannelId }) => {
// This line retrieves the list of channels, along with some additional information.
const [channels, hasMore, loadMore] = useChannelsList();
// This line initializes a state variable to keep track of whether the component has been initialized.
const [hasInitialized, setHasInitialized] = useState(false);
// This useEffect function will run when the component is first mounted and whenever 'channels' or 'hasInitialized' changes.
useEffect(() => {
// Check if the component hasn't been initialized and there are channels available.
if (!hasInitialized && channels?.length) {
// If the conditions are met, select the first channel in the list.
onChannelSelect(channels[0]);
// Mark the component as initialized to prevent this from happening again.
setHasInitialized(true);
}
}, [channels, hasInitialized]);
// The rest of your component code goes here...
return (
// JSX code for your component...
);
};By adding this code, you’re ensuring that when the component loads and there are channels available, it will automatically select the first channel in the list and set the hasInitialized state to true to prevent it from happening again.
We recommend using our conversation channel, which offers the capability to check for an existing channel between users. For details, see Create Conversation Channel.
To query posts by tags, format your query like this: tags[]=tag1&tags[]=tag2.
curl --location --globoff 'https://api.sg.amity.co/api/v4/posts?targetId=65e18cd9e66dfc75f3cd8f7d&targetType=community&sortBy=lastCreated&tags[]=tag1&tags[]=tag2' \
--header 'accept: application/json' \
--header 'Authorization: Bearer xxx'Due to the design of our current product architecture, querying comments can only be performed using a post ID, not a user ID.
If you already followed our docs here:
and it still doesn't work. Ensure you’ve covered all bases in this checklist:
• Verify that you’re using a production certificate.
• Check if the app_id matches the issued push certificate.
• Confirm the certificate hasn’t expired or been revoked.
• Make sure the app enables the “push notification” capability.
• Ensure the app is running in a production build (TestFlight/App Store).
• Run the app on a real device.
• Verify that the user hasn’t disabled push notifications for the app.
• Check if the user’s “Do Not Disturb” mode is activated.
• Ensure that your APNs authentication key is uploaded to Firebase: Link
No, we would recommend you use our realm which is included in the iOS SDK and UIkit. You can check the compatible version between the iOS SDK and Realm on our changelog page in the compatibility section and adjust the version accordingly.
For more information on the iOS SDK and UIKit, you can visit:
To register push notifications on iOS, you'll require a .p12 certificate. During the process, make sure to select "Apple Push Notification Service SSL (Sandbox & Production)"
For detailed instructions on setting up an iOS push certificate, please consult this documentation: iOS Push Notification Certificate Setup.
It's not feasible to use a TypeScript CDN without a package manager. We recommend using package managers like npm or Yarn for support.
To check if you have blocked a user, refer to the "Blocked Users List" in the Social Plus documentation. This section provides instructions on how to view and manage your list of blocked users. For more information, you can visit: https://docs.amity.co/amity-sdk/social/block-and-unblock-user#blocked-users-list
You can mark messages as read using the Mark Message Read function. After marking a message as read, you may proceed with actions such as notifications or updates to the backend. For detailed guidance, refer to the documentation on Start/Stop Reading a Subchannel.
The current Flutter SDK only supports video, image, and file post types. Support for Poll posts is anticipated in future updates.
To get the voters for a specific answer in a poll, you can utilize the API endpoint provided: Get a poll answer. This API will return the user IDs of the voters along with their answers in the response.
No, you can either create a poll or add a different type of attachment, but not both together.
Currently, polls are not viewable directly through the console. However, if you have access to the Social Plus portal at https://portal.amity.co/, you can find your polls by navigating to My Dashboard > Posts and selecting "Poll" from the dropdown menu in the top right-hand side. This will display your poll posts.
To obtain your admin token, please follow these steps on the Social Plus console:
Navigate to "Settings" > "Admin Users"
Click on the cogwheel icon
First, your portal owner/head of admins needs to create the initial admin user on the console. Subsequent admin users can then create or grant access to additional team members. To do this, navigate to ‘Settings’ > ‘Admin Users’ and click on the ‘Create New Admin’ button located at the top right of the page. Fill in the username and password; team members can use these credentials to access the console.
Initially, only the portal owner can upload the PNS Certificate. They will find the option to do so by clicking on the “+ Add new certificate” button, which is exclusively available to them for the first upload.
The 'User' option, found under the 'Posts' section with 'User' selected in the dropdown menu, is specifically meant for fetching posts from a user's feed. Please note that it is not intended to retrieve posts from communities where a user has posted, based solely on the user's ID.
Please log in to your console, and you will find your API key and app region (endpoint) in the "Settings" > "Security" tab.
Changing the console password should be done through your super admin. Follow the provided steps for assistance.
Conversation channels are intentionally not accessible on the console by design. For further information on channel characteristics and this design choice, please visit Channel Characteristics.
On our console, you can only activate one push notification certificate per platform. It’s not possible to activate two iOS or two Android push notification certificates simultaneously.
To create new app environments for various purposes, like testing or production, follow these steps:
Log in to your Social Plus portal.
In the upper right corner, you'll find a "Create Application" button.
We recommend creating a separate application for each environment based on its specific purpose. This helps keep your testing and production environments organized and distinct.
Unfortunately, upgrading your application plan is not available at the moment. We recommend creating a new application with your desired plan instead. If you no longer need your previous applications, we can assist you in deleting them.
You can log in to your portal, navigate to the "Manage Payment" tab, and update the "Organization Name".
For this use case, you can use our user's object metadata field to store the postId of the posts the user wants to save so that they can be extracted and fetched later. The saved content can be accessed from the user's profile or a dedicated section within the user interface. The exact implementation and design of this feature can vary depending on the specific requirements and design of your application.
To add a Verified badge to a user’s profile, you need to update their user object’s metadata by including a ‘verified’ label. Once this label is in place, the frontend system can retrieve this information and display the Verified badge, styled as a blue tick or as per your custom design preferences. The verification process, governed by your frontend logic, ensures that the account meets your criteria for verification. After the account is verified according to these standards, you can then insert the ‘verified’ label into the metadata of the user’s profile.
While our product does not directly provide this feature, you can implement it on your end by updating the metadata of users. Invited users’ metadata can include an ‘invitedCommunity’ list. You can extract this list to query community details and display them. Once a user accepts or declines the invitation, the CommunityID will be removed from their metadata.
To share a post, create a new post and specify the destination target for the shared content.
In the metadata of the newly created post, include the original post's ID, for instance: "originalPostID": "abc".
When retrieving the shared post, implement frontend logic to check for the presence of the "originalPostID" field in the metadata. If found, fetch the original post using the provided ID (e.g., by calling "get post") and display it on the frontend.
This approach enables you to maintain a reference to the original post, ensuring consistency in content, reactions, and comments.
For email notifications, you can leverage our webhook events triggered when a post is flagged. You can find more details in the documentation here:
To receive email notifications based on this webhook event, you may need to implement this functionality using a third-party tool that can send email notifications when the webhook event is triggered, such as when a post is flagged.
While direct support for pinning posts is not available in Android UIKit versions below 4.0.0-beta14 and iOS UIKit versions below 4.0.0-beta15., you can implement a workaround by following these steps:
To Pin a Post:
Add a new option to the three-dot menu of the post.
Upon selection, implement logic to verify the user's role. If they possess a role that permits pinning posts, display the "Pin Post" option.
When selected, use the Social Plus SDK to update the community object’s metadata to include the pinned post.
To display the Pinned Post:
When querying the community feed, you'll also retrieve the community object.
Extract the “pinPostID” from the community object’s metadata.
Use the Social Plus SDK’s function to fetch the post using the “pinPostID”.
Place this post object at the top of the community feed list array, ensuring it appears first.
There are two approaches:
This is a simpler method where you can modify the user interface to hide or disable the channel creation button. This approach is straightforward and can be effective for casual users. However, it has a significant limitation:
Security Concern: Even if the button is hidden on the frontend, tech-savvy users might still be able to create channels using the API directly. This means that while the option may not be visible in the user interface, it’s not truly restricted at the system level.
If you are using the Social Plus Max package, a more robust solution is available through the Pre-Hook Event feature 1. This feature allows you to set up custom rules and control various aspects of your application, including channel creation.
Although Social Plus doesn't offer a built-in feature to filter posts by type directly in the global feed, you have the flexibility to create a custom filter on your frontend. Utilize the API to query posts by type at https://api-docs.amity.co/#/Post/get_api_v3_posts, then display the filtered results on your frontend.
Currently, SDK does not supply the duration of audio files. Nonetheless, there is a solution to show the audio duration:
Upon finishing the audio recording, record the audio's duration within the message's metadata.
To reveal the audio duration, retrieve this detail from the message metadata.
You can utilize our search post API to filter posts by using the postedUserId parameter
To implement push notifications in Web React JS, you can utilize our webhook events. These events provide real-time updates on new posts and comments, including sender and receiver information. You can use this data to customize your push notifications with specific labels, details, and payload.
For a complete list of available webhook events, please visit: https://api-docs.amity.co/#/WebhookEvent
Content search will only return posts that were created after the content search feature was enabled. Posts created before the enablement will not be included in the content search response.
Please be aware that only posts created after the feature was enabled will be part of the search results.
When creating posts, you can include hashtags as you normally would. To search for these hashtags, we suggest using our content search feature, and including "hashtagList" in your query.
"hashtagList":[
"#tags1",
"#tags2",
"#tags3"
]You can find comprehensive guidance on how to utilize this feature in our documentation here: https://docs.amity.co/developers/beta-features/content-search
To inform a user that they have gained a new follower through the API server, you can make use of Social Plus's Webhooks. Webhooks enable the sending of real-time notifications for specific events, such as a user beginning to follow someone else. For comprehensive guidance on configuring and implementing Webhooks within Social Plus, please consult the resources below:
For notifications related to follow events, you can utilize either of the following webhooks:
For notifications when a follow is created: Follow Did Create Webhook
For notifications when a follow request is made: Follow Did Request Webhook. This is applicable if you have enabled the follow request feature. For additional details on the user connection method concept, please visit: https://docs.amity.co/amity-sdk/social/follow-unfollow#user-connection-method-concept
This error typically arises when an SDK function is called before successfully establishing a connection to the Social Plus session. To resolve this, ensure that you call UserRepository related functions only after the session state is set to ‘established’. You can monitor the session state using the following code snippet:
const [sessionState, setSessionState] = useState('');
useEffect(() => {
return Client.onSessionStateChange((state: Amity.SessionStates) => {
setSessionState(state);
});
}, []);This code tracks the session state, and you should proceed with calling SDK functions once the state confirms the session is established.
The error indicates a problem with the pagination token. In the result response, a pagination token is provided at the end of the first page. You should use this token to fetch subsequent pages. The response typically includes a "paging" section with "next" and "previous" strings, like this:
"paging": {
"next": "string",
"previous": "string"
}Use the value from the ‘next’ or ‘previous’ string as your query token to access additional pages.
This error occurs when the SDK login process is in progress while other actions are attempted. To resolve this, you should ensure that other actions are initiated only after the login process has successfully completed.
Our API/function has a rate limit of 100 calls per user within a 5-second window. To avoid encountering this error, it is important to carefully monitor and control the number of calls made to ensure they do not exceed this defined limit.
If you've encountered error code 400314 while trying to post content containing an image, it is likely related to our image moderation settings. To address this issue, follow these steps:
Confirm whether you have enabled image moderation in your console settings. You can do this by accessing the console and checking the image moderation settings under Settings > Image Moderation tab.
Adjust the confidence level in the console to an appropriate setting. For detailed instructions, please refer to this link: Image Moderation Settings.
If you are curious about how the confidence level functions and have questions, you can find answers in our FAQ section: Image Moderation FAQ.
Please be cautious not to set the confidence level too low, as it may result in the blocking of all images.
This error occurs because we have link moderation in place. You can manage this feature in the console by going to the "Moderation" > "Allow list" tab. If the feature is enabled, links that have not been added to the allow list will not be permitted to be posted in the community or chat.
Error 400311, known as RPCRateLimitError, indicates that the API/function call rate limit has been exceeded, with a cap of 100 calls per user within a 5-second window. To resolve this, it's advisable to check for any processes that might be making repeated API or function calls in a loop, which could be causing the limit to be reached.
Once a user is deleted using the API : Delete user API, it is not possible to undo this action. The user is permanently removed.
To delete inactive users, you can make use of the following API call:
Here's an example:
curl --location --request DELETE 'https://api.sg.amity.co/api/v4/users/test2?deleteAll=true&markMessageDeleted=false&hardDeletePost=false&hardDeleteComment=false' \
--header 'accept: application/json' \
--header 'Authorization: Bearer xxx'After the user is deleted, their display name will be automatically changed to 'Deleted user'. Please be aware that once users are deleted, there is no way to restore them.
When a user is globally banned by an admin, they lose the ability to authenticate with ASC and are automatically removed from all their existing channels. Additionally, all of the banned user’s messages are deleted, although if these messages are already cached in the SDK, they will only disappear upon refreshing.
However, the user’s social content, including posts, comments, and community memberships, remains intact.
The globally banned user will be unable to authenticate with Social Plus’s network again until the global ban is lifted.
Concurrent connections (CCU) are counted on a per-tab basis within the same web browser on the same device. If a user opens multiple tabs and all are active simultaneously, each active tab is counted as one concurrent connection.
However, browsers may close WebSocket connections for inactive tabs, so the CCU count typically reflects the number of active connections at any given time. For instance, if only one tab is active at a time, only one CCU is recorded.
Social Plus does not fully support a dark theme at the moment. However, you can customize the UI to create a dark theme using our open-source UIKit, which offers flexible UI customization options.
To delete an unused application, please contact our support team at support.asc@amity.co, and they will assist you in fulfilling your request.
Inactive users are defined as the total unique users, identified by their user IDs, who have registered within the Social Plus system but have not established any connection to any Social Plus network during the specific month for which the Monthly Active User (MAU) count is being calculated. This includes users who may have registered at any time in the past, such as someone who signed up in January but has been inactive since then, and are still considered inactive in the subsequent months like May.
You can download Figma files from the following links:
For Social Figma file: Social Plus Social UI Kit Figma.
For Chat Figma file: Social Plus Chat UI Kit Figma.
Social Plus can support multi-tenant systems by allowing the creation of multiple applications. Each application functions independently, maintaining its own separate data and content. This setup ensures that users cannot access content from other applications, effectively facilitating a multi-tenant environment.
Currently, Social Plus requires that all files be uploaded to its servers through the SDK/API. Using an external backend for file uploads is not supported.
Regrettably, metrics such as Monthly Active Users (MAUs) and engagement figures are only available on an individual application basis. These statistics can be accessed through our dashboard and console.
For an in-depth guide to the dashboard, you can refer to the Social Plus Portal Dashboard Guide. For console access, visit https://asc.amity.co/ and navigate to the usage page.
<b> or <i>, when sending a message or creating a post on Social Plus via API?Social Plus places a high priority on backend security to protect against injection attacks, including XSS, with all security measures undergoing periodic penetration testing. It's important to note that the frontend application is also susceptible to XSS attacks, which are beyond our control.
The Social Plus API processes post messages as plain text and does not natively support rich text formatting, like bold, italic, or hyperlinks. This design choice is made to safeguard data security and integrity and to mitigate the risk of cross-site scripting (XSS) attacks.
Nonetheless, the capability to support text formatting rests with the client-side editor and message renderer. You have the option to implement a system on your frontend that accommodates text formatting. For instance, employing a markdown language to encase text with specific symbols allows your frontend to identify and render the text according to the intended formatting.
Currently, .gif files are not supported for posts or messages on Social Plus.
