Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include new scope in s2s authorization #49

Merged
merged 2 commits into from
Jul 29, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions public/en-us/web-services/authentication/s2s.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,7 @@ When making any requests to service-to-service endpoints, you must always provid
| client_id | integer | true | Client ID issued to your game. |
| client_secret | string | true | Client Secret issued to your game. This should be secure on a backend server and never displayed to players. |
| grant_type | string | true | Must be `client_credentials`. |
| scope | string | false | The scopes you wish your token to have. Currently only, read, write, and monetization is supported. |
| scope | string | false | Specify the comma-separated scopes you wish your token to have. Valid scopes are `read`, `write`, `update`, and `monetization`. The `update` scope will elevate the token's authorization, allowing it to edit mods while acting as the game's leader. |

```
POST https://{your-game-id}.modapi.io/v1/oauth/token
Expand Down Expand Up @@ -163,4 +163,4 @@ Your backend service should be configured such as in the event that the service

- An OAuth Client ID, Client Secret and Service Tokens should be kept confidential at all times and never shared with untrusted clients such as game consoles or mobile devices.
- Service Tokens are not associated with any specific user on mod.io, and is a generic token designed to identify your secure server for S2S related tasks.
- Service Tokens are valid for 90 days. We highly recommend caching the token on your backend and only request a new service token if you require different scope(s) or the token has expired.
- Service Tokens are valid for 90 days. We highly recommend caching the token on your backend and only request a new service token if you require different scope(s) or the token has expired.
Loading