Anon Developer Docs

Docs

APIs and SDKs

Changelog

Get Access

Support

This endpoint returns an Anon Bearer Session token using `Member` credentials.

Member Login

LoginMember

BearerAuth

A session token that can be used to authenticate as an Anon Member identity for use in subsequent requests as a `Bearer` token via `Authorization` header.

LoginSession

Welcome to Anon

Quickstart

Use pre-built actions to automate tasks on connected accounts

Actions Library

Securely collect and connect end-user accounts to your application

Overview

Connect user sessions to your web app using Anon Link

Embed the account connection flow in your iOS app

Use the Anon Chrome Extension Library to create your own chrome extension.

Anon Link Chrome Extension

Embedded Link UI

Integrate your existing auth provider with Anon.

Self-hosted User Pools

Learn how to create `UserPools`, `SdkClients`, and `appUserIdTokens` needed to start using Anon Link.

Connecting your users

Execute actions using connected user sessions

Retrieve a connected user session and execute custom automation scripts

Runtime SDK

Tooling and features that help automate user actions without detection

Stealth Features

Explore different hosting environments for running your automation scripts

Hosting Options

Supported Integrations

Glossary

FAQs / Troubleshooting

Usage reference for SDK endpoints and methods

Typescript SDK Reference

Generates a url for launching Anon Link. You must pass either an appUserId or appUserIdToken in the query parameters.

Create Link URL

Issues a new `AppUserIdToken` to be used as a bearer token for authenticating app user traffic. **Can only be used with Anon-hosted UserPools**. In this case, Anon serves as your identity provider, issuing and validating tokens for your users. For each app user you want to connect to Anon, call this endpoint with that user's ID to issue an AppUserIdToken that they can use for authentication with Anon. This credential is sensitive and can be used to access that user's sessions, so it should be stored securely or not at all. You may call this route whenever you need to issue a new AppUserIdToken (for example, upon login or token expiration). Duplicate calls with the same user ID will refresh the expiration, but will have no other effects. Takes an optional `exp`iration; this defaults to 6 months from time of issuing.

SDKs

APIs

Member Login

Authorizations

Body

Response