API ThreatJammer.com User API

Conheça a plataforma

O que integrar com ThreatJammer.com User API

Descrição técnica preservada da especificação de origem. A versão do contrato ajuda a identificar a API; confirme a disponibilidade atual no fornecedor.

The public API open to the users. Read the docs and learn more.. General information Description Threat Jammer supports two end-user REST APIs: the User API and the Report API. The end-user uses the User API to interact with the different databases, heuristics, and machine learning processes. Devices use the Report API to interact with Threat Jammer. This document will explain how to use the User API and interact with the different services, create a token, interpret the quota information, and create the HTTP request to interact with the User API. Authentication The API is protected by a Bearer authentication schema. Bearer authentication (also called token authentication) is an HTTP authentication scheme that involves security tokens called bearer tokens. It is used to authenticate the user. All the different endpoints expect a Bearer token in the Authorization header. Example: curl -X 'GET' 'https://dublin.api.threatjammer.com/test' -H 'accept: application/json' -H 'Authorization: Bearer YOUR_API_KEY' You can obtain a token after registering on the ThreatJammer.com website for free. Region specific tokens All the Bearer tokens contain information about the authorized region. The developers have to use a token created for the region they want to use. A token used in a different region will return a 401 Unauthorized error. Global errors The API will return the following permanent errors: - a 401 Unauthorized error if the token is not valid, or does not belong to the region. - a 401 Unauthorized error if the token does not exist. - a 401 Unauthorized error if the token is malformed. - a 403 Forbidden error if the subscription level is not enough. Some endpoints are only available for paid subscription levels. And these temporary errors: - a 429 Too Many Requests error if the quota is exceeded (see below). Quota limits Every request to the User API will consume one (1) quota point. The API has two rate limiting processes: - a quota limit of 5000 requests per month for the FREE account. The limit is reset every month. - a quota limit of 10 requests per minute for the FREE account. The limit is reset every minute and implements a sliding window mechanism.

Do planejamento à produção

Checklist para integrar ThreatJammer.com User API

1. Defina o fluxo. Identifique quais dados precisam circular, o sistema de origem e o resultado esperado.
2. Leia os requisitos oficiais. Verifique acesso à API, plano necessário, versão e ambiente de testes.
3. Configure o acesso com segurança. Guarde credenciais secretas no servidor e conceda apenas as permissões necessárias. Restrinja chaves públicas conforme a documentação do fornecedor.
4. Teste a primeira requisição. Valide os campos, a paginação e o formato de resposta com dados de teste.
5. Prepare o tratamento de falhas. Considere limites de requisição, retentativas com espera e prevenção de operações duplicadas.
6. Acompanhe a integração. Registre erros sem expor dados sensíveis e monitore alterações na API.