randomapi / randomuser.me-old-source Goto Github PK

Example, in french :
Miss => Mlle
Ms, Mrs => Mme
Mr => M

Would save some frustration and headaches of end-users not having to implement their own capitalizing functions

For example:
https://randomuser.me/api/portraits/women/11.jpg
and
https://randomuser.me/api/portraits/thumb/women/11.jpg
are 2 different women.

This also leads to problems on your website. Steps to reproduce the issue are as follows:

1. Visit the following link https://randomuser.me/photos
2. Click on any thumbnail to view the full-size image of the person.
3. You will see a different image.

Hi,
There is a problem in randomuser.me/api . Please fix it cuz I'm testing my project with it! ;) tnx

504 Gateway Time-out

AL
AL
AZ
AR
CA
CL
CT
DE
FL
GA
HI
ID
IL
IN
IA
KA
KY
LA
ME
MD
MA
MI
MN
MS
MT
MO
NE
NV
NH
NJ
NM
NY
NC
ND
OH
OK
OR
PA
RI
SC
SD
TN
TX
UT
VT
VA
DC
WV
WI
WY

WordPress installs don't use local images by default, they use Gravatar. I was thinking of building a random user importer using the API. It would be great if email addresses had associated Gravatar images. Feel free to close if the idea is infeasible.

Some languages have different endings for Male and Female last names.

My suggestions is to look for female_last_names.txt file and use it if present, otherwise stick to default last_names.txt

Hello,
Can you add support for pagination? Or just additional parameter for offset.

I understand that this is based on the unix timestamp that is used for the dob field. But, for a number of reasons, it would be great to have some older random users generated as well.

Based on the current dob field format, I'm not sure how this would be done. Time before epoch??

I'll be generating my own birthdays for the time being, but older users would be great.

Looks like the Random User API is down? Got the following error:

Error 502 Ray ID: 56a51f591829d276 • 2020-02-24 23:12:06 UTC
Bad gateway

Noticed because I have a project on my website that uses it.

using "results" parameter returns n number of users but all from the same nationality.

Can I commit other language data ??
I see you don't merge a German data #27

I have shared C# code for using and displaying data from RandomAPI/Randomuser.me-Data

https://github.com/RaviRamDhali/programming-procedure/blob/master/Snippets/C-Sharp/Data-Generator-RandomUser

• Limit (already there as results)
• Gender (Male/Female)

And probably AGE limited avtars

• say I am looking for 50-60 age users (for demonstrations)

Hey there!

When requesting multiple users, is there a way to find a per-generated-user seed to make a second call that only returns the first item in the results array?

If not, would it make sense to move seed outside of the first result in the results array?

Background — I'm making two calls to your API:

1. This is a GET request for multiple users: https://www.runscope.com/public/03041da1-29a4-4d55-9f08-90098f078340/4c6b0d79-504f-4eed-9460-d24b35e59cdf
2. And this uses the seed from the first result in the first call to (theoretically) fetch the first user in the list again: https://www.runscope.com/public/03041da1-29a4-4d55-9f08-90098f078340/03093baa-4b6b-4a10-85d1-6f681ba89155

Expected behavior: The seed in the first result would apply to only that randomly generated user, and making a subsequent call to /?seed={{seed}} would return that same first user.

Actual behavior: seed is included in the first item in the results array but applies to the entire list of results, rather than the first item. I couldn't find a per-generated-user seed in the response body when making a call like /?results=100.

The main reason I can see the password element being used, is to test the validation of password input fields on a form. In many cases, it is necessary to test that correct validation takes place for special characters, numbers etc. Adding more "random" looking passwords would be a good idea I think.

Currently some local names have unicode characters (groß, Işik, etc), how about names in a different alphabet (Greek, Cyrillic)? Should we agree to use english-transliterated version?

It seems like both website and the api is down

I requested 200 random users and all the user birth days are in January 1970. Is this a bug or by design?

Related to issue #10, the nationality parameter also doesn't work. It randomly returns US or GB. It might require the same fix.

https://randomuser.me/api/?results=200

This doesn't return a valid JSON. It returns only part of it, around ~30 entries, I think, then it stops.

I was using rand(0, 10000) to generate a seed to work with and began noticing that seeding wasnt working, after some very limited test on only integers as seeds, it seems that some seeds work and some dont when only using integers as seeds. I'm using a results parameter of 20 too.

Testing for me:
http://api.randomuser.me/?seed=252&results=20 - Respects seed
http://api.randomuser.me/?seed=2&results=20 - Does not respect seed
http://api.randomuser.me/?seed=200&results=20 - Respects seed
http://api.randomuser.me/?seed=100&results=20 Does not respect seed

I've no idea what the pattern here is?

Why have the user pictures changed?

Hi

This is an awesome API - just a couple of improvements for GB based users would help as follows...

GB Postcode formats are alphanumeric and between six and eight characters long. They are divided into two parts separated by a single space. Examples of postcodes include "SW1W 0NY", "PO16 7GZ", "GU16 7HF", or "L1 8JQ".

As for phone numbers well... formatting them can be complex. You can read much more detail here: http://www.area-codes.org.uk/formatting.php

The basic list of geographic patterns below show the various valid formats in the UK:
01### #####
01### ######
011# ### ####
01#1 ### ####
013873 #####
015242 #####
015394 #####
015395 #####
015396 #####
016973 #####
016974 #####
016977 ####
016977 #####
017683 #####
017684 #####
017687 #####
019467 #####
02# #### ####

Non geographic numbers:
03## ### ####
05### ######
0500 ######
07### ###### Note: Mobile (Cell) numbers always begin "07..."
0800 ######
08## ### ####
09## ### ####

Hope that helps!

Cheers

Maybe consider the ability to point an image tag to the site (randomuser.me/randimg) that would spit out a random user picture. So I could simply drop a few img tags in and get random user pictures.

The Irish data generated does not include a City. Also It includes a State and a Zip. See http://api.randomuser.me/?nat=ie for an example.

The correct format for Irish addresses is as follows:
[Firstname] [Lastname]
[Street Address]
[City name]
Co. [Countyname]

State is not required, but postcodes are being introduced in Summer 2015.

It would be useful to have a seed for each individual user in the list, so we could reference to the same user later. Now it includes the seed only in the first record and it seems to be a seed for the multiple users request itself

For example, our app needs only name & email. Is there anyway for the API to generate only these fields?

Of course, right now we can fetch only required things from API result. However I think it would be faster if API has to generate only a few fields that we need.

i'm suggesting a solution that can be very useful for the utilization of this API by developers.
i figured out that some fields changes name for every nationality, we have the "Zip" field and the " Social Security number " field that change name.
- zip field -
For all nationality it is named "zip" but for GB it is named "Postcode"
- Social Security number field -
here a the list of every nationality available now on the API
AU = PPS
DE = HETU
ES = DNI
FI = HETU
FR = INSEE
GB = NINO
IE = PPS
NL = BNS
US = SSN

• the problem is when developpers will try to deserialize the json, the most common way to do this is to create a Model reprisenting the JsonObject and then deserialize the JsonString,

this is a model that works with US ( see the field SSN ) :

but if we change the nationality for exemple DE ( the field needs to be named HETU ) and if i use the same Model my application will crash,
Yes i can add some conditions, but i know that the API is growing and later some new nationalities will be added,

• suggested solution :
  Adding some naming standards, like this the API will still usefull for a long time, even with the intervention of hundreds of contributers around the world.

i propose :

1. change the name of the security number to "IDnumber"
2. we add a new field "IDnotation" that hold the diffrent naming variations.
3. we have to chose between "Zip" or "Postcode" and use it for all nationalities

http://api.randomuser.me/?gender=female

You can see this by reloading that URL a few times.

http://api.randomuser.me/?format=csv still returns a json result

Pretty much self-explanatory.

Small dataset, I know, but only 1/12 returned results were women.

We can do better than this.