POST
/v1/accountsUpdate Account Limits
Configure account-specific operational limits for rate limiting and batch processingTo update account-specific operational limits (like daily profile visits, search limits, or batch size), use this endpoint. The params object contains the updated values for batch size, daily limits per action, or time gaps between batches.
Parameter Keys
batch
Type:
integer
Description:
(Optional) Updated batch size per launch. Controls how many actions run per batch
batch_hours
Type:
integer
Description:
(Optional) Delay in hours between each batch run
[attribute]
Type:
integer
Description:
(Optional) Daily limit for the specific attribute like profiles, searches, or messages
Headers
| Key | Value | Required |
|---|---|---|
| Authorization | Token YOUR_API_KEY | Yes |
| Content-Type | application/json | Yes |
Request Body
accountstring
RequiredExample: 2372242060b59e03ac39f7691765bbf8
typestring
RequiredExample: sales-nav-sync
paramsobject
RequiredExample: {batch: 20, profiles: 150, searches: 199, batch_hours: 2}
Response Field Explanations
params.default
object
Example: {...}
params.user
object
Example: {...}
params.user.batch.current
integer
Example: 0
params.user.batch.last_batch_at
string
Example: 18/07/2022 21:47:09
params.user.[attribute].value
integer
Example: 0
params.user.[attribute].timestamp
integer
Example: 1716508800
Pro Tip
Adjust batch and batch_hours to control how aggressively your account scrapes. Lower values help avoid platform rate limits.
Warning
Don't exceed the max values defined in the account type's default params. Higher limits may trigger anti-bot measures.
Note
The params.user object tracks real-time usage. Use it to monitor how close you are to daily limits.
Pro Tip
Set conservative limits initially and increase gradually based on your account's health and platform tolerance.