Automate Google Site Verification
HumDay reads Google Site Verification’s own published API description and derives 7 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What Google Site Verification is
Verifies ownership of websites or domains with Google.
API host: www.googleapis.com
What HumDay can do in Google Site Verification
5 documented operations change something in Google Site Verification.
- PATCHModify the list of owners for your website or domain.
/webResource/{id} - PUTModify the list of owners for your website or domain.
/webResource/{id} - POSTGet a verification token for placing on a website or domain.
/token - POSTAttempt verification of a website or domain.
/webResource - DELETERelinquish ownership of a website or domain.
/webResource/{id}
What HumDay can read from Google Site Verification
These are the operations a schedule or a trigger can watch.
- GETGet the list of your verified websites and domains.
/webResource - GETGet the most current data for a website or domain.
/webResource/{id}
How automating Google Site Verification works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live Google Site Verification account.
- Grant access, then go live. You approve the specific Google Site Verification operations it may use — and only those.
Automate Google Site Verification with these
- Gmail79 operations
- Google+9 operations
- Google Abusive Experience Report2 operations
- Google Accelerated Mobile Pages (AMP) URL1 operations
- Google Access Approval7 operations
- Google Access Context Manager9 operations
- Google ACME DNS2 operations
- Google Ad Exchange Buyer38 operations
- Google Ad Exchange Buyer II50 operations
- Google Ad Experience Report2 operations
- Google Admin SDK122 operations
- Google AdMob7 operations
Categories
Questions about Google Site Verification automation
- Can HumDay connect to Google Site Verification?
- Yes. HumDay reads Google Site Verification's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 7 operations are documented.
- Do I need to write code to automate Google Site Verification?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Google Site Verification account.
- What can HumDay do in Google Site Verification?
- 5 of the 7 documented operations change something in Google Site Verification, and 2 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Google Site Verification account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Google Site Verification is held behind that approval.
Where this came from
The operations above are read from a published API description for Google Site Verification at siteverification.googleapis.com/$discovery/rest?version=v1. Descriptions are the provider’s own words, not ours. Last published 2023-04-21.