Skip to content
AlterEstate
A developer connecting property listings through the AlterEstate API

AlterEstate API

The AlterEstate API lets you connect websites, property portals, lead forms and internal tools to the AlterEstate real estate CRM.

AlterEstate is a real estate CRM used by agencies and developers across Latin America. The REST API returns JSON and uses the base URL https://secure.alterestate.com/api/v1.


Authentication

The API uses two credentials. Each endpoint page states which one it needs.

CredentialHeaderUsed for
Account tokenAuthorization: Token <key>Leads, contacts, deals and property writes.
Public tokenaetoken: <key>Reading properties and agents. An administrator generates it.
None—Cities and sectors.

Keep the account token on your server

Every endpoint that uses Authorization: Token must be called from your backend, never from a frontend. The account token acts as the user who owns it. Anyone who has it can read and change that agency’s contacts, deals and properties, including clients’ names, phones and emails.

  • Do not put the account token in a website, a single-page app, a mobile app, a browser extension or any JavaScript sent to the browser. Anyone can open the developer tools and copy it. Environment variables bundled into frontend code count as shipped.
  • Have your frontend call your own server. Your server keeps the token in a secret store or environment variable, calls AlterEstate and returns only the data the page needs.
  • Do not log the token, commit it to a repository or paste it into tickets and chats.
  • If the token was exposed, write to dev@alterestate.com right away so it can be revoked.
Correct flow
Browser / mobile app  →  your backend (holds the token)  →  secure.alterestate.com
Browser / mobile app  →  secure.alterestate.com with Authorization: Token   ✗ never

Resources


Pagination

List endpoints for properties, contacts and deals return count, next, previous and results. Pass page to move forward. next is null on the last page.


Errors

StatusMeaning
200The request succeeded.
201The resource was created.
400The body or a parameter is invalid. The response names the field.
401The token is missing or invalid.
404The resource or route does not exist.
429Too many requests. Pause and retry with backoff.
500Server error. Retry, and contact dev@alterestate.com if it persists.

Rate limits

The integration limit is 10 requests per second per account. Pace requests across all workers for that account and retry with backoff on HTTP 429. Honor Retry-After when present. If your integration needs more capacity, write to dev@alterestate.com.


Frequently asked questions

What is the AlterEstate API base URL?

All endpoints live under https://secure.alterestate.com/api/v1 and return JSON.

How do I authenticate with the AlterEstate API?

Send your account token in the Authorization header as "Token <key>" for leads, contacts, deals and property writes, always from your backend. Send the public token in the aetoken header to read properties and agents. Cities and sectors need no token.

Can I call the AlterEstate API from my frontend?

Not with the account token. Any endpoint that uses Authorization: Token must be called from your backend, because anyone can copy a token that reaches the browser or a mobile app and use it to read and change the agency’s CRM data. Your frontend calls your server, and your server calls AlterEstate.

Where do I find my AlterEstate public API token?

An administrator can copy it from the AlterEstate dashboard under Settings → Public API Token.

What is the AlterEstate API rate limit?

10 requests per second per account. Pace requests across workers and back off on HTTP 429. This is a per-second limit, not a separate per-minute or daily quota.

Who do I contact for API support?

Write to dev@alterestate.com.

Last updated . Questions? Emaildev@alterestate.com.