System Status Monitor

We use UptimeRobot to monitor the API's availability. Its public page shows current status and history.

Monitored around the clock by UptimeRobot
Open Status Page

Opens the status page hosted by UptimeRobot in a new tab.

What is monitored

The status page runs HTTP(s) checks on both parts of the service:

  • api.tikliveapi.com - the API itself. Every request goes to the base URL https://api.tikliveapi.com, so this is the monitor to look at when calls fail.
  • www.tikliveapi.com - this website, which serves the documentation, the playground and your account dashboard.

Open it for the live state of each monitor, its day-by-day uptime history and the latest recorded downtime.

If your requests fail

Start with the status page. If api.tikliveapi.com is up there, work through these checks:

  1. Read the response body. When a request cannot be served, the API returns a JSON object with a message field instead of the endpoint's data. The missing-key and invalid-key messages below come back with HTTP status 200, so check the body, not only the status code.
  2. Send your key in the X-Api-Key header. Without it the API answers {"message": "Please sign up to tikliveapi.com"}.
  3. Use your current key. {"message": "Api-Key is not available"} means the key is not valid. A regenerated key replaces the old one at once, so copy your current key from the Dashboard tab of your profile.
  4. Check your credits. Each successful request costs 1 credit, and credits never expire. Your balance is on the same Dashboard tab, and Pricing lists the credit packages.
  5. Stay within the rate limit. The standard limit is 200 requests per minute per API key; contact us to raise it.
  6. Compare with the documentation. Each endpoint page in the documentation lists its required parameters and an example request you can try in the playground.

Still failing? Contact support with the endpoint, the parameters you sent and the time of the failed request.