Skip to main content

EasyPoll API Documentation

Welcome to the EasyPoll API documentation! This guide provides all the information you need to interact with the EasyPoll API, including endpoints, request and response formats, authentication methods, and more.

The EasyPoll API is in beta

Endpoints, request bodies and responses can still change, and breaking changes are possible while the beta label is in place. Do not treat the current shape of a response as stable. Please refer to this documentation for the latest updates.

Base URL​

The base URL for all API requests is:

https://easypoll.com/api/v1

Versioning​

The API version is part of the path, and v1 is the current version. The version segment says which shape the contract has, not how stable it is. Leaving beta will not change the path.

Requests without a version segment (https://easypoll.com/api/...) are still answered and are treated as v1, but they are deprecated and respond with Deprecation and Link headers.

The easypoll.bot API base URL is deprecated

Requests to https://easypoll.bot/api continue to be served, but support for this address ends on December 31, 2026, 23:59:59 UTC. Responses from that host carry a Sunset header with this date. Please migrate your integration to https://easypoll.com/api/v1 before then.

Authentication​

To authenticate with the EasyPoll API, you need to obtain an API key. You can get your API key by logging into the EasyPoll dashboard and navigating to API Keys.

Include your API key in the Authorization header of each request to authenticate:

Authorization: Bearer <api-key>

Rate Limiting​

The EasyPoll API enforces rate limiting to ensure fair usage. If you exceed this limit, you will receive a 429 Too Many Requests response. You can check your current rate limit status using the following headers in the API response:

  • x-ratelimit-limit: The maximum number of requests allowed in the time window
  • x-ratelimit-remaining: The number of requests remaining in the time window
  • x-ratelimit-reset: The time in seconds until the rate limit resets

If you hit a rate limit, you should wait until the reset before making additional requests.
The retry-after header in the response indicates the number of seconds to wait before retrying.