randomapi/randomuser.me-node

Source code that powers randomuser.me

randomuser.me-node's Issues

Add CORS support

Add timezone

Is it possible to add user's timezone in the "dob" and "registered" fields based on birth location?

Thanks

Add TR nat

Port over TR nat from PHP to Node.js

Add CSV format

CSV format option for API results

Bigger images?

Apparently even the big image is only a 128x128 thumbnail - is there a way to retrieve the full size image of a user?

Add Description

Hello there,
This is not an issue it's just a suggestion, can you please add a description of the users, so when we designers fill the data with awesome randomuser API..there is a little thing we need that a description, that currently missing...If you guys add this features then it will be more usable.
Best Regards,
Ajoy Karmakar

Problem in extension photoshop

hello
i have problem in extension photoshop

http://i.imgur.com/SVd27AY.png

High quality Profile Picture

Hi,
You did a great job but I stuck on a problem...Actually am creating an application where the people's profile picture should come with a large size but now the scenario is the image is pixelated, am already using large version, can you please increase the quality at least 600x600 pixel ?

best regards,
Ajoy Karmakar

Convert stats page from AJAX to Sockets

Addition of "friends" field?

Very useful for building more complex prototypes. I would be happy to see if this is something I can add!

Support querying by id

API not support querying by id and also not respect the RESTful API conventions so it can support as separate action such as (https://randomuser.me/api/users/:id) or at least as parameter such as (https://randomuser.me/api/?user_id="id").

Multiple Parameters not working

Hi

Im trying to pull 25 female users like this but im getting both males and females.

curl https://randomuser.me/api/?results=25&gender=female

Also tried to get 25 results and only include gender value but it's also not working.

curl https://randomuser.me/api/?results=25&inc=gender

Any help?

Thanks

Space in email address

I've had email addresses with spaces multiple times using the API. For example using this request:
https://randomuser.me/api/?results=1&nat=nl&seed=25f27b301463f0a5

{
  "results": [
    {
      "gender": "female",
      "name": {
        "title": "miss",
        "first": "tammy",
        "last": "van de bovenkamp"
      },
      "location": {
        "street": "6986 stadsbuitengracht",
        "city": "montferland",
        "state": "limburg",
        "postcode": 59032
      },
      "email": "tammy.vande [email protected]",
      "login": {
        "username": "heavybear861",
        "password": "goober",
        "salt": "9yRh9EL8",
        "md5": "be6cd6f72540ce287d9f634db614ba8e",
        "sha1": "72034f0355f89c735360796dce28b44d23c66a7d",
        "sha256": "17d517631b157a260e1ba800bf9a39037b681817e3e1503fdda9fc2b90623f71"
      },
      "registered": 1216056241,
      "dob": 86315672,
      "phone": "(813)-966-4527",
      "cell": "(648)-084-0047",
      "id": {
        "name": "BSN",
        "value": "25864257"
      },
      "picture": {
        "large": "https://randomuser.me/api/portraits/women/78.jpg",
        "medium": "https://randomuser.me/api/portraits/med/women/78.jpg",
        "thumbnail": "https://randomuser.me/api/portraits/thumb/women/78.jpg"
      },
      "nat": "NL"
    }
  ],
  "info": {
    "seed": "25f27b301463f0a5",
    "results": 1,
    "page": 1,
    "version": "1.0"
  }
}

By the way, awesome service!

implement stats page with stats routing

standardize fields

Fields currently differ quite a bit between nationalities.

Need to standardize the names

Option to configure password policy

It would be great if its possible to configure a password policy to randomly generate a password instead of reading from file.

Optimize Generator

Currently, generator is pretty slow...

Investigate ways to improve performance

How to add new data

I would like to open a PR adding my name & 'city' to the database however the README is unclear as to how to do this

Multiversion Support

Feature Proposal: timezone Field In the Data

Hey, guys, Awesome service!

I don't know if this is the right place for suggestions, but I think the data will benefit from a timezone field (maybe as a part of location field?)

Also, how about adding gis coordinates in that object as well?

Thanks!

SQL format

SQL format for API results

add xnat option for excluding nats

Get stats chart working

Stats are being sent, but the chart doesn't work yet.

Extra space at the end of last name steeves

Randomuser.me-Node/api/.nextRelease/data/US/lists/last.txt

Line 264 in 92c811d

steeves

Hello,

had some repeated test failures due to an extra space at the end of the last name "steeves". I attempted to clone this repo, but was having a bit of difficulty getting everything running, figured this changed was easy enough to just communicate to you all. Is there any chance we can get that space removed?

Thank you for your consideration.

Add download flag

Add dl & download flag to automagically start downloads for the API results

Update documentation for version 1.0

is this still under development..!

Hey guys, any wiki how can we contribute, and how can we use!

Implement client rate limiter

Concurrent requests limiter is implemented in NGINX (currently 10 requests/second), but that won't prevent HUGE requests of 10 @ 5,000 users per request from crashing the server.

Make it so that there is a limit of users to be generated on a per ip basis.

Implement pagination

Implement mongodb stats

Convert current MySQL stats system into Mongo

Port PHP data generator to NodeJS

Port over the current functionality - no more and no less...updates will be made once the 1st port is complete

Implement older versions with new Node JS routing

Also log the request stats for older versions in the new mongodb

Skip the Arabic names

I don't want to receive the Arabic names.
I have set https://randomuser.me/api/?results=15&?nat=us , but still showing up.
Did something I miss?
Thank you.

General code clean up

Publish a JSON Schema ...

... so ppl can use this JSON Schema to generate proper access classes e.g. in Java.

Missing license

Hi, missing License,

Add pretty option for JSON

JSON is currently compressed with no whitespace for smallest transfer size.

Add pretty option so that humans can read it if they want to.

Nats can accept multiple comma delimited list

Allow multiple nats to be specified.

Id.value is not always returned

Is it this the desired behaviour?

Great API anyway, many thanks!

It requires Access-Control-Allow-Origin for more than 4 concurrent requests

It does work well for under 4 persons data requested at concurrent

for (let i = 0; i < 4; i++) {
      const promise = this.http.get<any>('https://randomuser.me/api/').toPromise();
      promises.push(promise);
    }
    Promise.all(promises).then(function(values) {
      console.log(values);
    });

But it doesn't work if it over 4 persons data

for (let i = 0; i < 20; i++) {
      const promise = this.http.get<any>('https://randomuser.me/api/').toPromise();
      promises.push(promise);
    }
    Promise.all(promises).then(function(values) {
      console.log(values);
    });

https://stackoverflow.com/questions/50145612/promise-all-get-access-control-allow-origin-only-when-more-than-4-promises-use

Make CLI script

CLI script...possibly NPM module for easy user generation locally

Add DK nat

please add new query by city

I want to get random user by city, like https://randomuser.me/api/?nat=us&city=palmdale
please add this query selection
thanks

dob & registered date results limited in scope and occasionally exhibit an impossibru time paradox

Virtually all dob results are in January 1970 and sometimes the registered date is chronologically prior to dob.

Original conversation with confirmation of the issues as bugs:
https://twitter.com/paul_m_edwards/status/761723586788757504

Update footer text

Update footer text to UI Faces

Support for application/vnd.api+json

Any thought of supporting the content-type of application/vnd.api+json?

Documentation displays invalid JSON

Perhaps a bit trivial, but the documentation at https://randomuser.me/documentation displays invalid JSON. It's missing the first double quote for the values: "property": value",:

{
  "results": [
    {
      "gender": male",
      "name": {
        "title": mr",
        "first": samuel",
        "last": ross"
      },
      "location": {
        "street": 5592 pockrus page rd",
        "city": santa ana",
        "state": oregon",
        "postcode": 69974
      },
      "email": [email protected]",
      "login": {
        "username": silverwolf434",
        "password": blackjac",
        "salt": d14iEZQT",
        "md5": 261a57061d35918f5c3ef7f90f4f2a80",
        "sha1": c330ad8c974ab9982622d5d5506cfed4886a79ab",
        "sha256": 8ca4a1ca48975a69bd829de61298cd6a950dede740d4c0e755d07ee4cfc06fa5"
      },
      "registered": 1155461743,
      "dob": 1078494582,
      "phone": (179)-102-8139",
      "cell": (107)-396-0688",
      "id": {
        "name": SSN",
        "value": 476-30-9095"
      },
      "picture": {
        "large": https://randomuser.me/api/portraits/men/80.jpg",
        "medium": https://randomuser.me/api/portraits/med/men/80.jpg",
        "thumbnail": https://randomuser.me/api/portraits/thumb/men/80.jpg"
      },
      "nat": US"
    }
  ],
  "info": {
    "seed": 705567e86a824a27",
    "results": 1,
    "page": 1,
    "version": 1.0"
  }
}

Add JSONP support

Invalid date format

The date format in the dob field returned by this API is unsupported by Safari, in which it says "Invalid Date" after passing it to the JavaScript Date constructor. Currently, it's a string formatted like "1983-07-14 07:29:45". In my opinion, this API should leave the date formatting up to the consumer, and since this API currently returns the date as a string, it inherently comes with its own formatting.

I propose that to mitigate this, the dob field should be either a UNIX timestamp, or potentially a UNIX timestamp with millisecond resolution. UNIX timestamps are a common, well-known, and widely supported method of representing a specific moment in time. However, JavaScript's Date constructor takes a UNIX timestamp with millisecond resolution (instead of the common second resolution), so a decision would have to be made as to if JavaScript consumers must multiply the result by 1000 before passing it to the Date constructor, or if consumers that support normal UNIX timestamps must divide by 1000 before constructing their respective representation of a moment in time.

Regardless, I think that this field should be changed to either a standard UNIX timestamp or one with millisecond resolution so that it's easier for consumers to parse and easier for consumers to format to their users' respective preferences and locale

Add exclude/include flags

Add flags for the API to specify which fields to include/exclude.