--- title: fields.get | Doing Work API description: Custom field values on one record, with any required fields still empty. Money-type values and currency are null unless you may see prices (see_prices); key. url: https://doingwork.work/docs/reference/fields-get/ --- # fields.get Custom field values on one record, with any required fields still empty. Money-type values and currency are null unless you may see prices (see_prices); key and type stay visible. | | | |---|---| | Who | Agents can call this | | REST | `GET /v1/fields/get` | | MCP tool | `fields_get` | | Writes | no | | Area | [Imports, custom fields, tags and search](https://doingwork.work/docs/reference/#imports-custom-fields-tags-and-search) | ## When to use it Custom field values on one record, with any required fields still empty. Money-type values and currency are null unless you may see prices (see_prices); key and type stay visible. ## What to tell the owner Tell them what you found in plain words. Don't read back raw fields. ## Input | Field | Type | Required | |---|---|---| | `shop_id` | string (uuid) | yes | | `target` | string (one of customer, property, job, quote, invoice) | yes | | `object_id` | string (uuid) | yes | ## Example ```http GET https://doingwork.work/v1/fields/get?shop_id=00000000-0000-4000-8000-000000000000&target=customer&object_id=00000000-0000-4000-8000-000000000000 ``` ## Output JSON. The response shape isn't published yet; read the fields you need and ignore the rest. Errors are `{code, message, status}`. ## Errors | Code | Status | What to do | |---|---|---| | `invalid_input`, `invalid_token`, `rate_limited` | | Can happen on any call. See [errors](https://doingwork.work/docs/errors/). |