Amity API Rate Limits

General
1

Hi,

Do you have some rate limits for calling you API?
Couldn’t find any in documentation.

We are integrating from our backend and sending Posts to up to 200+ Communities (as Admin) and would like to understand rate rate limits, so we do not get throttled.

Thank you.

2

Hello @bn9001 , Yes, our API has a rate limit of 10 calls per second per user. To avoid throttling, please monitor and control the number of API calls, especially when posting to multiple communities.

If you have further questions, feel free to reach out.

3

Thank you for a fast response!

Just to double check - we are calling from backend, not from SDK or UI kit (so, a pure integration from backend, not something that all other users will do).
We are using an Admin user and with admin token.
We are not going to have that many calls for regular users for sure.

  • So, here is still applies only 10 requests per second for Admin user with admin token?
  • Is this per Application or to ask more precise - are there some higher limits on per Application/Account level for these admin calls to API?
  • Are there some other limits like 600 requests per minute or you throttle on more than 10 requests per second?
  • Are there some different limits for payed Core/Max accounts?

Thank you.

4

@bn9001 Thank you for your follow-up questions! Here’s the clarification:

  • 10 Requests per Second: This limit applies to both regular and admin users, even when using an admin token. It’s set to maintain system stability and performance.
  • Per Application/Account Level: The 10 requests per second limit is applied per user, not specifically at the application or account level. It’s important to keep this in mind across all your admin operations to avoid throttling.
  • Additional Throttling: There aren’t additional limits like 600 requests per minute. The main limit is 10 requests per second. If exceeded, you might experience delays due to throttling.
  • Different Limits for Paid Accounts: The 10 requests per second limit applies to all account types, including Core and Max accounts.

Please let us know if you need further assistance.

1 Like
5

If I use the admin access token to trigger bulk user creation (Register Session) and community creation APIs, how does the rate limiting work in this scenario?

6

Hello @vadivelk , Our API rate limit is 100 transactions per 5 seconds per network — this applies to all API calls including Register Session and community creation, regardless of token type.

Could you share roughly how many users and communities you are planning to create? This will help us advise on the best approach. :blush:

7

In my scenario, there is a possibility of more than 100 requests. There are 3 lakh+ users in my system. Whenever a role change happens in my system, the same role should be reflected in Social+ as well.

There is a cron job that runs every hour and processes eligible records, sometimes up to 50,000 records. The processing includes community creation, channel creation, session registration, adding users to communities, adding users to channels, assigning roles to community users, assigning roles to channel users, removing roles from community users, and removing roles from channel users.

8

Hello @vadivelk , Based on your use case, here is our team’s recommended approach to handle high-volume requests while staying within Social+'s limit of 100 requests per 5 seconds.

// Social+ limit: 100 req / 5 sec — we use 80 as safety margin
import Bottleneck from 'bottleneck';

const limiter = new Bottleneck({
  maxConcurrent: 10,
  reservoir: 80,
  reservoirRefreshAmount: 80,
  reservoirRefreshInterval: 5000,
});

async function createCommunity(data) {
  return limiter.schedule(() => api.post('/api/v4/communities', data));
}

Use a single shared limiter instance across all operation types so they collectively never exceed the rate limit. Excess requests will be auto-queued rather than dropped.

Hope this helps — let us know if you have any questions. :raising_hands: