Similarweb API
GET /v1/website/{id}/demographics-mobile/gender endpoint removal
Stopped workingSubscribe to Similarweb APIShare
On January 1, 2025, the GET /v1/website/{id}/demographics-mobile/gender endpoint stopped working as part of the sunset of Demographics 1.0. Requests sent to this endpoint now fail because it is no longer available.
Calls it hits
GET /v1/website/{id}/demographics-mobile/gender
What to use instead of these calls
Switch to Demographics 2.0 by calling GET /v4/website/{domain}/demographics_v2/gender, which covers both desktop and mobile web together.
In Similarweb API's words
This endpoint is no longer available This endpoint was deprecated as part of the sunsetting of Demographics 1.0 endpoints on 01.01.2025.
Facts
- API
- Similarweb API
api.similarweb.com - Kind
- Endpoint removal
- Announced
- December 31, 2024
- Takes effect
- January 1, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Similarweb API's own pages
Questions
When does this change take effect?
Calls to GET /v1/website/{id}/demographics-mobile/gender on Similarweb API stopped working on January 1, 2025.
What happens to calls after January 1, 2025?
They have failed since January 1, 2025.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Similarweb API 3
-
GET /v1/website/{id}/demographics-mobile/ageEndpoint removal Stopped working -
GET /v1/website/{id}/demographics/ageEndpoint removal Stopped working -
GET /v1/website/{id}/demographics/genderEndpoint removal Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.