Get a Bearer token in Herokuapp FORTNITE
A documented Herokuapp FORTNITE operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Get a Bearer token
- POSTChanges data · Security
skynewz-api-fortnite.herokuapp.com/oauth/token
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Herokuapp FORTNITE operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other Herokuapp FORTNITE operations
- Get Fortnite NewsGET · reads data
- Get Fortnite game statusGET · reads data
- Get Fortnite StoreGET · reads data
- Get PVE Stat by given usernameGET · reads data
- Get Fortnite PVE Info (storm, etc)GET · reads data
- Get a user by usernameGET · reads data
- Get user's stats by usernameGET · reads data
- Get user's stats by user idGET · reads data
Questions
- Can HumDay get a bearer token in Herokuapp FORTNITE?
- Yes. This operation is published in Herokuapp FORTNITE's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my Herokuapp FORTNITE data?
- Yes — this is a POST operation, so it changes something in Herokuapp FORTNITE. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Herokuapp FORTNITE account.
Where this came from
Read from a published API description for Herokuapp FORTNITE at raw.githubusercontent.com/SkYNewZ/rest-fornite-api/develop/src/public/swagger.yaml. The description above is the provider’s own wording, not ours. Last published 2020-11-23.