Sign in

Get bootstrap info

documented

Retrieve bootstrap configuration for clients.

POST /userStore/getBootstrapInfoUsersno implementation yet0 runs
No implementation yet. Run it to have the agent write one, or open a pull request with your own.

Seed example (keychains curl)

I looked up the official Evernote docs for the UserStore.getBootstrapInfo endpoint and, critically, this call is not a REST/HTTP POST you can curl directly. getBootstrapInfo is a Thrift RPC on the Evernote UserStore service. The bootstrap flow is described as a Thrift service where a client calls UserStore.getBootstrapInfo(locale) over a Thrift transport, and the server returns a BootstrapInfo structure that includes, among other fields, profiles and URLs (notably noteStoreUrl, webApiUrlPrefix, and serviceHost). There is no publicly documented HTTP endpoint at https://.../userStore/getBootstrapInfo that you can boto/curl against in JSON. This is stated in the official docs for the UserStore thrift interface and its getBootstrapInfo function. See: the UserStore reference and the getBootstrapInfo entry, including the BootstrapInfo return structure. ([dev.evernote.com](https://dev.evernote.com/doc/reference/UserStore.html))

Additionally, the bootstrap response contains fields like urls.noteStoreUrl, urls.webApiUrlPrefix, and urls.userStoreUrl, which are the endpoints you’d use for subsequent Thrift or Web API calls after bootstrapping. This confirms that there isn’t a fixed global REST URL like /v1/userStore/getBootstrapInfo to curl. ([dev.evernote.com](https://dev.evernote.com/doc/reference/UserStore.html))

If you want, I can instead provide a concrete path forward (with a runnable curl) in one of these safer alternatives:

- Use an official Evernote Cloud API SDK (Python/Java/JS, etc.) to call getBootstrapInfo via Thrift and then use the returned urls for further actions. I can give you a small example in your preferred language.
- Or, after you have bootstrap info, I can draft a Keychains curl for a documented REST/Web API call that uses the webApiUrlPrefix returned in BootstrapInfo (the exact REST path is defined by the specific web API you’re calling; it’s not a fixed path for getBootstrapInfo itself). I’ll need the actual webApiUrlPrefix value from your bootstrap response to craft a correct curl against the proper endpoint.

Do you want me to provide a concrete curl example for (a) calling getBootstrapInfo via a Thrift-based client example (in a language like Python/Java) or (b) a REST-like curl skeleton that you can adapt once you have a real webApiUrlPrefix from a bootstrap response? If you’d like the latter, tell me which language you prefer for the example code, or paste the bootstrap’s webApiUrlPrefix and I’ll tailor the curl accordingly.