# Custom Fields Accessibility

**URL:** <https://community.servicem8.com/t/custom-fields-accessibility/1211>\
**Category:** General\
**Created:** [September 30, 2026, 8:57pm UTC](https://community.servicem8.com/t/custom-fields-accessibility/1211 "2026-09-30T20:57:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![steven\_williams](https://avatars.discourse-cdn.com/v4/letter/s/e47774/32.png) [@steven\_williams](https://community.servicem8.com/u/steven_williams)\
**Post date:** [September 30, 2026, 8:57pm UTC](https://community.servicem8.com/t/custom-fields-accessibility/1211/1 "2026-09-30T20:57:10Z")

</div>

I see many posts related to trouble accessing custom fields via API. I don’t want to pay to add custom fields just to later discover that they are not accessible via API.

I don’t see confirmation of resolutions listed…

1. Are Custom Fields on the Job Record accessible via API?

2. Are there any current issues, other than user originated, that may prevent access to a custom field on the Job record?

---

<div class="post-metadata">

**Author:** ![Cody](https://sea2.discourse-cdn.com/flex002/user_avatar/community.servicem8.com/cody/32/52_2.png) [@Cody](https://community.servicem8.com/u/Cody)\
**Post date:** [October 3, 2026, 9:00pm UTC](https://community.servicem8.com/t/custom-fields-accessibility/1211/2 "2026-10-03T21:00:41Z")

</div>

Hi Steven,

Yes, once a Job custom field exists on an account, its value is accessible through the Job record in the REST API. The API field name uses the `customfield_` prefix.

Creating or managing custom-field definitions through the Custom Fields API is limited to Public Applications using OAuth 2.0. Existing custom-field values can be read or written through the REST API.

Custom Fields documentation: [Overview](https://developer.servicem8.com/docs/custom-fields-overview)

Thanks,  
Cody