lookups are available in the Management interface: is:bot Search for bots (used for project scoped tokens). is:active Search for active users. email:TEXT Search by e-mail. Translation workflows Using org/rfc/rfc6585#sectio 4] – when throttling is in place Authentication tokens Changed in version 4.10: Project scoped tokens were introduced in the 4.10 release. Each user has his personal access token the user profile. Newly generated user tokens have the wlu_ prefix. It is possible to create project scoped tokens for API access to given project only. These tokens can be identified by the wlp_ prefix

lookups are available in the Management interface: is:bot Search for bots (used for project scoped tokens). is:active Search for active users. email:TEXT Search by e-mail. Translation workflows Using org/rfc/rfc6585#sectio 4] – when throttling is in place Authentication tokens Changed in version 4.10: Project scoped tokens were introduced in the 4.10 release. Each user has his personal access token the user profile. Newly generated user tokens have the wlu_ prefix. It is possible to create project scoped tokens for API access to given project only. These tokens can be identified by the wlp_ prefix

lookups are available in the Management interface: is:bot Search for bots (used for project scoped tokens). is:active Search for active users. email:TEXT Search by e-mail. Translation workflows Using org/rfc/rfc6585#sectio 4] – when throttling is in place Authentication tokens Changed in version 4.10: Project scoped tokens were introduced in the 4.10 release. Each user has his personal access token the user profile. Newly generated user tokens have the wlu_ prefix. It is possible to create project scoped tokens for API access to given project only. These tokens can be identified by the wlp_ prefix

org/rfc/rfc6585#section-4] – when throttling is in place Authentication tokens Changed in version 4.10: Project scoped tokens were introduced in the 4.10 release. Each user has his personal access token the user profile. Newly generated user tokens have the wlu_ prefix. It is possible to create project scoped tokens for API access to given project only. These tokens can be identified by the wlp_ prefix – Is user active? (optional) is_bot (boolean) – Is user bot? (optional) (used for project scoped tokens) GET /api/users/(str: username)/ Returns information about users. username (string) – User’s username

org/rfc/rfc6585#section-4] – when throttling is in place Authentication tokens Changed in version 4.10: Project scoped tokens were introduced in the 4.10 release. Each user has his personal access token the user profile. Newly generated user tokens have the wlu_ prefix. It is possible to create project scoped tokens for API access to given project only. These tokens can be identified by the wlp_ prefix – Is user active? (optional) is_bot (boolean) – Is user bot? (optional) (used for project scoped tokens) GET /api/users/(str: username)/ Returns information about users. username (string) – User’s username

org/rfc/rfc6585#section-4] – when throttling is in place Authentication tokens Changed in version 4.10: Project scoped tokens were introduced in the 4.10 release. Each user has his personal access token the user profile. Newly generated user tokens have the wlu_ prefix. It is possible to create project scoped tokens for API access to given project only. These tokens can be identified by the wlp_ prefix – Is user active? (optional) is_bot (boolean) – Is user bot? (optional) (used for project scoped tokens) GET /api/users/(str: username)/ Returns information about users. username (string) – User’s username

org/rfc/rfc6585#section-4] – when throttling is in place Authentication tokens Changed in version 4.10: Project scoped tokens were introduced in the 4.10 release. Each user has his personal access token the user profile. Newly generated user tokens have the wlu_ prefix. It is possible to create project scoped tokens for API access to given project only. These tokens can be identified by the wlp_ prefix – Is user active? (optional) is_bot (boolean) – Is user bot? (optional) (used for project scoped tokens) GET /api/users/(str: username)/ Returns information about users. username (string) – User’s username

org/rfc/rfc6585#section-4] – when throttling is in place Authentication tokens Changed in version 4.10: Project scoped tokens were introduced in the 4.10 release. Each user has his personal access token the user profile. Newly generated user tokens have the wlu_ prefix. It is possible to create project scoped tokens for API access to given project only. These tokens can be identified by the wlp_ prefix – Is user active? (optional) is_bot (boolean) – Is user bot? (optional) (used for project scoped tokens) GET /api/users/(str: username)/ Returns information about users. username (string) – User’s username

org/rfc/rfc6585#sectio 4] – when throttling is in place Authentication tokens Changed in version 4.10: Project scoped tokens were introduced in the 4.10 release. Each user has his personal access token the user profile. Newly generated user tokens have the wlu_ prefix. It is possible to create project scoped tokens for API access to given project only. These tokens can be identified by the wlp_ prefix – Is user active? (optional) is_bot (boolean) – Is user bot? (optional) (used for project scoped tokens) GET /api/users/(str: username)/ Returns information about users. username (string) – User’s username

org/html/rfc6585#section-4] – when throttling is i place Authentication tokens Changed in version 4.10: Project scoped tokens were introduced in the 4.10 release. Each user has his personal access token the user profile. Newly generated user tokens have the wlu_ prefix. It is possible to create project scoped tokens for API access to given project only. These tokens can be identified by the wlp_ prefix – Is user active? (optional) is_bot (boolean) – Is user bot? (optional) (used for project scoped tokens) GET /api/users/(str: username)/ Returns information about users. username (string) – User’s username