code: 
  '''Response {
    "object": "list",
    "url": "/v1/customers",
    "has_more": false,
    "data": [
      {
        "id": "cus_8TEMHVY5moxIPI",
        "object": "customer",
        "address": null,
        "balance": 0,
        "created": 1463528816,
        "currency": "usd",
        "default_source": "card_18CHs82eZvKYlo2C9BGk8uHq",
        "delinquent": true,
        "description": "Ava Anderson",
        "discount": null,
        "email": "ava.anderson.22@example.com",
        "invoice_prefix": "F899D8E",
        "invoice_settings": {
          "custom_fields": null,
          "default_payment_method": null,
          "footer": null,
          "rendering_options": null
        },
        "livemode": false,
        "metadata": {},
        "name": null,
        "next_invoice_sequence": 12,
        "phone": null,
        "preferred_locales": [],
        "shipping": null,
        "tax_exempt": "none",
        "test_clock": null
      },
      {...},
      {...}
    ]
  }'''
nl: PaginationAll top-level API resources have support for bulk fetches via "list" API methods. For instance, you can list charges, list customers, and list invoices. These list API methods share a common structure, taking at least these three parameters: limit, starting_after, and ending_before.Stripe's list API methods utilize cursor-based pagination via the starting_after and ending_before parameters. Both parameters take an existing object ID value (see below) and return objects in reverse chronological order. The ending_before parameter returns objects listed before the named object. The starting_after parameter returns objects listed after the named object. These parameters are mutually exclusive -- only one of starting_after orending_before may be used.Our client libraries offer auto-pagination helpers to easily traverse all pages of a list.