hubapi.com – crm
Allows an app to extend the CRM UI by surfacing custom cards in the sidebar of record pages. These cards are defined up-front as part of app configuration, then populated by external data fetch requests when the record page is accessed by a user.
- Homepage
- https://api.apis.guru/v2/specs/hubapi.com:crm/v3.json
- Provider
- hubapi.com:crm / crm
- OpenAPI version
- 3.0.1
- Spec (JSON)
- https://api.apis.guru/v2/specs/hubapi.com/crm/v3/openapi.json
- Spec (YAML)
- https://api.apis.guru/v2/specs/hubapi.com/crm/v3/openapi.yaml
Tools (8)
Extracted live via the executor SDK.
-
cards.deleteCrmV3ExtensionsCardsAppIdCardIdArchivePermanently deletes a card definition with the given ID. Once deleted, data fetch requests for this card will no longer be sent to your service. This can't be undone.
-
cards.getCrmV3ExtensionsCardsAppIdCardIdGetByIdReturns the definition for a card with the given ID.
-
cards.getCrmV3ExtensionsCardsAppIdGetAllReturns a list of cards for a given app.
-
cards.patchCrmV3ExtensionsCardsAppIdCardIdUpdateUpdate a card definition with new details.
-
cards.postCrmV3ExtensionsCardsAppIdCreateDefines a new card that will become active on an account when this app is installed.
-
sampleResponse.getCrmV3ExtensionsCardsSampleResponseGetCardsSampleResponseReturns an example card detail response. This is the payload with displayed details for a card that will be shown to a user. An app should send this in response to the data fetch request.
-
openapi.previewSpecPreview an OpenAPI document before adding it as a source
-
openapi.addSourceAdd an OpenAPI source and register its operations as tools