canonical: https://jentic.com/apis/reviewstudio.com/reviewstudio # ReviewStudio API This document describes the ReviewStudio API and its usage. The headers for all the requests are the following: 
 'X-REVIEWSTUDIO-EMAIL' = Email of the admin. 'X-REVIEWSTUDIO-TOKEN' = API Key.
. The API exposes 128 endpoints. ## For AI agents Programmatically getaccountreviewsettings, putaccountreviewsettings. Covers 128 operations. ## Scope Does not handle payments, crm, or developer tools - use for communications only. ## Capabilities - getAccountReviewSettings - putAccountReviewSettings - getAccountReviewDefaults - putAccountReviewDefaults - postReviews - getReviews ## Use cases ### Communications Operations Use the ReviewStudio API to perform communications operations programmatically. The API provides 128 endpoints covering core functionality including getaccountreviewsettings, putaccountreviewsettings, getaccountreviewdefaults. Example prompt: Call GET /account/review/settings to getaccountreviewsettings ### Automated Account Management Automate account operations by combining multiple ReviewStudio API endpoints. Agents can putaccountreviewsettings and then getaccountreviewdefaults in a single workflow. Example prompt: Call PUT /account/review/settings to putaccountreviewsettings, then verify the result ### AI Agent Integration via Jentic AI agents discover and call ReviewStudio API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually. Example prompt: Search Jentic for 'getaccountreviewsettings', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /account/review/settings | getAccountReviewSettings | | PUT | /account/review/settings | putAccountReviewSettings | | GET | /account/review/defaults | getAccountReviewDefaults | | PUT | /account/review/defaults | putAccountReviewDefaults | | POST | /reviews | postReviews | | GET | /reviews | getReviews | | GET | /reviews/{id} | getReviewsId | | PUT | /reviews/{id} | putReviewsId | ## Key resources - **Account** — Operations for account - **Clients** — Operations for clients - **Labels** — Operations for labels - **My** — Operations for my - **Profile** — Operations for profile ## Why Jentic - **Setup:** Wiring the ReviewStudio API by hand means setting its X-REVIEWSTUDIO-EMAIL and X-REVIEWSTUDIO-TOKEN headers on every call to app.reviewstudio.com and handling retries yourself. Through Jentic you install once, import the ReviewStudio API from the API Directory, store those credentials once, and your agent calls it. - **Permission scoping:** ReviewStudio puts the review id in the URL path (/reviews/{id}), so a rule can pin your agent to one review: it can read that review and nothing else. You choose the operations it may call, so ones like updating a review or changing account settings are not included unless you add them. - **Credential handling:** Your ReviewStudio email and token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'read account review settings' or 'create a review', and Jentic returns the matching ReviewStudio API operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Twilio** — Alternative communications API - **Sendgrid** — Alternative communications API - **Pusher** — Complementary communications API ## FAQ ### What authentication does the ReviewStudio API use? The ReviewStudio API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context. ### Can I getaccountreviewsettings with the ReviewStudio API? Yes. Use the GET /account/review/settings endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the ReviewStudio API? Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer. ### How do I getaccountreviewsettings through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'getaccountreviewsettings'. Jentic returns the matching ReviewStudio API operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the ReviewStudio API have? The ReviewStudio API exposes 128 endpoints covering account, clients, labels operations. ### Can I limit what my agent is allowed to do with the ReviewStudio API? Yes. Jentic One is self-hosted by you, so your own rules decide which ReviewStudio operations and credentials the agent may use. Because ReviewStudio puts the review id in the URL path, such as GET /reviews/{id}, you can pin the agent to reading a single review and nothing else. You choose the operations it may call, so write actions like PUT /reviews/{id} or PUT /account/review/settings are excluded unless you add them.