Has anyone successfully connected to RentPost’s API using a Custom integration key?

Follow

Nicolo Ciantro

September 18, 2026 21:05

I’m trying to connect RentPost to our reporting and automation tools, starting with read-only access.

I created a Custom integration, selected our Manager role and the Production environment, and generated an API key. However, multiple freshly generated keys return:

HTTP 401 — “Invalid, expired or revoked auth token.”

The connection we tested uses:

• Endpoint: https://api.rentpost.com/graphql

• Authentication: Authorization: Bearer <API key>

• A minimal GraphQL query: { __typename }

Support previously told me API documentation wasn’t ready, so I’m wondering whether custom integration keys require a different endpoint, another header, or an activation step.

Has anyone successfully connected through Zapier, Make, or a custom script? A working example with credentials removed, or a pointer to the correct instructions, would be greatly appreciated.

Thanks!

1

• Official comment

  

  Jacob Thomason September 21, 2026 07:19

  Hello Nicolo.  Yes, the API requires an auth token.  Currently, the generation of new tokens is disabled, in preparation for our new update scheduled very soon.  The new update will include many breaking changes.  Therefore, to prevent any additional refactors, we've limited new auth tokens to request only.  If you'd like to proceed with a new token, despite these imminent breaking changes, please email relax@rentpost.com and we can issue you one.

  After our new update is released, you'll be able to generate a new token from within your user account.  Thanks!

  Comment actions Permalink

Please sign in to leave a comment.