What fields are included in the token request for server-to-server integration?

• A. grant_type, client_id, client_secret, scope, and account_id
• B. redirect_uri and code
• C. response_type only
• D. client_id and redirect_uri

Answer: (A)

Server-to-server integration uses OAuth 2.0 with the client credentials flow, where the app requests a token on its own behalf. The token request must include the grant_type (set to client_credentials), the application's client_id and client_secret, and typically scope to define what the token can access. In Marketing Cloud, you also include account_id to tie the token to a specific MID. Because there’s no user involved in this flow, you don’t supply redirect_uri, code, or response_type—these belong to flows that involve redirecting a user for authorization. So the fields grant_type, client_id, client_secret, scope, and account_id form the correct set for a server-to-server token request.