# Company in REST **URL:** \ **Category:** API Q&A\ **Created:** [February 23, 2022, 5:02pm UTC](https://integration.keap.com/t/company-in-rest/86586 "2022-02-23T17:02:17Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Monica\_Burden\_The\_AP](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/monica_burden_the_ap/32/147_2.png) [@Monica\_Burden\_The\_AP](https://integration.keap.com/u/Monica_Burden_The_AP)\ **Post date:** [February 23, 2022, 5:02pm UTC](https://integration.keap.com/t/company-in-rest/86586/1 "2022-02-23T17:02:17Z")
With the XML-RPC we can add text to the Company field, or add ID to CompanyID field to link to a company record. It looks like with REST, we MUST create a company record and add the id to the contact if we want to list a company (or use a custom field). Is this correct? ---
**Author:** ![John\_Borelli](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/john_borelli/32/11880_2.png) [@John\_Borelli](https://integration.keap.com/u/John_Borelli)\ **Post date:** [February 25, 2022, 6:50pm UTC](https://integration.keap.com/t/company-in-rest/86586/2 "2022-02-25T18:50:34Z")
Yes, REST is organized differently and it’s just how it’s designed to function. ---
**Author:** ![TomScott](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/tomscott/32/67_2.png) [@TomScott](https://integration.keap.com/u/TomScott)\ **Post date:** [February 28, 2022, 4:39pm UTC](https://integration.keap.com/t/company-in-rest/86586/3 "2022-02-28T16:39:01Z")
Yes, the older XMLRPC API exposes a lot of “legacy” fields that aren’t currently in use in all versions of our software and will be phased out eventually. Companies previously were just a string value on a Contact record, but currently are a record in their own right with relationships to other records. This change happened a few years ago and solved a lot of problems about variations in company names when records were being added. The REST API follows the current modeling.