GET
/status/{address}Get transaction status
Returns the deposits and withdrawals seen at a bridge address, newest first. Responses are cursor-paginated: each request returns one page plus a `nextCursor`. To read the full history, pass each `nextCursor` back as `cursor` until it comes back null. To track only recent activity, keep requesting the first page without a cursor.
- Base URL
- https://bridge.polymarket.com
- Auth
- Public, no key
- Rate limit
- 50 req / 10s (5 per second)
- Limit applies to
- Bridge API general
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
| address | path | string | yes | The bridge address to query for transaction status, taken from the `/deposit` or `/withdraw` response. EVM, Solana, Tron, and Bitcoin address formats are supported. EVM addresses are normalized before the request is forwarded upstream. |
| limit | query | integer | no | Maximum number of transactions per page. A page may contain fewer transactions than requested and still have a following page. |
| cursor | query | string | no | Opaque continuation token returned as `nextCursor` by the previous response. Omit it to request the first page. URL-encode it, since cursors can contain characters such as `+`, `/`, and `=`. Invalid, tampered, or cross-address tokens return 400; restart the walk without a cursor when that happens. |
| paginate | query | string | no | Compatibility parameter forwarded upstream for existing integrations. Pagination applies whether or not it is sent, so new integrations should omit it and use `cursor` and `limit` alone. When sent, the only supported value is `true`. |
Example
curl -X GET "https://bridge.polymarket.com/status/<address>"Response fields
| Field | Type | Description |
|---|---|---|
| transactions | object[] | One page of transactions for the given address, newest first. This is a page, not the full history for the address. |
| nextCursor | string | Opaque continuation token for the next page, or null when the pagination walk is complete. Pass it back verbatim as `cursor` on the next request; never parse, modify, construct, or reuse it with a… |
Responses
| Status | Meaning |
|---|---|
| 200 | Successfully retrieved transaction status |
| 400 | Bad Request - Missing or invalid address, limit, or cursor |
| 500 | Server Error |
From Polymarket's published OpenAPI spec and rate-limit tables, synced 2026-10-04.