A little ROBLOX Web API for use with the upcoming HttpService.
I’ve focused on requests related to groups until now, as ROBLOX lacks a lot of those.
However, I plan to add methods for each other aspect of ROBLOX, too.
Any feedback, suggestions or requests for additional methods?
[size=2]Is this the proper board to post it?[/size]
Fantastic! A long-requested attempt at enhancing group-management! 
This is great, why not add group logo while you’re at it?
Maybe description?
Neato. How about adding a way to get the current shout and the name of the leader?
Unrelated to groups: Have you thought about adding a method to get a player’s username from their userid and vice versa? That would be super useful.
[quote] Neato. How about adding a way to get the current shout and the name of the leader?
Unrelated to groups: Have you thought about adding a method to get a player’s username from their userid and vice versa? That would be super useful. [/quote]
This is already possible with the current API is it not?
[quote] Neato. How about adding a way to get the current shout and the name of the leader?
Unrelated to groups: Have you thought about adding a method to get a player’s username from their userid and vice versa? That would be super useful. [/quote]
This is already possible with the current API is it not?[/quote]
Not as far as I’m aware.
Note: Added GetGroupLeader and GetGroupDescription. WIll work work on the name/id of the user now.
Another note: Also added GetUserName and GetAllNames. Check documentation.
Check http://janberktold.com/RobloxAPI/docs/ for updated requests.
[quote] [quote=“ArceusInator” post=5848]Neato. How about adding a way to get the current shout and the name of the leader?
Unrelated to groups: Have you thought about adding a method to get a player’s username from their userid and vice versa? That would be super useful. [/quote]
This is already possible with the current API is it not?[/quote]
Not as far as I’m aware.[/quote]
Username from ID: http://api.roblox.com/users/261
However, currently you can’t go the other way.
Great job by the way Jan! Actually helps me massively.
Group shout would be useful as mentioned.
Maybe create some forum APIs? Would be great if we could display a thread and the most recent replies in game.
[quote] [quote=“woot3” post=5856][quote=“ArceusInator” post=5848]Neato. How about adding a way to get the current shout and the name of the leader?
Unrelated to groups: Have you thought about adding a method to get a player’s username from their userid and vice versa? That would be super useful. [/quote]
This is already possible with the current API is it not?[/quote]
Not as far as I’m aware.[/quote]
Username from ID: http://api.roblox.com/users/261
However, currently you can’t go the other way.
Great job by the way Jan! Actually helps me massively.
Group shout would be useful as mentioned.
Maybe create some forum APIs? Would be great if we could display a thread and the most recent replies in game.[/quote]
The problem with groups shouts are, that they have to be visible to the public in order for me to be able to read them out.
And yea, after I updated to a better cache system, I’ll go for some forum stuff + the other way around.
That’s cool
I’d like a simple way to set and get strings per player
like global Player:SaveString()
Finished porting the cache over to a SQL database for some organization.
Will work on more requests now.
Return nil if it can not be read?
http://apiroblox.netne.net/GetShout.php?gid=100130
Made one myself. Thought it might go quite well on this thread.
As a web developer with a website based on roblox which has over 20,000 registered accounts, I can tell you that I’d never actually use any of these APIs. Reason being that if they aren’t officially supported by ROBLOX, then I have no way of knowing if your service will actually work. If you want to be useful, you should write an API and then put it on GitHub or something similar. That way, web developers can have the peace of mind to know that it’s going to work.
On the other hand, this isn’t even that hard. As long as you have some basic knowledge on how to use curl, you don’t need one of these. One of the perks of an API as opposed to a web-based API, is that you can use authenticated accounts. No one in their right mind would use a web-api with a ROBLOX username and password. Until ROBLOX can add some sort of API key system, you’re better off just writing it yourself.
[quote] As a web developer with a website based on roblox which has over 20,000 registered accounts, I can tell you that I’d never actually use any of these APIs. Reason being that if they aren’t officially supported by ROBLOX, then I have no way of knowing if your service will actually work. If you want to be useful, you should write an API and then put it on GitHub or something similar. That way, web developers can have the peace of mind to know that it’s going to work.
On the other hand, this isn’t even that hard. As long as you have some basic knowledge on how to use curl, you don’t need one of these. One of the perks of an API as opposed to a web-based API, is that you can use authenticated accounts. No one in their right mind would use a web-api with a ROBLOX username and password. Until ROBLOX can add some sort of API key system, you’re better off just writing it yourself. [/quote]
Considering I’m getting some hundreds requests daily since HttpService was released, there seems to be a group of developers who are interested in such an API.
I don’t exactly get what you mean by ‘web-api with ROBLOX username and password’ as nobody here talked about that.