***
title: "RequestContextService"
generated: true
---------------
Creates new [RequestContext](/current/core/reference/typescript-api/request/request-context#requestcontext) instances.
```ts title="Signature"
class RequestContextService {
create(config: {
req?: Request;
apiType: ApiType;
channelOrToken?: Channel | string;
languageCode?: LanguageCode;
currencyCode?: CurrencyCode;
user?: User;
activeOrderId?: ID;
}) => Promise;
fromRequest(req: Request, info?: GraphQLResolveInfo, requiredPermissions?: Permission[], session?: CachedSession) => Promise;
}
```
### create
\
ApiType; channelOrToken?: Channel | string; languageCode?: LanguageCode; currencyCode?: CurrencyCode; user?: User; activeOrderId?: ID; }) => Promise<RequestContext>`} since="1.5.0" />
Creates a RequestContext based on the config provided. This can be useful when interacting
with services outside the request-response cycle, for example in stand-alone scripts or in
worker jobs.
Without a `user`, the resulting context is anonymous and carries no permissions, which
services that perform permission checks will reject. Pass the `User` the context should act
as — commonly the superadmin for administrative scripts:
```ts
const { superadminCredentials } = this.configService.authOptions;
const superAdminUser = await this.connection.rawConnection.getRepository(User).findOneOrFail({
where: { identifier: superadminCredentials.identifier },
// The roles (and their channels) must be loaded, or the resulting context
// has the user's id but no permissions.
relations: { roles: { channels: true } },
});
const ctx = await this.requestContextService.create({
apiType: 'admin',
user: superAdminUser,
});
```
### fromRequest
\Permission[], session?: CachedSession) => Promise<RequestContext>`} />
Creates a new RequestContext based on an Express request object. This is used internally
in the API layer by the AuthGuard, and creates the RequestContext which is then passed
to all resolvers & controllers.