Integrating with Metricsco
Sending data to Metricsco is easy and familiar for most developers.
The Metricsco API is organized around REST. Our API is designed to have predictable, resource-oriented URLs and to use HTTP response codes to indicate API errors. We use built-in HTTP features, like HTTP authentication and HTTP verbs, which can be understood by off-the-shelf HTTP clients, and we support cross-origin resource sharing to allow you to interact securely with our API from a client-side web application (though you should remember that you should never expose your secret API key in any public website’s client-side code). JSON will be returned in all responses from the API, including errors.
To make the Metricsco API as explorable as possible, you can setup a separate profile for test-mode. Each profile has its own API key.
You authenticate to the Metricsco API by providing one of your API keys in the request. You can manage your API keys from your account profile. You can have multiple API keys active at one time. Your API keys carry many privileges, so be sure to keep them secret!
To use your API key, you need only set apiKey equal to your key.
All API requests must be made over HTTPS and You must authenticate for all requests.
Metricsco uses conventional HTTP response codes to indicate success or failure of an API request. In general, codes in the 2xx range indicate success, codes in the 4xx range indicate an error that resulted from the provided information (e.g. a required parameter was missing, etc.), and codes in the 5xx range indicate an error with Metricsco’s servers.
HTTP Status Code Summary
HTTP Response Code 400 – Bad Request. Often missing a required parameter or parameters validation failed. Message Body will include Error Message.
HTTP Response Code 401 – API Key validation failed.
HTTP Response Code 404 – Not Found. The requested item does not exists.
HTTP Response Code 500 – Server Error.
Importing your old data
We can help you backfill old data. Contact Us