# APIs

Besides the Client SDKs, Authgear exposes the following APIs for simple integration with your applications for authentication and user management.

All of these are on the endpoint of your app. The default endpoint is at `https://[myapp].authgear.cloud` unless you set up a custom domain. `[myapp]` is your project name.

Unless otherwise specified, all paths mentioned here are relative to the endpoint of your app.

Authgear provides the following groups of APIs:

* [**OAuth 2.0 and OpenID Connect**](https://github.com/authgear/docs/blob/main/api-reference/apis/oauth-2.0-and-openid-connect-oidc): for connecting with OIDC Clients
* [**Admin API**](https://docs.authgear.com/reference/apis/admin-api): for your servers to manage users via a GraphQL endpoint.
* [**User Import API**](https://docs.authgear.com/reference/apis/user-import-api)**:** this is an API that supports the bulk import of users from another system to an Authgear project.
* [**User Export API**](https://docs.authgear.com/reference/apis/user-export-api): an API that allows you to export user data from an Authgear project into a file in CSV or ndjson format.
* [**Authentication Flow (Auth Flow) API**](https://docs.authgear.com/reference/apis/authentication-flow-api): for developing a customized Web or Mobile Native Auth UI instead of the default user interface provided by Authgear.
* [**Resolver Endpoint**](https://docs.authgear.com/get-started/backend-api/nginx): for API Gateway or Servers to check the validity of access tokens or cookies in the request header.

Here are all of the special paths with each group of the API above.

## OAuth 2.0 and OpenID Connect

For more information about the OIDC API endpoint, please refer to the following sections or any of the Regular Web App Getting Started guides.

{% content-ref url="apis/oauth-2.0-and-openid-connect-oidc" %}
[oauth-2.0-and-openid-connect-oidc](https://docs.authgear.com/reference/apis/oauth-2.0-and-openid-connect-oidc)
{% endcontent-ref %}

{% content-ref url="../get-started/oidc-provider" %}
[oidc-provider](https://docs.authgear.com/get-started/oidc-provider)
{% endcontent-ref %}

The related URLs are:

* `/.well-known/openid-configuration`\
  This endpoint serves a JSON document containing the OpenID Connect configuration of your Authgear project. That includes the authorization endpoint, the token endpoint, and the JWKs endpoint. Here is [an example of how it looks](https://accounts.portal.authgear.com/.well-known/openid-configuration).
* `/.well-known/oauth-authorization-server`\
  This endpoint serves a JSON document containing the authorization server metadata of your Authgear project. That includes the authorization endpoint, the token endpoint, and the JWKs endpoint. Here is [an example of how it looks](https://accounts.portal.authgear.com/.well-known/openid-configuration).
* `/oauth2/userinfo`\
  The UserInfo Endpoint is an OAuth 2.0 Protected Resource that returns Claims about the authenticated end user. When the client presents with a valid Access Token, the endpoint responds with the claims packaged in a JSON object. The claims are also the attributes of the [User Profile](https://docs.authgear.com/integration/user-profiles).

## Admin API

For more details about the Admin API, please refer to the following documentation:

{% content-ref url="apis/admin-api" %}
[admin-api](https://docs.authgear.com/reference/apis/admin-api)
{% endcontent-ref %}

The path for the Admin API is:

* `/_api/admin/graphql`

## User Import API

To learn more about using the User Import API, see the following documentation page:

{% content-ref url="../admin-and-operations/user-management/import-users-using-user-import-api" %}
[import-users-using-user-import-api](https://docs.authgear.com/admin-and-operations/user-management/import-users-using-user-import-api)
{% endcontent-ref %}

The path for the User Import API:

* `/_api/admin/users/import`

Use this endpoint to import users.

* `/_api/admin/users/import/{ID}`

Use this endpoint to query the status of an existing user import task.

## User Export API

See the following documentation for a detailed on how to use the User Export API:

{% content-ref url="../admin-and-operations/user-management/export-users-using-the-user-export-api" %}
[export-users-using-the-user-export-api](https://docs.authgear.com/admin-and-operations/user-management/export-users-using-the-user-export-api)
{% endcontent-ref %}

Paths for the User Export API:

* `/_api/admin/users/export`

Use the above endpoint to start the process of exporting users.

* `/_api/admin/users/export/{Task ID}`

Use the above endpoint to check when an existing export process is complete and retrieve the download URL for the export file.

## Authentication Flow API

You can find a detailed overview of the Authentication Flow API in the following documentation:

{% content-ref url="../customization/custom-ui/authentication-flow-api" %}
[authentication-flow-api](https://docs.authgear.com/customization/custom-ui/authentication-flow-api)
{% endcontent-ref %}

The path for the Authentication Flow API is:

* `/api/v1/authentication_flows`

## Resolver Endpoints

The resolver endpoint is at the following URL:

* `/_resolver/resolve`

The endpoint serves as a resolver to check the access token or cookie in the request headers. Forward incoming HTTP requests to this endpoint and the resolver will add the `x-authgear-` headers to the response.

See the list of `x-authgear-` headers in the specs [here](https://github.com/authgear/authgear-server/blob/master/docs/specs/api-resolver.md).

See implementation examples [here](https://docs.authgear.com/get-started/backend-api/nginx).

Should you choose to use Resolver Endpoints instead of JWT tokens to validate each API request, check out the following tutorial to learn how to go about that:

{% content-ref url="../get-started/backend-api/nginx" %}
[nginx](https://docs.authgear.com/get-started/backend-api/nginx)
{% endcontent-ref %}

## Other Special URLs

Here are two other URLs

* `/`\
  This endpoint is the entry point of the Web UI. You can visit it if you want to try your configuration (only for custom domains). However, this is NOT the authorization endpoint. You must use our SDK to initiate an authentication.
* `/settings`

This URL points to the default User settings UI provided by Authgear.