API references
Search documentation... ⌘K
API references
Open merchant dashboard
Merchant API
All our references

Filter Payment Links

Returns a paginated list of payment links for the authenticated merchant with advanced filtering capabilities.

This endpoint provides comprehensive search functionality using database-driven filtering, allowing you to filter links by status, amount ranges, and date ranges.

The response includes pagination controls with previous and next cursors that can be used to navigate through the payment link history efficiently.

Features:

  • Full-text search: Search across payment link descriptions and UIDs
  • Advanced filtering: Filter by status (active, disabled, expired, paid)
  • Range support: Support for amount ranges and date ranges
Endpoint signature
This endpoint requires an API key. Read our authentication guide for more information.
POST https://api.reservepay.com/merchants/filter-payment-links HTTP/1.1
Content-Type: application/json
Accept: application/json
Authorization: Bearer <token>
{
per_page: number?,
page: number?,
terms: string?,
status: string?,
amount: string?,
created_at: string?,
expires_at: string?,
}
Returns: object
New to Reservepay? Read our guide on how to call endpoints to get started. Note that this endpoint returns a paginated response, see the Pagination section of the same guide.
Request arguments
per_page number

Optional. Number of payment links to return per page. Default: 10, Maximum: 100

page number

Optional. Page number for pagination. Default: 1 (first page)

terms string

Optional. Full-text search across payment link descriptions and UIDs. Uses fuzzy matching for partial text matches.

status string

Optional. Filter by status (active, disabled, expired, paid)

Allowed values:
  • ACTIVE
  • DISABLED
  • EXPIRED
  • PAID
amount string

Optional. Filter by amount. Supports: exact amount (1000), range (1000..5000), or boundless ranges (1000.. or ..5000). Amounts are in the smallest currency unit (cents for USD).

created_at string

Optional. Filter by creation date. Supports: specific date (YYYY-MM-DD), date range (YYYY-MM-DD..YYYY-MM-DD), or keywords (today, yesterday, this_week, last_week, this_month, last_month)

expires_at string

Optional. Filter by expiration date. Supports: specific date (YYYY-MM-DD), date range (YYYY-MM-DD..YYYY-MM-DD), or keywords.

Response attributes
Attribute Description
previous
object

Pagination for the previous page. Contains 'before' (page number) and 'perpage' (page size) parameters. Use these values in the 'page' and 'perpage' parameters of the next request to get the previous page. Returns null if there is no previous page.
page
array

The current page of records, ordered by creation date (newest first). Each record is serialized according to the specified record_serializer option.
next
object

Pagination for the next page. Contains 'after' (page number) and 'perpage' (page size) parameters. Use these values in the 'page' and 'perpage' parameters of the next request to get the next page. Returns null if there is no next page.
Errors common to all endpoints
UNHANDLED_ERROR

This error occurs when the server encounters an unexpected internal error that it cannot handle gracefully. This typically happens due to bugs, infrastructure issues, or edge cases that weren't anticipated during development.

INVALID_ARGUMENTS

This error occurs when the request contains invalid or missing parameters. Common cases include missing required fields, or values that don't match the expected format or type.

BAD_VERSION

This error occurs when making requests to an API version that does not exist. This commonly happens when using an outdated SDK or when the API version specified in the request URL is incorrect.

CODE SAMPLES
curl
Learn how to run these code samples in your terminal by reading our guide.