# RenewalInfo endpoint **URL:** \ **Category:** Client dev\ **Created:** [December 27, 2023, 1:19pm UTC](https://community.letsencrypt.org/t/renewalinfo-endpoint/210765 "2023-12-27T13:19:43Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![petercooperjr](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/petercooperjr/32/84698_2.png) [@petercooperjr](https://community.letsencrypt.org/u/petercooperjr)\ **Post date:** [December 27, 2023, 1:33pm UTC](https://community.letsencrypt.org/t/renewalinfo-endpoint/210765/3 "2023-12-27T13:33:12Z")
This is a draft called ACME Renewal Information (ARI) that's being tested with suggestions from the server on when a client should renew. It's particularly useful for when the CA needs to revoke a certificate without the subscriber's approval (due to some sort of misissuance event) and so the client can check and find out that it needs to renew early. (It could also help the CA spread out load or deal with scheduled downtime.) It's still a draft, and the current implementation is in part to be able to get feedback before getting finalized. (And I gave [quite a bit of feedback myself earlier this year](https://community.letsencrypt.org/t/thoughts-from-starting-to-play-with-ari/200276).) What's currently implemented is [draft-01](https://datatracker.ietf.org/doc/draft-ietf-acme-ari/01/), though it looks like [there's a draft-02 now](https://datatracker.ietf.org/doc/draft-ietf-acme-ari/02/) (which I hadn't seen before) which on first glance may be addressing some of my (and others') concerns. If you want to implement it in order to try it out and maybe even give some feedback then you're certainly welcome to. But just be aware that as it's still a draft things are likely to continue to change. --- _[View the full topic](https://community.letsencrypt.org/t/renewalinfo-endpoint/210765)._