Consuming the API

Authentication

Our APIs' authentication uses the JWT standard with the implementation of unique and temporary tokens requested via the Authenticate (Get JWT) using your client key.

Not our costumer yet?

Click here and register now to enjoy our amazing services! After registration, one of our representatives will contact you to assist.

Already have an account and wish to contract a new service or request a POC client key for testing? Contact us via email at comercial@most.com.br.

Domains

MOST API services must be consumed by the client's backend and their servers must be registered in an IP whitelist. Therefore, any communications with embedded devices must pass through the client's backend before being directed to mostQI.

INFO

Production domain: production-mostqiapi.com (with whitelist)

Production, homologation, and POC domain: mostqiapi.com (without whitelist)

The homologation and POC domain can be accessed from any IP. These two domains point to the same production environment.

It is not recommended to use the mostqiapi.com domain for production, as it is subject to interruptions associated with security triggers.

CAUTION

The exclusive production domain can only be accessed by backends whose IPs have been registered in a mostQI whitelist.

All requests must be made using the HTTPS protocol.

Tests on the DOCs Platform

Our API documentation is made available through a third-party platform to facilitate the visualization and interaction with the provided endpoints. It is important to note the following points:

DANGER

Tests conducted directly on the documentation platform should only be performed using the POC (Proof of Concept) client key, which is intended for demonstration purposes and has limited consumption. The use of production client keys should be carried out exclusively through direct integration by the client's backends.

Security of the client key: It is the client's responsibility to keep the client key secure and confidential. We recommend implementing appropriate measures to protect the client key against unauthorized access. The client will be responsible for the costs of all queries made with their client key.

Responsible Use: The use of the API and its client keys must follow the terms established in the service agreements and the security policies of your organization.

For more information on using our API, read the complete documentation available on the platform.

Authentication#

Domains#

Tests on the DOCs Platform#

Authentication

Domains

Tests on the DOCs Platform