Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Di sebagian besar halaman dokumentasi, API Explorer ringkas terlihat di sisi kanan layar. Jika APIs Explorer tidak terlihat, klik
Try it! untuk menampilkan versi ringkas APIs Explorer.
Jika Coba! tidak muncul di sisi kanan halaman dokumentasi referensi, berarti metode tersebut tidak didukung oleh APIs Explorer. Misalnya, API Explorer tidak kompatibel dengan API yang memerlukan akun layanan, sehingga tidak muncul di halaman dokumentasi untuk API tersebut.
Menampilkan versi yang diperluas dari APIs Explorer
Versi yang diperluas dari APIs Explorer berisi cURL, HTTP, dan mungkin
contoh kode lainnya. Untuk menampilkan versi APIs Explorer yang diperluas, klik Layar penuh fullscreen.
Menjalankan metode
APIs Explorer memungkinkan Anda memasukkan parameter wajib, parameter opsional, dan, jika berlaku, isi permintaan untuk metode API. Untuk banyak metode REST, seperti metode daftar, Anda hanya perlu mengisi satu atau dua kolom sebelum dapat mengeksekusi metode. Misalnya, metode
books.volumes.list
Books API hanya memerlukan parameter kueri (q) untuk mencantumkan buku. Untuk mencoba metode
books.volumes.list:
Jika APIs Explorer tidak ditampilkan, klik Try it!
Di kolom q, ketik Hunger Games (tanpa tanda kutip atau karakter khusus).
Scroll ke bawah, lalu klik Jalankan.
(opsional) Layar login Google meminta Anda memilih Akun Google.
(opsional) Dialog otorisasi Google akan menanyakan apakah Anda mengizinkan
"Mengelola buku Anda". Klik Izinkan. Hasilnya akan muncul di bawah tombol Jalankan.
Jika APIs Explorer menampilkan hasil 200, berarti metode berhasil.
Memecahkan masalah APIs Explorer
Anda menerima error 401 atau 403
Jika Anda mendapatkan error 401 atau 403 saat menjalankan metode menggunakan API Explorer, kemungkinan hal ini disebabkan oleh masalah pada salah satu hal berikut:
Anda menggunakan jenis otorisasi yang salah (kunci API, bukan OAuth 2.0).
Coba alihkan jenis otorisasi.
Anda menggunakan OAuth 2.0, tetapi dengan cakupan yang terlalu sempit. Coba gunakan cakupan yang lebih luas.
Dialog otorisasi tidak muncul
Penjelajah API menggunakan pop-up untuk memberikan akses ke data pribadi Anda. Jika browser Anda memblokir pop-up, pop-up ini tidak akan muncul dan Anda tidak akan dapat memberikan akses.
Jika Anda mengklik Izinkan di dialog otorisasi dan tidak terjadi apa pun, coba ubah setelan pop-up browser Anda untuk mengaktifkan pop-up.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Informasi yang saya butuhkan tidak ada","missingTheInformationINeed","thumb-down"],["Terlalu rumit/langkahnya terlalu banyak","tooComplicatedTooManySteps","thumb-down"],["Sudah usang","outOfDate","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Masalah kode / contoh","samplesCodeIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-07-26 UTC."],[[["\u003cp\u003eThe APIs Explorer allows you to test API methods directly in the documentation by providing parameters and executing requests.\u003c/p\u003e\n"],["\u003cp\u003eTo use the APIs Explorer with methods requiring authorization, you need to generate and use your own credentials.\u003c/p\u003e\n"],["\u003cp\u003eThe expanded APIs Explorer provides code samples in various formats like cURL and HTTP for easier integration.\u003c/p\u003e\n"],["\u003cp\u003eIf you encounter a 401 or 403 error, verify the authorization type and scope, as they are the most common causes.\u003c/p\u003e\n"],["\u003cp\u003eThe APIs Explorer uses popups for authorization, so ensure your browser settings allow them to function correctly.\u003c/p\u003e\n"]]],[],null,["# Display the APIs Explorer and execute a method\n\nOn most documentation pages, a condensed APIs Explorer is visible on the\nright-hand side of the screen. If the APIs Explorer isn't visible, click\n**Try it!** to display the condensed version of the APIs Explorer.\n\nIf **Try it!** doesn't appear on the right-hand side of a reference\ndocumentation page, the method isn't supported by the APIs Explorer. For\nexample, the APIs Explorer isn't compatible with APIs that require service\naccounts, so it doesn't appear on documentation pages for those APIs.\n\nDisplay the expanded version of the APIs Explorer\n-------------------------------------------------\n\nThe expanded version of the APIs Explorer contains cURL, HTTP, and possibly\nother code samples. To display the expanded version of the APIs Explorer,\nclick Full screen fullscreen.\n| **Note:** To run the code samples, you must generate and use your own authorization credentials. For an explanation of how to create a project and generate credentials, refer to your specific Google API's documentation.\n\nExecute a method\n----------------\n\nThe APIs Explorer lets you enter required parameters, optional parameters,\nand, if applicable, a request body for API methods. For many REST methods,\nsuch as list methods, you only need to fill one or two fields before you can\nexecute the method. For example, the Books API's\n[`books.volumes.list`](/books/docs/v1/reference/volumes/list)\nmethod only requires a query parameter (`q`) to list books. To try the\n[`books.volumes.list`](/books/docs/v1/reference/volumes/list)\nmethod:\n\n1. Navigate to [`books.volumes.list`](/books/docs/v1/reference/volumes/list).\n2. If the APIs Explorer isn't displayed, click **Try it!**\n3. In the **`q`** field, type *Hunger Games* (without any quotes or special characters).\n4. Scroll down and click **Execute**.\n5. (optional) A Google sign-in screen asks you to select a Google account.\n6. (optional) A Google authorization dialog asks you if it's okay to \"Manage your books.\" Click *Allow*. The results appear below the Execute button.\n\nIf the APIs Explorer shows a result of 200, then the method was successful.\n| **Note:** After you allow the authorization screen to make an authorized request, the APIs Explorer is authorized to make other requests until the credentials expire. Therefore, you don't see the authorization screen for every subsequent method call. For further information on credentials, see [Test with different credential types and scopes](/explorer-help/authorization-and-authentication).\n\nTroubleshoot APIs Explorer issues\n---------------------------------\n\n### You received a 401 or 403 error\n\nIf you're getting a 401 or 403 error when executing a method using the APIs\nExplorer, it is likely due to a problem with one of the following:\n\n- You're using the wrong authorization type (API key instead of OAuth 2.0). Try switching the authorization type.\n- You're using OAuth 2.0, but with too narrow a scope. Try using a broader scope.\n\n### Authorization dialog doesn't appear\n\nThe APIs Explorer uses a popup to grant access to your private data. If your\nbrowser blocks popups, this popup won't appear and you won't be able to grant\naccess.\n\nIf you click **Allow** in the authorization dialog and nothing happens, try\nchanging your browser's popup settings to enable popups."]]
