Google Keep API
The Google Keep API is used in an enterprise environment to manage Google Keep content and resolve issues identified by cloud security software.
Productivity & workspace#openapi#analytics#media
Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.
Overview
The Google Keep API is used in an enterprise environment to manage Google Keep content and resolve issues identified by cloud security software.
Endpoints 6
notes
- GETGets a note.
/v1/:nameGets a note. - DELETEDeletes a note
/v1/:nameDeletes a note. Caller must have the OWNER role on the note to delete. Deleting a note removes the resource immediately and cannot be undone. Any… - GETLists notes
/v1/notes?filter=string&pageSize=0&pageToken=stringLists notes. Every list call returns a page of results with page_size as the upper bound of returned items. A page_size of zero allows the server to choose… - POSTCreates a new note.
/v1/notesCreates a new note.
notes.permissions
- POSTCreates one or more permissions on the note
/v1/:parent/permissions:batchCreateCreates one or more permissions on the note. Only permissions with the WRITER role may be created. If adding any permission fails, then the entire request… - POSTDeletes one or more permissions on the note
/v1/:parent/permissions:batchDeleteDeletes one or more permissions on the note. The specified entities will immediately lose access. A permission with the OWNER role can't be removed. If…
API details
- Base URL
https://keep.googleapis.com- Authentication
- OAuth 2.0 (authorization code flow) with 2 scopes
An API key in the key query parameter - Operations
- 6 operations on 4 pathsPOST 3GET 2DELETE 1
- Main resources
- notes 4notes.permissions 2
- Response formats
application/json- Description format
- Google API Discovery, API version
v1 - Links
- Documentation · OpenAPI document
- Listed from
- Google API Discovery document (googleapis/discovery-artifact-manager) (Apache-2.0)
How to test the Google Keep API in Swastik Codes
- Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
- Fork it into your workspaceChoose a workspace. You get your own copy of the Google Keep API collection, without the publisher's secrets.
- Add your credentialsThis API uses OAuth 2.0 (authorization code flow) with 2 scopes. Add yours in the collection's variables or an environment; the requests already reference it.
- Send a requestPick an endpoint, for example “Gets a note.” (GET /v1/:name), and press Send. Check the response, add tests and run the whole collection with the runner.
Frequently asked questions
What is the Google Keep API?
The Google Keep API is used in an enterprise environment to manage Google Keep content and resolve issues identified by cloud security software. It is listed under Productivity & workspace and has 6 endpoints.
Who publishes the Google Keep API?
It is listed from Google's public API description (an OpenAPI document), not published by Google on Swastik Codes. Anyone who controls googleapis.com can claim the profile by adding a DNS TXT record.
What is the base URL of the Google Keep API?
Requests go to https://keep.googleapis.com. Endpoint paths are added to this base URL.
How do I authenticate with the Google Keep API?
It accepts 2 methods: OAuth 2.0 (authorization code flow) with 2 scopes; an API key in the key query parameter.
How many endpoints does the Google Keep API have?
6 operations on 4 paths (3 POST, 2 GET, 1 DELETE). The largest groups are notes, notes.permissions.
Is forking the Google Keep API free?
Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.