Updated docs.

djstripe/management/commands/djstripe_sync_models.py

@@ -22,6 +22,13 @@
 
  7) To only sync Stripe Accounts and Charges for sk_test_XXX and sk_test_YYY API keys:
  python manage.py djstripe_sync_models Account Charge --api-keys sk_test_XXX sk_test_YYY
+
+ 6) To only sync Stripe Accounts for sk_test_XXX and sk_test_YYY API keys for objects created after {unix_timestamp}:
+ python manage.py djstripe_sync_models Account --api-keys sk_test_XXX sk_test_YYY --created "{\"gt\": {unix_timestamp}}"
+
+ 7) To only sync Stripe Accounts and Charges for sk_test_XXX and sk_test_YYY API keys for objects created between {unix_gt_timestamp} and {unix_lt_timestamp}:
+ python manage.py djstripe_sync_models Account Charge --api-keys sk_test_XXX sk_test_YYY --created "{\"gte\": {unix_gt_timestamp}, \"lte\": {unix_lt_timestamp}}"
+
 """
 import json
 from typing import Dict, List, Union

docs/usage/manually_syncing_with_stripe.md

@@ -27,6 +27,12 @@ A list of models to sync can also be provided along with the API Keys.
 ```
 This will sync all the Invoice and Subscription data for the given API Keys. Please note that the API Keys sk_test_YYY and sk_test_XXX need to be in the database.
 
+An Optional Kwarg `created` can be added to restrict syncing objects created between a certain timeperiod as mentioned in the [Stripe docs.](https://stripe.com/docs/api/customers/list#list_customers-created). Please note that the `created` kwarg is not supported by all Stripe models and we silently ignore it is the model being synced does not support it.
+
+```bash
+ ./manage.py djstripe_sync_models Invoice Subscription --api-keys sk_test_XXX sk_test_YYY --created "{\"gte\": {unix_gt_timestamp}, \"lte\": {unix_lt_timestamp}}"
+```
+
 You can manually reprocess events using the management commands
 [`djstripe_process_events`][djstripe.management.commands.djstripe_process_events]. By default this processes all events, but
 options can be passed to limit the events processed. Note the Stripe API