Mention every significant outcome of your projects
I'd say it depends on what position you are applying for. But since you notice that you are currently a student, I'm sure it's sort of junior engineering position. In this case, you should definitely put this number among other outcomes for the project mentioned.
There are no formulae to calculate appropriateness of putting numbers, but I'll try to give away some ideas:
- if it's a side project you've built in your spare time, and you yourself are proud of it, put the numbers if you feel that it will impress people (say, 1 API request isn't cool, 100 so-so, 1000 requests are cool),
- if it's a project you've built solely by your hands and experience, without a team, put the numbers that are 5–20 times greater,
- if it's a project you've built as a member of a team, put the numbers that are even greater by the size of the team (for the team of two, 20,000 API requests is somewhat okay).
What you should keep in mind is that static numbers rarely interest people. You got 1,500 API requests during what period of time? Give some information about dynamics. For example, you got only 1 request at the first day after the launch, then 10 at the second day, then 100 by the end of the week. This picture seems far more impressive because makes people extend approximation further, no matter if they make a gross error in that. In this example case, exponential growth is being shown, which is kinda rad and make people want to hire you right away.
Good practices and numbers
Now, about good practices. Of course, it's significantly more indicative when you put some numbers next to things you have been doing. But there are many sorts of numbers. Say, if you pushed 15 employees to leave the organization because of your difficult nature, this particular way of showing off in numbers isn't practically useful.
Try to use the STAR method. This method is basically invented to stand out on an interview but you can apply it to your resume too.
- Put out the situation. Why did you start that project? What is the all-world problem you've tried to solve? A short sentence or two, like, “I found out that there will be a global shortage of food by 2030, and ones who own farms will be interested in selling their goods for highest price.”
- Then task. What you'd done to solve the problem? Again, a short passage like, “After some consideration, I've come up with an idea that it'd be win-win to connect two audiences, farmers and their end customers.”
- After that, your action. What you actually did, in what manner? Like, “So I created this simple service that would allow farmers post their goods in one tap, add photos and determine marketable quantities, and to stand out against competitors.”
- And as the received outcome, your result. This is where you must shine most and perfect place to put the numbers. Like, “I've launched an MVP in 4 weeks which then gained X users, having produced 1,500 API requests in the course of Y months and growing by Й percent weekly.”
So, in the end, I'd say that amount of numbers should be roughly 1/4 of your resume.