Open API (311/Geocoding) update
0 views
Skip to first unread message
Dmitry Kachaev
Jun 28, 2009, 2:17:22 PM6/28/09
to OCTO Labs (DC Government)
Just want to give some update on state of API.
We fixed a number of bugs and added some exception handling (will be
improved further with meaningful error codes in JSON format)
Open 311 API "submit" method will be integrated with backend (either
production or QC environment) and available for developers (ETA:
Monday noon/EOB).
I highly encourage to start using API keys for all you calls. We would
like to start enforcing it on Monday for v1 of API, so we don't have
any surprises on July 1st (Let me know if you want to delay that).
Details here http://octolabs.pbworks.com/About-Open-API-Keys
We didn't incorporated concerns on "not so perfect" JSON structure in
method responses in v1. It will be built into v2 of API (see docs
already available here http://octolabs.pbworks.com/Open-API-Documentation,
and please provide your suggestions if needed)
We can conduct another conf call for developers on Monday evening, let
us know if needed.
-Dmitry
We fixed a number of bugs and added some exception handling (will be
improved further with meaningful error codes in JSON format)
Open 311 API "submit" method will be integrated with backend (either
production or QC environment) and available for developers (ETA:
Monday noon/EOB).
I highly encourage to start using API keys for all you calls. We would
like to start enforcing it on Monday for v1 of API, so we don't have
any surprises on July 1st (Let me know if you want to delay that).
Details here http://octolabs.pbworks.com/About-Open-API-Keys
We didn't incorporated concerns on "not so perfect" JSON structure in
method responses in v1. It will be built into v2 of API (see docs
already available here http://octolabs.pbworks.com/Open-API-Documentation,
and please provide your suggestions if needed)
We can conduct another conf call for developers on Monday evening, let
us know if needed.
-Dmitry
Shaun Farrell
Jun 29, 2009, 1:07:32 PM6/29/09
to OCTO Labs (DC Government)
Are we looking at more EOB for the integration updates?
4pm 5pm?
On Jun 28, 2:17 pm, Dmitry Kachaev <dmitry.kach...@gmail.com> wrote:
> Just want to give some update on state of API.
>
> We fixed a number of bugs and added some exception handling (will be
> improved further with meaningful error codes in JSON format)
>
> Open 311 API "submit" method will be integrated with backend (either
> production or QC environment) and available for developers (ETA:
> Monday noon/EOB).
>
> I highly encourage to start using API keys for all you calls. We would
> like to start enforcing it on Monday for v1 of API, so we don't have
> any surprises on July 1st (Let me know if you want to delay that).
> Details herehttp://octolabs.pbworks.com/About-Open-API-Keys
4pm 5pm?
On Jun 28, 2:17 pm, Dmitry Kachaev <dmitry.kach...@gmail.com> wrote:
> Just want to give some update on state of API.
>
> We fixed a number of bugs and added some exception handling (will be
> improved further with meaningful error codes in JSON format)
>
> Open 311 API "submit" method will be integrated with backend (either
> production or QC environment) and available for developers (ETA:
> Monday noon/EOB).
>
> I highly encourage to start using API keys for all you calls. We would
> like to start enforcing it on Monday for v1 of API, so we don't have
> any surprises on July 1st (Let me know if you want to delay that).
>
> We didn't incorporated concerns on "not so perfect" JSON structure in
> method responses in v1. It will be built into v2 of API (see docs
> already available herehttp://octolabs.pbworks.com/Open-API-Documentation,
> We didn't incorporated concerns on "not so perfect" JSON structure in
> method responses in v1. It will be built into v2 of API (see docs
Shaun Farrell
Jun 29, 2009, 1:07:42 PM6/29/09
to OCTO Labs (DC Government)
Are we looking at more EOB for the integration updates?
4pm 5pm?
On Jun 28, 2:17 pm, Dmitry Kachaev <dmitry.kach...@gmail.com> wrote:
4pm 5pm?
On Jun 28, 2:17 pm, Dmitry Kachaev <dmitry.kach...@gmail.com> wrote:
> Just want to give some update on state of API.
>
> We fixed a number of bugs and added some exception handling (will be
> improved further with meaningful error codes in JSON format)
>
> Open 311 API "submit" method will be integrated with backend (either
> production or QC environment) and available for developers (ETA:
> Monday noon/EOB).
>
> I highly encourage to start using API keys for all you calls. We would
> like to start enforcing it on Monday for v1 of API, so we don't have
> any surprises on July 1st (Let me know if you want to delay that).
> Details herehttp://octolabs.pbworks.com/About-Open-API-Keys
>
> We fixed a number of bugs and added some exception handling (will be
> improved further with meaningful error codes in JSON format)
>
> Open 311 API "submit" method will be integrated with backend (either
> production or QC environment) and available for developers (ETA:
> Monday noon/EOB).
>
> I highly encourage to start using API keys for all you calls. We would
> like to start enforcing it on Monday for v1 of API, so we don't have
> any surprises on July 1st (Let me know if you want to delay that).
>
> We didn't incorporated concerns on "not so perfect" JSON structure in
> method responses in v1. It will be built into v2 of API (see docs
> already available herehttp://octolabs.pbworks.com/Open-API-Documentation,
> We didn't incorporated concerns on "not so perfect" JSON structure in
> method responses in v1. It will be built into v2 of API (see docs
Dmitry Kachaev (OCTO)
Jun 29, 2009, 1:09:27 PM6/29/09
to OCTO...@googlegroups.com
Yes. I looks more like 6pm.
-Dmitry
Dmitry Kachaev, Director of R&D
Office of the CTO, DC Government
voice: (202) 527-9423
mail: dmitry....@dc.gov
location: One Judiciary Square, 1010S
schedule: http://links.dc.gov/dk-freebusy
Office of the CTO, DC Government
voice: (202) 527-9423
mail: dmitry....@dc.gov
location: One Judiciary Square, 1010S
schedule: http://links.dc.gov/dk-freebusy
Reply all
Reply to author
Forward
0 new messages