The Trassets Data API exposes your real-estate data through two distinct endpoint types. Each type is optimized for a different integration pattern: category endpoints serve normalized, business-ready data that you can query directly, while raw endpoints expose full source tables for bulk replication and data warehousing.
Category Endpoints
Category endpoints follow the path pattern /{category}/{api_table} and return denormalized, business-ready data that is pre-filtered to your customer scope.
Use these endpoints for day-to-day integrations, dashboards, and incremental data fetches. They support offset-based pagination with limit and offset query parameters, and they return pagination metadata in response headers such as X-Total-Count, X-Has-More, X-Next-Offset, and X-Next-Cursor.
Example request to a category endpoint:
Raw Endpoints
Raw endpoints follow the path pattern /raw/{table_name} and return full, unfiltered source tables exactly as they exist in the replication layer.
Use these endpoints for bulk synchronization, full-table exports, and loading data into a data warehouse. They support cursor-based pagination via the cursor query parameter and a next_cursor field in the response body. The maximum page size is 10,000 rows. The response includes an X-Snapshot-At header that tells you the sync timestamp for the current snapshot.
Example request to a raw endpoint:
To continue paginating, pass the next_cursor value from the previous response as the cursor parameter on the next request. When next_cursor is null, you have fetched every row in the table.
Comparison
Use category endpoints for day-to-day operational queries and raw endpoints for full-table replication into your data warehouse. If you only need a subset of records, category endpoints will be faster and easier to paginate.
