Why use the Settings API over a new administration menu?

Question

I'm writing a 'quote-me' plugin which provides the end-user with a quote based on data they submit through a front-end form. The quote is calculated according to a price list. The price list varies depending on the time of year so I need a way of letting the admin-user update the prices via the back-end dashboard.

My first thought was to use the Settings API but have since seen administration menus can be created.

Considering my objective above, should I create a new admin menu or should I use the Settings API? Which is more appropriate for my use case and why?

Hoping someone can explain. Thanks in advance.

UPDATE:

My confusion came from my assumption that the Settings API is to be used for just the Settings administration menu. But now I know the Settings API can be used across the whole set of administration menus, including new ones I create.

Thanks for your answers and comments!

Answer 1

The two are not the same thing at all, and likely you'll use both.

The Administration Menu stuff shows you how to create the menu item and page for your settings to live on. In other words, the menu item in the left hand bar, and the existence of the page itself.

The Settings API is what you use to actually build the contents of that page (the table of settings, form fields, and submit button), and to then process the data coming back from it.