Ironscales API Patterns

Ironscales API authentication requires an API key and a Company ID. You must include these credentials in your requests to the MCP server to securely access incident management and reporting tools.

Use offset-based pagination to handle large incident lists from Ironscales. This API pattern allows you to retrieve data in manageable chunks, ensuring efficient and secure data manipulation without overwhelming the server.

Handle rate limiting by monitoring HTTP error codes returned by the Ironscales API. When you receive a rate limit error, implement backoff strategies in your integration logic to delay subsequent requests.

Available MCP tools cover incident management, statistics retrieval, and allowlist operations. These tools enable you to list open phishing incidents and manipulate security data directly through the API.

HTTP error codes during Ironscales API integration indicate issues like authentication failures or rate limit exceeded. Review these codes to implement proper error handling and ensure robust data retrieval.