You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For historical reasons, the Visit API model does not expose any information of the short URL that was visited to produce it.
This is because originally you could only get visits for a specific short URL, so the URL was implicit.
However, the API has evolved a lot since, with the ability to get visits for a domain, tag or all visits together. This means it would now be a more useful information.
Perhaps exposing the whole ShortUrl model for every visit would be a bit overkill, but at least a way to uniquely identify a short URL (domain + shortCode/customSlug and potentially short URL just for convenience) so that it can be used to query the short URL via other endpoints.
Use case
This would help users cross-reference the short URL that generated a particular visit when listing visits that belong to different short URLs.
The text was updated successfully, but these errors were encountered:
Summary
For historical reasons, the
Visit
API model does not expose any information of the short URL that was visited to produce it.This is because originally you could only get visits for a specific short URL, so the URL was implicit.
However, the API has evolved a lot since, with the ability to get visits for a domain, tag or all visits together. This means it would now be a more useful information.
Perhaps exposing the whole
ShortUrl
model for every visit would be a bit overkill, but at least a way to uniquely identify a short URL (domain + shortCode/customSlug and potentially short URL just for convenience) so that it can be used to query the short URL via other endpoints.Use case
This would help users cross-reference the short URL that generated a particular visit when listing visits that belong to different short URLs.
The text was updated successfully, but these errors were encountered: