The QUERY method
Every endpoint that answers GET also answers QUERY, at the same address and with the same parameters. QUERY is a read like GET, safe to retry, but it carries its parameters in the request body, so a long search stays out of the address and out of the logs that record addresses.
Send the body as JSON or as a form. The answer is exactly the one GET gives for the same parameters, validation errors included.
A parameter may sit in the address or in the body, never in both. Sending the same one twice answers 422 with an error on that parameter.
To page, send QUERY again with the next page in the body. The meta object of the answer says which page this is and how many there are in total.
Every answer from an endpoint that accepts QUERY carries an Accept-Query header listing the body formats it reads. A HEAD request is the cheapest way to check.
Rate limit
Sixty requests per minute, per user, shared by every key and device. Every answer carries the budget left in X-RateLimit-Remaining.
Keys act as you, with exactly the access you have. Make one per integration so you can revoke it alone.