Is WhatPulse API down?
Current status, daily uptime history and troubleshooting for the WhatPulse API (Tracking).
No, WhatPulse is up
WhatPulse answered our last daily check (Oct 24, 2026, 12:25 UTC) in 1429 ms with HTTP 200.
Checking WhatPulse now…
Sending a request from our server.
WhatPulse API uptime history
- Uptime
- 2 checks so far
- Last check
- Oct 24, 2026, 12:25 UTC
- Response
- 1429 ms · HTTP 200
- Last up
- Now
We check WhatPulse's listed URL (https://developer.whatpulse.org/#web-api) once a day. History started when WhatPulse was first checked, so new entries show fewer than 30 days.
WhatPulse API not working for you?
- A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header.
- If calls fail only in the browser with a CORS error, WhatPulse may not allow cross-origin requests. Call it from your server instead.
- If it works from one network but not another, check firewalls, VPNs and regional blocks.
- Check the provider's documentation, status page or social accounts for planned maintenance or a changed endpoint.
Tracking APIs up at their last check
- 1
PostalPinCode API
Online · 857 msAPI for getting Pincode details in India.
- No API key needed
- HTTPS
No authHTTPSCORS ? - 2
WeCanTrack API
Online · 713 msAutomatically place subids in affiliate links to attribute affiliate conversions to click data.
- Callable from the browser (CORS)
- HTTPS
apiKeyHTTPSCORS - 3
WhereParcel API
Online · 692 msUnified parcel tracking API across 60+ carriers worldwide (USPS, FedEx, UPS, DHL, etc.).
- Callable from the browser (CORS)
- HTTPS
apiKeyHTTPSCORS - 4
Aftership API
Online · 506 msAPI to update, manage and track shipment efficiently.
- Callable from the browser (CORS)
- HTTPS
apiKeyHTTPSCORS - 5
Mapbox API
Online · 519 msMaps, directions, geocoding. A free tracking API by Mapbox.
- HTTPS
apiKeyHTTPSCORS ?
WhatPulse API status FAQ
Is WhatPulse API down right now?
WhatPulse answered our last daily check (Oct 24, 2026, 12:25 UTC) in 1429 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether WhatPulse is responding at this moment.
How do you check whether WhatPulse API is up?
Once a day our checker requests WhatPulse's listed URL (https://developer.whatpulse.org/#web-api) and records whether it answers within 15 seconds. Answers like 401 (needs a key), 403 (blocks bots) or 429 (rate-limited) count as up, because the server responded. The listed URL is often the documentation page, so an API endpoint can occasionally fail while its docs stay up.
What can I use if WhatPulse API is down?
Free Tracking APIs that were up at their last check include PostalPinCode, WeCanTrack, WhereParcel. See the full list of WhatPulse alternatives for a comparison.
Why does WhatPulse API work for others but not for me?
A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header. If calls fail only in the browser with a CORS error, WhatPulse may not allow cross-origin requests. Call it from your server instead. If it works from one network but not another, check firewalls, VPNs and regional blocks.