---
title: "Get a list of offices for all destinations"
method: GET
path: "/odata/v1/Office/OfficeReplication()"
tags: ["Office"]
---

# Get a list of offices for all destinations

`GET /odata/v1/Office/OfficeReplication()`

Both methods are valid and return the same result:
The path-style is more intuitive and commonly used in RESTful APIs.
The function-style follows OData conventions.

<b>Path-style access: </b>```/odata/v1/Office/OfficeReplication```

<b>Function-style access: </b>```/odata/v1/Office/OfficeReplication()```

## Query parameters

- `$select` string
- `$count` boolean
- `$filter` string
- `$orderby` string

## Response `200`

OK

- DDFInfrastructureSwaggerExampleModelsODataReplicationListResponse2DDFCoreEntitiesOfficeIdentifierDDFCoreVersion1000CultureNeutralPublicKeyTokenNullDDFCoreEntitiesOfficeDDFCoreVersion1000CultureNeutralPublicKeyTokenNull
  - `@odata.context` string, nullable
  - `value` DDFCoreEntitiesOfficeIdentifier[], nullable
    - `OfficeKey` string, nullable — A unique identifier for this record from the immediate source. This is the numeric only key and used as an alternative to the OfficeKey fields.
    - `ModificationTimestamp` string, date-time, nullable — Date/time the roster (member or office) record was last modified (in Zulu time (UTC)).

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `404` — Not Found
- `500` — Internal Server Error

---

[API](https://skmtc.net/realtor/apis/realtor-ca-ddf-web-api-documentation.md) · [All operations](https://skmtc.net/realtor/apis/realtor-ca-ddf-web-api-documentation/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/realtor/realtor-ca-ddf-web-api-documentation/versions/17c9ffddac21/schema)