How to make a name show instead of a number when sending sms through a Gateway? - anonymous

this question is a tad more on the technical side, but I hope it can be easilly solved.
You see, my problem here is the following:
I have a Gateway for sending SMS, however, I want those SMS to show a name instead of the number (company/Bank name for instance) like some Banks/providers have over here.
However I can't seem to find any sort of documentation on how to achieve this.
Is there any sort of way to achieve what I want?

Related

Generate Instagram related Hashtags - API

I'm trying to generate multiple related hashtags based on the keyword entered by the user. For example: if the user has typed 'meme', it would generate multiples hashtags related to it (memes, funny memes)
I looked for an Instagram API but didn't find any such endpoints. There are lots of sites and apps available over this thing. Can anyone suggest to me how this would work? I'm not expecting you to do work for me. Just need your guidance on this? Is there any way to achieve this?
https://developers.facebook.com/docs/instagram-api/guides/hashtag-search/ (I goes over all the endpoint but didn't find it, is there any other way to achieve it?)
Demo:- https://toolzu.com/hashtag-generator-for-instagram/ (this brings related hashtags, difficulty and number of times each hashtag has been used)
This api returns hashtags related to a keyword. It's easy to use with axios. Downside is a the limited number of free calls
hashtag api: https://rapidapi.com/miguel.aka.kelter/api/hashtagy-generate-hashtags/
Good luck

Get referral (parthnership) link for a product on Aliexpress?

The question is about API and independent from programming language.
I want to get a commission from products on Aliexpress.
API documentation (press "API Documents")
But I can't understand how to generate a link and then how to check if it is correct.
As I understand I need to use 1.1 listPromotionProduct request, get all the links from the result and apply 1.3 getPromotionLinks to them. Is it correct?
Yes you're right this is the way to do it, so you need to do two API calls, one to api.listPromotionProduct, collect up the URLs and then make a call to api.getPromotionLinks.
This URL works:
http://gw.api.alibaba.com/openapi/param2/2/portals.open/api.getPromotionLinks/YOURAPIKEY?fields=totalResults,trackingId,publisherId,url,promotionUrl&trackingId=YOURTRACKINGIDHERE&urls=https://www.aliexpress.com/item/Rotary-Cheese-Tools-Cheese-Grater-Stainless-Steel-Slicer-Shreds-Drum-Hand-Held-Ginger-Graters-Cutter-Kitchen/32706493641.html
Append more URLs to this URL using a comma (up to 50 URL's).
Likely Issue
The thing I was doing wrong was using the wrong trackingID, it's not your digital signature but the affiliate ID you specified in https://portals.aliexpress.com/publisher_manage.htm (I think you can have multiple affiliate ID's).

MessageBird originator handling

I am a bit confused conerning the services of the SMS Provider MessageBird; their API permits to include an "Originator", which is used as the sender of the SMS. On one hand, the documentation
https://developers.messagebird.com/
states that in some countries the originator is not used and refers to a list of country-specific information. On the other hand, this list
http://support.messagebird.com/hc/en-us/sections/202017565-Country-Info-Restrictions?page=1#articles
does not include an entry for Denmark. The specific problem is that using the same account, the originator is used for Germany, but apparently doesn't work for Denmark. Does anyone have any experience with this or any information which might be helpful? If so, I would appreciate any comment.
The originator as you said it is going to be used as the sender of the SMS.
But there are restrictions as you noted on the docs. For example when you are sending messages to the US you cannot use alphanumeric originators like "Codor LLC". You need to use a numeric phone number.
If you are trying to send an SMS to Denmark from a german originator number it should work. No restrictions apply here.
Something else can be broken. Please contact support (support#messagebird.com) and we'll help you out (I work at MessageBird).

youtube API v3 - rate (like/dislike) comment/commentThread?

Quick question - as stated in the title. Is that possible? I thought the following endpoint would be my best shot: https://developers.google.com/youtube/v3/docs/comments/update, but can't find anything that resembles api call for rating a video, nor did I find any documentation on that for v3
If it is, please point me to the http endpoint.
Partially Yes, You can use that endpoint and specify a value for snippet.viewerRating but as of now it only allows you to specify two values like and none.
The rating the viewer has given to this comment. Note that this property does not currently identify dislike ratings, though this behavior is subject to change. In the meantime, the property value is like if the viewer has rated the comment positively. The value is none in all other cases, including the user having given the comment a negative rating or not having rated the comment.

How to get reposted tracks from my activities?

Using the Souncloud API, I'd like to retrieve the reposted tracks from my activities. The /me/activities endpoint seems suited for this and I tried the different types provided.
However, I didn't find out how to get that data. Does anyone know?
Replace User Id, limit and offset with what you need:
https://api-v2.soundcloud.com/profile/soundcloud:users:41691970?limit=50&offset=0
You could try the following approach:
Get the users that shared a track via /tracks/{id}/shared-to/users endpoint.
Fetch the tracks postet by this user via /tracks endpoint, as the _user_id_ is contained.
Compare the tracks metadata with the one you originally posted.
I am not into the Soundcloud API, but taking a close look at it seems to make this approach at least as technical possible, though e.g. fetching all tracks won't be a production solution, of course. It's more a hint. Perhaps reposting means something totally different in this context.
And the specified entpoint exists in the general api doc, so I don't know if you would have to extend the java-api-wrapper for using it.