Dev Portal Deprecated on Monday. (08/12/22)

Key Facts:

  • API Central developer portal to be read-only starting Monday, 08/15, at 9 AM PT
  • New developer portal and API gateway to be available for testing starting Tuesday, 08/16
  • Extra support channels to be available

Current developer portal deprecated

This is to remind you that on Monday morning at 9:00 am the current “API Central” developer portal at will be deprecated and switched to “read-only” mode. You can continue to rely on it for information about your current access credentials and interactive docs for Berkeley APIs, but you won’t be able to make any changes or initiate requests there.

(We should note that the current API gateway at, while also deprecated, will continue to be supported and function as it currently does throughout the three month transition period. New APIs or contract breaking changes will be implemented on the new platform.)

Data transfer and final testing

Throughout Monday and into the wee hours Tuesday morning, we’ll be busy transferring all API management information from the current platform to the new AWS one, then thoroughly testing all functions.

Our A/B performance and load testing thus far has shown that the AWS platform is much more consistent and better able to handle spikes in demand. We’re also A/B testing every idempotent API call in all available formats with every active credential set to ensure no unexpected glitches during your transition (this has also served as a great soak test).

New portal and gateway released for your testing

On Tuesday morning, once we’re able to verify that all of our tests have been successful, we’ll send you the URLs for the new developer portal and API gateway and you can begin kicking their tires and such.

We’ve intentionally chosen to release these at the beginning of the campus wide “no-fly” zone to allow you a few weeks to implement use of the new platform in your test environments, and we urge you to take advantage of this. While we have a comprehensive test suite, we simply cannot even conceive of all of the http client libraries you all are using, nor all of the myriad ways you’ve been calling the APIs. Especially if you’re using older versions of software or making complex or long-running calls, you need to do your own thorough testing before moving your production clients over to the AWS platform.

New portal and gateway released for testing

We’re committed to making this transition as easy as possible for each of you individually and for the campus as a whole. In addition to our support email (, we’ll also be available via a new Slack channel in the Berkeley IT workspace, “# api-transition-help,” and will offer “open office hours” via Zoom on Friday mornings at 9-10 am (through at least September 9).

Please let us know how it’s going–we look forward to your feedback!

Stay tuned for more information, and as always, if you have any questions, please reach out to us at or # api-transition-help on Slack.