Introduction

Calling conventions

The Web API consist of HTTP request-response methods, all of form https://api.taggun.io/api/{group}/v1/{method}

All methods are implemented in synchronous fashion which holds the connection open until the response is delivered or the timeout period expires. There are no webhooks or deferred callback mechanism.

All response contains JSON object and header with content-type: application/json; charset=utf-8

All API requests must be made over HTTPS.

Authentication

Authenticate your account with your request by including apikey in the request header.

You can request for an API key by sending an email to ck-lee@taggun.io

Keep your API keys secret. Do not distribute your API key in native applications, client-side JavaScript, or public code repositories.

See here for code examples

Admin

Taggun uses Slack bot for any admin purposes. See how Marvin can assist you with any administrative tasks.

High availability cluster

There are 2 data centers hosted on AWS, located in US West (Northern California) and Asia Pacific (Sydney) regions. They perform the same functions and act as a high-availability cluster with active/active node configuration.

Latency based routing

DNS queries of api.taggun.io will respond with the IP Address of the resource that provides the best latency. For example: If latency is lowest between the caller and Sydney data center, the DNS query of api.taggun.io will resolve to the IP Address of Sydney data center.

You can also specify the target data center locations. This is useful if your application needs to comply with data sovereignty regulation. Use these data center specific host names:

api-au.taggun.io will resolve to the IP Address of Sydney data center in Australia

api-us.taggun.io will resolve to the IP Address of Northern California data center in North America.

Staging Environment

The staging environment is ASAP as similar as production and is hosted on the same production kit

Staging environment is used for development and testing purposes only. Not for production use.

Any release will be deployed to staging environment prior to production environment.

Use these hostnames for staging environment:

api-s.taggun.io will respond to the IP Address of the resource that provides the best latency.

api-au-s.taggun.io will resolve to the IP Address of Sydney data center in Australia

api-us-s.taggun.io will resolve to the IP Address of Northern California data center in North America.

Usage limits

Taggun enforces the following usage limits:

Type of limit Usage limit
MB per request 20mb
Requests per second 5
Requests per minute 300
Requests per hour 2000

results matching ""

    No results matching ""