curl --request GET \
--url https://api.owem.com.br/v4/i/ping \
--header 'Authorization: <authorization>'{
"requestId": "d662bce0-a94f-4af2-b420-edbe79a8741d",
"success": true,
"size": 1,
"message": "Ping OK",
"data": "pong"
}
Validate authentication, IP allowlist, and TLS connectivity. Test your integration with the Owem API.
curl --request GET \
--url https://api.owem.com.br/v4/i/ping \
--header 'Authorization: <authorization>'{
"requestId": "d662bce0-a94f-4af2-b420-edbe79a8741d",
"success": true,
"size": 1,
"message": "Ping OK",
"data": "pong"
}
Basic {Base64(API_KEY:API_SECRET)}1 on success)"pong" on success{
"requestId": "d662bce0-a94f-4af2-b420-edbe79a8741d",
"success": true,
"size": 1,
"message": "Ping OK",
"data": "pong"
}
| HTTP | Description |
|---|---|
| 200 | Valid credentials and IP on allowlist |
| 400 | Malformed Authorization header |
| 401 | Invalid or revoked API Key/Secret |
| 403 | IP not on allowlist |
| 429 | Rate limit exceeded |
| 500 | Internal server error |
Error 401 - Unauthorized
API_KEY:API_SECRET, check Base64 encoding, and confirm credentials
have not been rotated.Error 403 - Forbidden
Error 400 - Bad Request
Authorization header format. It should be Basic {Base64}.Timeout or TLS error
curl -v for diagnostics, check proxy/firewall, and confirm SNI is
enabled.requestId to support for easier diagnostics.Was this page helpful?