> ## Documentation Index > Fetch the complete documentation index at: https://docs.realie.ai/llms.txt > Use this file to discover all available pages before exploring further. # Owner Search > Search parcels by recorded current-owner name. Requires state and at least one of lastName or nameContains. Both recorded owner-name slots are searched. The v3 result window is limited to 200 candidate parcels, so broad names can return an incomplete set; refine the query to narrow the results. Pagination uses limit and offset, with offset + limit at most 200 on v3 reads. The account response-shape setting controls whether properties contain nested v3 records or the v2-compatible flat layout; see the [v3 overview](/api-reference/v3/overview) and [Property Data Schema](/api-reference/v3/property-data-schema). Send the API key directly in the Authorization header. Normal API-access and billing checks apply. A successful 200 response costs one token; 400, 401, 403, and 404 responses are not billed. See [Plans and Pricing](/api-reference/pricing). This base endpoint allows up to 100 properties per page. For county filtering, use [Premium Owner Search](/api-reference/v3/premium/premium-owner-search). ## OpenAPI ````yaml api-reference/v3/openapi.json GET /public/property/owner/ openapi: 3.1.0 info: title: Realie Property Data API (v3) description: API for looking up property details by address and unit number. version: 3.0.0 servers: - url: https://app.realie.ai/api security: [] paths: /public/property/owner/: get: tags: - Property summary: Owner Search description: >- Search parcels by recorded current-owner name. Requires state and at least one of lastName or nameContains. Both recorded owner-name slots are searched. The v3 result window is limited to 200 candidate parcels, so broad names can return an incomplete set; refine the query to narrow the results. Pagination uses limit and offset, with offset + limit at most 200 on v3 reads. The account response-shape setting controls whether properties contain nested v3 records or the v2-compatible flat layout; see the [v3 overview](/api-reference/v3/overview) and [Property Data Schema](/api-reference/v3/property-data-schema). Send the API key directly in the Authorization header. Normal API-access and billing checks apply. A successful 200 response costs one token; 400, 401, 403, and 404 responses are not billed. See [Plans and Pricing](/api-reference/pricing). This base endpoint allows up to 100 properties per page. For county filtering, use [Premium Owner Search](/api-reference/v3/premium/premium-owner-search). operationId: ownerSearch parameters: - name: state in: query required: true schema: type: string description: Two-letter state abbreviation (for example, CA). - name: lastName in: query required: false schema: type: string description: >- Owner surname or company name. Required unless nameContains is provided. Matching is case-insensitive. If both lastName and nameContains are supplied, both must match the same recorded owner name. - name: firstName in: query required: false schema: type: string description: >- Optional given-name prefix, used with lastName to narrow the owner match. - name: nameContains in: query required: false schema: type: string description: >- Match every supplied word in the same recorded owner name; word order does not matter. This is word matching, not an arbitrary substring search. Can be used without lastName. Supported only on v3 data reads; otherwise returns 400. - name: fuzzy in: query required: false schema: type: boolean default: false description: >- Set true to allow one edit with the first two characters matching exactly. Use a single-token lastName for fuzzy surname matching, or nameContains for multiword fuzzy queries. firstName remains a prefix match. Supported only on v3 data reads; otherwise returns 400. - name: limit in: query required: false schema: type: integer minimum: 1 maximum: 100 default: 10 description: >- Maximum results per page. Defaults to 10; values above 100 are capped at 100. On v3 reads, offset + the applied limit must be at most 200 or the request returns 400. - name: offset in: query required: false schema: type: integer minimum: 0 default: 0 description: >- Number of matched records to skip. Defaults to 0. On v3 reads, offset + the applied limit must be at most 200. Refine the name query rather than paging beyond this window; cursor pagination is not supported. - name: includeExplicitNulls in: query required: false schema: type: boolean default: false description: >- Set true to include missing public nested property fields as explicit nulls. Requires an account enabled for the nested v3 response shape and a v3 data read; otherwise returns 400. Without this flag, fields with unknown values may be omitted. responses: '200': description: >- Matching properties found. Each successful request consumes one token, independent of the number of properties returned. content: application/json: schema: type: object required: - properties - metadata properties: properties: type: array description: >- Matching current-owner parcels. Accounts enabled for the v3 response shape receive nested property records on v3 reads; other accounts receive the v2-compatible flat shape. See the v3 Property Data Schema for nested fields. items: type: object metadata: type: object required: - limit - offset - count properties: limit: type: integer description: Applied page size after defaulting or capping. offset: type: integer description: Applied number of matched records skipped. count: type: integer description: >- Number of properties in this response, not a total match count. '400': description: >- Bad Request - Missing state or both name parameters, a v3-only mode used on a v2 read, or offset + limit exceeding 200 on a v3 read. Also returned when includeExplicitNulls=true cannot use the nested v3 response shape. content: application/json: schema: type: object properties: error: type: string description: Description of the error that occurred. example: >- Bad Request: State and lastName (or nameContains) are required parameters '401': description: Unauthorized - Missing or invalid API key content: application/json: schema: type: object properties: error: type: string description: Description of the error that occurred. example: 'Unauthorized: API key is missing' '403': description: >- Forbidden - Billing, card verification, subscription status, or overage spending cap blocks access. Follow action before retrying. The first blocking condition is returned; a non-active subscription can return subscription_inactive before unpaid_invoices. See https://docs.realie.ai/api-reference/response-codes#resolving-a-403-response for each code and recovery steps. content: application/json: schema: type: object required: - error - code - action - billing_url properties: error: type: string description: >- Human-readable explanation. Use code instead of matching this text in integrations. example: 'Forbidden: Pay your outstanding invoices to restore access' code: type: string description: Machine-readable reason for the access denial. enum: - card_not_verified - payment_method_required - overage_limit_exceeded - unpaid_invoices - subscription_inactive - subscription_required - subscription_ended - billing_unavailable - billing_configuration_error - access_denied example: unpaid_invoices action: type: string description: >- The next step to restore access. Display this guidance to the person who manages billing. example: >- Open Billing and pay all outstanding invoices. Update your payment card if a payment fails, then retry once your subscription is active. billing_url: type: string format: uri description: >- Billing page where the account owner can resolve the issue. example: https://app.realie.ai/billing example: error: 'Forbidden: Pay your outstanding invoices to restore access' code: unpaid_invoices action: >- Open Billing and pay all outstanding invoices. Update your payment card if a payment fails, then retry once your subscription is active. billing_url: https://app.realie.ai/billing '404': description: Not Found - No properties found content: application/json: schema: type: object properties: error: type: string description: Description of the error that occurred. example: No properties found '500': description: Internal Server Error content: application/json: schema: type: object properties: error: type: string description: Description of the error that occurred. example: Internal Server Error '503': description: >- Service temporarily unavailable, including a database timeout. Retry later. content: application/json: schema: type: object properties: error: type: string security: - apiKeyAuth: [] components: securitySchemes: apiKeyAuth: type: apiKey name: Authorization in: header description: Provide your API key directly in the header. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.