Agentic Fabriq
Benchmark Email
MARKETING · EMAIL
Contacts, lists, campaigns, and reports from the account they connected.
Connecting Benchmark Email in practice
Benchmark Email returns failures inside HTTP 200 responses — a Response.Status of 1 is success and -1 is failure — so a client that branches on the status code reads errors as successes. The credential locks out rather than throttles: five invalid token attempts within two minutes trigger a ten-minute window in which every login is rejected, which is exactly what a connector retrying a rotated key in a loop produces.
Rate limits
- Benchmark Email publishes no requests-per-minute, per-hour or per-day API limit. The only documented throttle is on authentication: "You will receive this error if you have tried to log in with an invalid token/password at least five times within two minutes", which "requires a cooling time of 10 minutes, where any attempts to log in will be rejected".
Worth knowing
- The key does not go in Authorization: it goes in a custom header named AuthToken against the base URL clientapi.benchmarkemail.com, so generic HTTP connectors, gateways and secret-injection layers need configuring specially.
- Token reuse is a documented requirement rather than an optimisation — "Try to store authenticated tokens and reuse them, instead of using login() for each method call" — because re-authenticating per call walks straight into the lockout: "Failure to do so might lead you to be locked out for 10 minutes."
- Bulk reads have to be paged and bulk writes time out: "All our bulk fetching methods like emailGet, listGet, reportGet have the option to fetch specific pages of results" and "Trying to import very large amounts of data might lead to timeouts." No numeric batch-size cap is published.
- Two API generations coexist — the RESTful v3 API and a legacy XMLAPI — with no sunset date for the legacy one, and Benchmark publishes no scope or permission vocabulary for either, so the key is account-wide by default.
Checked against How do I access the Benchmark Email APIs (2026-09-29), Too many API calls detected (2026-09-29), API best practice recommendations (2026-09-29), RESTful API v3 examples (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Benchmark Email behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.