Cynthia AI API

What authentication does the Cynthia AI API use?

Cynthia AI uses HTTP bearer authentication. Clients first call POST /zapier_token_exchange to convert a Zapier OAuth code into a bearer token, then send that token in the Authorization header on subsequent calls. Through Jentic the bearer token is stored in the encrypted vault and never injected into the agent's prompt context.

Can I forward arbitrary review data with the Cynthia AI API?

Yes, the POST /zapier_receive_data endpoint accepts review payloads from a Zapier-triggered source. The schema is shaped around Zapier action handlers, so the most reliable integration path is via a Zap that already maps the source review fields into the expected request body.

What are the rate limits for the Cynthia AI API?

The OpenAPI spec does not declare explicit rate limits. Treat the integration as best-effort and implement retry-with-backoff for non-2xx responses on /zapier_receive_data. Confirm production quotas with Andromeda Intelligence before sending high-volume traffic.

How do I send a review through the Cynthia AI API via Jentic?

Run pip install jentic, then search Jentic for 'forward a review to Cynthia AI'. Jentic returns POST /zapier_receive_data with its input schema, loads the bearer credential from the vault, and executes the call with your review payload.

Do I need to call the token exchange before every Cynthia request?

No. Call POST /zapier_token_exchange once to obtain a bearer token, then reuse it on subsequent /zapier_receive_data calls. Use POST /zapier_test_credentials periodically to confirm the token is still valid before high-volume runs.