# API Confirmation

**URL:** <https://community.hubspot.com/t/api-confirmation/110564>\
**Category:** APIs & Integrations\
**Tags:** oauth, contacts\
**Created:** [July 2, 2024, 7:58pm UTC](https://community.hubspot.com/t/api-confirmation/110564 "2024-07-02T19:58:54Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![MrNiamh](https://avatars.discourse-cdn.com/v4/letter/m/f19dbf/32.png) [@MrNiamh](https://community.hubspot.com/u/MrNiamh)\
**Post date:** [July 2, 2024, 7:58pm UTC](https://community.hubspot.com/t/api-confirmation/110564/1 "2024-07-02T19:58:54Z")

</div>

Hi,

I am working with a client would like to confirm the following are possible through the API before we start the project, should be fairly simple!

1. We have some custom objects (e.g. Organisations), which has its own fields. We need to be able to read some of those properties. Can you confirm we would need to call /crm/v3/objects/{objectType}/{objectId}, which would return a json with a properties field, which would contain the custom field field?

2. Similarly, they have some custom fields on a Contact. Can you confirm we can retrieve these from /crm/v3/objects/contacts/{contactId}}, which would return a json with a properties field, which would contain the list of custom properties?

3. We also need to be able to see which contacts are in which organisation (via associations). Can you confirm we can view these in the responses from the above questions? I.e. we can see the associated contacts from the organisation, and we can see the associated organisation from the contact.

4. We have member registration on the CMS, we want to use a private app so the users can use that same login for a different backend. Is that possible?

---

<div class="post-metadata">

**Author:** ![Bortami](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/bortami/32/221350_2.png) [@Bortami](https://community.hubspot.com/u/Bortami)\
**Post date:** [July 2, 2024, 9:42pm UTC](https://community.hubspot.com/t/api-confirmation/110564/2 "2024-07-02T21:42:50Z")

</div>

1. 

GET

`/crm-object-schemas/v3/schemas/{objectType}`

will return the schema of the object which includes all the available fields. ([docs link).](https://developers.hubspot.com/docs/api/crm/crm-custom-objects)

/crm/v3/objects/{objectType}/{objectId}

will return a specific record’s property values.

2. The above schema endpoint would also work for Contacts.

3. Associations for specific records are returned when you call

/crm/v3/objects/{objectType}/{objectId}

and add associations as a query parameter. If you do not include a parameter, associations are ignored. You get a more consistant response if you use the associations API,

/crm/v4/objects/{objectType}/{objectId}/associations/{toObjectType}.

1. 

HubSpot’s out of the box CMS login is only usable on CMS pages. To use that login across apps, you’d want to look into implementing SSO. ([docs)](https://developers.hubspot.com/docs/cms/features/memberships/sso)

``

---

<div class="post-metadata">

**Author:** ![MrNiamh](https://avatars.discourse-cdn.com/v4/letter/m/f19dbf/32.png) [@MrNiamh](https://community.hubspot.com/u/MrNiamh)\
**Post date:** [July 3, 2024, 3:47pm UTC](https://community.hubspot.com/t/api-confirmation/110564/3 "2024-07-03T15:47:27Z")

</div>

Actually, an additional question on number 4.

The client already has a number of users on their CMS, and so want to minimise disruption to them. By converting to SSO, will they use the same logins? Or will they have to re-register?

---

<div class="post-metadata">

**Author:** ![Bortami](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/bortami/32/221350_2.png) [@Bortami](https://community.hubspot.com/u/Bortami)\
**Post date:** [July 3, 2024, 6:08pm UTC](https://community.hubspot.com/t/api-confirmation/110564/4 "2024-07-03T18:08:12Z")

</div>

If you require SSO for a subdomain that already hosts private content with member registration, that content will no longer be accessible to registered contacts. ([more docs](https://knowledge.hubspot.com/website-pages/set-up-single-sign-on-sso-to-access-private-content#before-you-get-started)) So, yes, they’ll have to be re-registered.

Implementing SSO is a bit of a conversation and entirely depends on your use case for the private content. I have not found it good for private content for the public, but it is good for organizations that have internal or network based membership needs.

---

<div class="post-metadata">

**Author:** ![MrNiamh](https://avatars.discourse-cdn.com/v4/letter/m/f19dbf/32.png) [@MrNiamh](https://community.hubspot.com/u/MrNiamh)\
**Post date:** [July 3, 2024, 6:19pm UTC](https://community.hubspot.com/t/api-confirmation/110564/5 "2024-07-03T18:19:00Z")

</div>

Thanks for the response - I think I am still a bit unsure (and actually just posted [another question](https://community.hubspot.com/t5/CMS-Development/Using-SSO-for-CMS-and-custom-backend/td-p/1000732) with a bit more detail)!

The private content (and therefore logins) are for members of the network, correct. We would be moving everyone to SSO if we did this.

I think it might actually be easier to explain this over call, so I’ve booked in some time with you if that’s okay!

---

<div class="post-metadata">

**Author:** ![MrNiamh](https://avatars.discourse-cdn.com/v4/letter/m/f19dbf/32.png) [@MrNiamh](https://community.hubspot.com/u/MrNiamh)\
**Post date:** [July 3, 2024, 3:43pm UTC](https://community.hubspot.com/t/api-confirmation/110564/6 "2024-07-03T15:43:03Z")

</div>

Thanks for your help @Bortami !
