Home → Questions →

Semantics of createdBeforeDate and createdAfterDate

• Edit

Dan Kamins

08 Jun, 2010 04:17 AM

Please explain the semantics of createdBeforeDate and createdAfterDate as used in the API request:
https://cheddargetter.com/developers#all-customers

1. Do they only accept YYYY-MM-DD? Or are times allowed too (ISO8601?)?

2. Is the query interpreted as (>= createdAfterDate) and (<= createdBeforeDate)? If I provide the same date for each, it includes everything from that day, so that's what it seems like.

3. What TZ is being used?

4. If a user signed up on Monday and then changed plans on Friday, were they "created" Monday or Friday?

Thank you.

1. Support Staff 1 Posted by Marc Guyer on 08 Jun, 2010 02:03 PM

   

   Oops. I could have sworn there was more detail in the docs. We've just added some (excerpt follows).

   As in all date and time related operations, the timezone used is the timezone set for the authenticated user. Dates are inclusive. e.g. assuming timezone for the authenticated user is set to UTC, 2010-07-04 <= X <= 2010-08-04 is interpreted as 2010-07-04T00:00:00+00:00 <= X <= 2010-08-04T23:59:59+00:00.

   The API only accepts whole dates.

   A customer's createdDatetime will never change. A customer's createdDatetime and the createdDatetime of the customer's first subscription will be the same moment. If the customer changes plans, there will be a new subscription record (with a new createdDatetime).
   

   • Edit

2. Marc Guyer closed this discussion on 08 Jun, 2010 02:03 PM.

3. Dan Kamins re-opened this discussion on 08 Jun, 2010 05:55 PM

4. 2 Posted by Dan Kamins on 08 Jun, 2010 05:55 PM

   

   Great, thank you for the clarification.

   Related: Is there any way to query for customers who changed plans within a date range?

   • Edit

5. Support Staff 3 Posted by Marc Guyer on 08 Jun, 2010 06:02 PM

   

   Hmm... No, there isn't.

   • Edit

6. Marc Guyer closed this discussion on 08 Jun, 2010 06:02 PM.