It’s less processing and bandwidth intensive than technologies like SOAP and more organized than GraphQL. Secure and fast. Just the way you want to run your tests.
We use the Hash-based message authorization code (HMAC). When you send HTTPS requests to Convert, you sign the requests so that Convert can identify who sent them. Every request contains Signature, calculated with the help of a Secret Key, Request URL, Request payload, Request Expiration time.
Changes to request value affect the signature. And the connection attempt isn’t authorized.
Between the requests you can send to our server, and the core data models they interact with, you can bring all the features and functionalities of the Convert Experiences appanywhere you want.
Add users, start projects, remove goals, create a hypothesis and sort experiments with tags.
The potential is literally unlimited.
1. If you are on an Expert or Enterprise plan, you can use the API right away.
2. If you are on the Growth plan, consider upgrading to Expert or Enterprise for immediate API access.
3. Once you’re in the Developer account and have clicked the API Keys tab, generate a “New API Key”. See the screenshot below.
4. You’ll receive a fresh token for each application you connect to. Read more about our API authentication.