search

bitly / bitly-api-python

python library to the bitly api
http://github.com/bitly/bitly-api-python
Other
244 stars 92 forks source link

Set or edit tags using python client #44

Closed rkpatel33 closed 7 years ago

rkpatel33 commented 7 years ago

I notice that there does not seem to be a way to set the tag for links through the client, only bundles, yet from reading online bundles are deprecated.

Is there away to set/get tags using the API right now?

Thx.

tpherndon commented 7 years ago

There are no public APIs for dealing with tags right now, no.

rkpatel33 commented 7 years ago

We will be creating thousands of shortened links for unique referral urls to be sent in text messages. Is there any other way you suggestion to organize them if they are create via API as part of a Django app?

My current fallback intention was to come up with a naming scheme that would include all the info that I would need to look one up using the search.

tpherndon commented 7 years ago

The normal recommendation for dealing with Bitlinks is to store, at the very least, the target URL and the Bitlink itself in a data store of some kind. That way you avoid re-shortening the same link, which wastes your rate limit, and you have a record of what you've done. When you need a Bitlink for a URL, look first in your data store. If you find the record, use that information. If you do not find a record, shorten the URL via the API, then store the result in your data store.

rkpatel33 commented 7 years ago

Ok, thanks, that makes sense on our backend and will keep it in mind.

I was more asking about organizing in the web interface, since we will also use the Bitly website to create manual PR and marketing links etc. Will be hard to look at if it’s also cluttered with thousands of server generated links as well.

Rishi Patel | mail@rishinyc.com

On Fri, Aug 4, 2017 at 11:01 AM, Peter Herndon notifications@github.com wrote:

The normal recommendation for dealing with Bitlinks is to store, at the very least, the target URL and the Bitlink itself in a data store of some kind. That way you avoid re-shortening the same link, which wastes your rate limit, and you have a record of what you've done. When you need a Bitlink for a URL, look first in your data store. If you find the record, use that information. If you do not find a record, shorten the URL via the API, then store the result in your data store.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/bitly/bitly-api-python/issues/44#issuecomment-320314854, or mute the thread https://github.com/notifications/unsubscribe-auth/ADn5wTHzApEGct44Q87sUirsWW6vKhJbks5sU1xpgaJpZM4OuADv .

tpherndon commented 7 years ago

Assuming you are a paying customer, I would separate your usage into two separate groups under the account, one for marketing and PR, and one for your automated referral Bitlinks.

rkpatel33 commented 7 years ago

Awesome. Thx!