10to8 / 10to8-enterprise-api-hubspot-demo Goto Github PK

HubSpot have recently renamed their scopes from 'contacts' to 'crm.objects.contacts.write crm.objects.contacts.read', but support the old scopes for older HubSpot accounts.

We have updated the scopes to match the latest ones offered with fresh HubSpot account sign-up.

For simplicity, this demo is handling these asynchronously using multiprocessing
In a production environment, a task queue such as Celery is recommended.

If an unexpected API error occurs whilst syncing a Customer/Contact, we do not update the Sync Status field to indicate that an error had occurred.

(Expected error scenarios are handled and the "Sync Status" is updated where appropriate).

Note: Studying the flask server log would show the error.

10to8 provides a means of intervening if a deletion will result in a customer with future bookings being deleted.
See: https://10to8.com/api/enterprise/v2/#operation/patch-api-enterprise-v2-customer-id

For simplicity this demo is not making use of this mechanism - we've disabled the conflict detection with force=True on the Customer Delete endpoint.

We've not integrated with HubSpot's GDPR endpoints, as they are in Beta and subject to change.
https://developers.hubspot.com/docs/api/crm/contacts

To configure this demo for use, API keys are stored in a config file.
In a production environment, consider using a secure secret management system instead.

For simplicity, this demo does not restrict access to the webhook callback URLs hosted on this flask server.
For a production environment, the following may be worth considering:

• Adding basic authentication to your callback URLs used for your webhooks
• Restricting IP ranges to only the services you're expecting