Authentication

All requests to MarketHype’s API require authentication. To authenticate, send the correct HTTP header with a valid API token for your organization.

The API token should always be provided as an HTTP header called X-API-TOKEN. Requests with a missing or incorrect token header will receive a 401 (Unauthorized) HTTP response.

<aside> <img src="/icons/key_green.svg" alt="/icons/key_green.svg" width="40px" />

API Token

You can create new API tokens under Settings / API Key in the MarketHype app.

</aside>

Endpoints

Authenticated users can interact with any endpoint through the specified HTTP request method. For security, SSL encryption by issuing requests through HTTPS is enforced for all API endpoints.

All API endpoints are available under https://api.markethype.io. Refer to the API references for each endpoint for a complete URL.

HTTP Response codes

These are the HTTP Response codes the MarketHype API may use. The documentation for each endpoint will specify exactly which response codes are applicable to that endpoint.

• 200 - Success - Request processed successfully
• 204 - Success - Request processed successfully
• 401 - Unauthorized - Missing or incorrect API token in header
• 422 - Unprocessable Entity - Something is not right with the request body. The response body will contain more information about the error
• 429 - Too Many Requests - You are making requests at a rate that exceeds acceptable API use. You should reduce the rate at which you query the API.
• 500 - Internal Server Error - Something went wrong on the MarketHype servers processing your request. We logged the error, but your message was most likely lost.