Skip to content

API does not accept the date format that it uses to format its own dates #11

Open
@ghidinelli

Description

@ghidinelli

We have a custom field set with a date value. When we access data from the Batchbook API, the date is returned to us like this:

{"id":xxxx,"custom_field_definition_id":34,"custom_field_definition_name":"Do Not Contact Before","datetime_value":"2013-10-07T00:00:00-07:00"}]}

Note the -07:00 GMT offset. However, if we try to simply send this value back, we receive a 422 Unprocessable Entity. Removing the GMT offset such that dates look like this:

{"id":xxxx,"custom_field_definition_id":34,"custom_field_definition_name":"Do Not Contact Before","datetime_value":"2013-10-07T00:00:00"}]}

Works and is accepted. It isn't practical to modify the values in data returned to us by the API in order to send them back to the API. Whatever it spits out, it should also accept.

Please change the API to accept the datetime values with GMT offset.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions