Update search

Seed example (keychains curl)

I’m unable to provide a working curl command for POST /noteStore/updateSearch because the Evernote Cloud API uses Thrift (not JSON REST) and the NoteStore URL is user-specific, not a fixed API endpoint. The official Cloud API docs describe NoteStore as a Thrift service (with a NoteStore URL that differs per user) and show updateSearch as a NoteStore method that takes a SavedSearch object and returns an update sequence number. A raw JSON curl against /noteStore/updateSearch will not be compatible with the public API. See the Cloud API core concepts and NoteStore reference for details. ([dev.evernote.com](https://dev.evernote.com/doc/articles/core_concepts.php)) 

If you still want to proceed, here are viable paths:
- Use the official SDK (Python, Java, etc.) to call NoteStore.updateSearch with a SavedSearch object. The SDK handles Thrift transport and token handling. ([dev.evernote.com](https://dev.evernote.com/documentation/cloud/))
- If you insist on a low-level HTTP Thrift call, you must send a Thrift-encoded payload to the user-specific NoteStore URL with the correct OAuth credentials; this is non-trivial to craft by hand and not documented as a JSON REST call. The API docs confirm updateSearch requires a SavedSearch (guid, name, query, scope, etc.) and returns an updateSequenceNum. ([dev.evernote.com](https://dev.evernote.com/doc/reference/NoteStore.html?utm_source=openai))

What would you like to do next?
- I can give you a concrete SDK-based example (Python/Java) showing how to call updateSearch with placeholders for the SavedSearch fields.
- Or I can outline the exact steps to generate a Thrift payload and show a curl skeleton using a hypothetical Thrift payload structure (not JSON) if you have a Thrift-capable transport ready. 

Important context and sources:
- Evernote Cloud API overview and NoteStore usage (two services: UserStore and NoteStore; NoteStore URL is per-user): This is the basis for how calls are made and why a fixed REST endpoint isn’t available. ([dev.evernote.com](https://dev.evernote.com/doc/articles/core_concepts.php))
- NoteStore.updateSearch signature and behavior (takes a SavedSearch and returns an update sequence number): This defines what the request must contain. ([dev.evernote.com](https://dev.evernote.com/doc/reference/NoteStore.html?utm_source=openai))
- SavedSearch type reference and SavedSearch fields (guid, name, query, scope, format, etc.): See the NoteStore reference and SavedSearch types in the official docs. ([dev.evernote.com](https://dev.evernote.com/doc/reference/NoteStore.html))
- Authentication methods for Evernote Cloud API (OAuth and developer tokens) and SDK availability: This informs how you obtain and present credentials. ([dev.evernote.com](https://dev.evernote.com/doc/articles/authentication.php?utm_source=openai))

Note: If you want me to proceed with an SDK-based example or a detailed Thrift-payload outline, tell me your preferred language (Python, Java, etc.) and I’ll tailor the code with placeholders for the SavedSearch fields.