Search
K

Developer Policies

Impermissible ProducerSync API Usage Patterns

The following patterns negatively impact system performance, increase load, or create inconsistent downstream behavior. These usage patterns are not supported and may result in rate limiting, throttling, or degraded performance.

1. Rapid Subscribe → Unsubscribe → Re-subscribe Cycles

AgentSync does not support programmatic workflows that:

  • Subscribe an NPN
  • Immediately remove that NPN
  • Re-subscribe the same NPN within the same billing period

Recommended approach: Maintain stable subscription lists and avoid frequent churn within a billing cycle.

2. Excessive Token Requests

Tokens should be reused for all ProducerSync API calls until they expire. Requesting a new token for each call, or significantly more often than necessary, puts avoidable strain on authentication services.

Recommended approach: Reuse tokens until they expire. See API Authentication for AgentSync's recommended practices.

3. Individual NPN Update Requests

Requests to update your subscribed population should use AgentSync’s aggregated endpoints with pagination.

Making individual update requests for each NPN creates unnecessary load and is not supported.

Recommended approach: Use the bulk/aggregated population update endpoints and paginate through results as documented.

Consequences of Non-Compliant Usage

If customers operate outside of these policies or follow any of the disallowed patterns above, AgentSync may:

  • Apply rate limiting
  • Throttle usage
  • Withhold performance guarantees for affected endpoints

These measures ensure platform stability and protect overall system reliability.